V2EX / 2026-11-05

[分享创造] 做了个 5 MB 的原生 API 客户端 CurlGo，不自动装插件

最近 Postman 12.33.4 在后台给 Codex 和 Claude Code 装插件、改配置的 issue 挺火（ postmanlabs/postman-app-support#14370 ），而且又慢又卡，因为想着自己做一简易的，面向 Agent 的 API 工具。 CurlGo 是 macOS 上的原生 API 客户端，安装包 4.97 MB 。 HTTP / SSE / WebSocket 在同一个工作台，草稿、收藏和历史都保存在本机，不用账号；能贴 curl ，也能导入 Postman v2.1 、Bruno 集合（先预览再保存，集合脚本不执行）；断言检查状态码、响应头、JSON 字段，全部通过才把变量写进环境。桌面端不自动安装技能、插件或 MCP ，不修改 Codex / Claude Code / Copilot 配置，不注册启动 Hook ；可选 CLI 和 API Test Skill 由你自己单独装，--dry-run 只做本地预检。MIT 开源。目前只有 macOS Apple 芯片的安装包。官网： https://curlgo.echovic

Read original source

Source reference for [分享创造] 做了个 5 MB 的原生 API 客户端 CurlGo，不自动装插件. Screenshot not yet available. — Source record · preview pending · www.v2ex.comOpen the source for the full page.

Source record

Source: V2EX
Published: 2026-11-05 17:01:08 UTC
First discovered: 2026-11-05 20:30:16.952Z
Last collected: 2026-11-05 20:30:16.952Z
Author: echoVic
Topic: AI agents
Classification: Product launches & changes
Evidence level: E1 · source record; conclusions unverified

Research analysis

Rule-based research guidance derived from the source record. Audience and commercial demand require validation.

What changed

Source account: 最近 Postman 12.33.4 在后台给 Codex 和 Claude Code 装插件、改配置的 issue 挺火（ postmanlabs/postman-app-support#14370 ），而且又慢又卡，因为想着自己做一简易的，面向 Agent 的 API 工具。 CurlGo 是 macOS 上的原生 API 客户端，安装包 4.97 MB 。 HTTP / SSE / WebSocket 在同一个工作台，草稿、收藏和历史都保存在本机，不用账号；能贴 curl ，也能导入 Postman v2.1 、Bruno 集合（先预览再保存，集合脚本不执行）；断言检查状态码、响应头、JSON 字段，全部通过才把变量写进环境。桌面端不自动安装技能、插件或 MCP ，不修改 Codex / Claude Code / Copilot 配置，不注册启动 Hook ；可选 CLI 和 API Test Skill 由你自己单独装，--dry-run 只做本地预检。MIT 开源。目前只有 macOS Apple 芯片的安装包。官网： https://curlgo.echovic

Version & cost evidence

Recent records to compare: “Show HN: Hand Your Markdown Tasks to Claude Code from a Kanban Board” (Show HN, Nov 5, 2026); “Show HN: CalmCanary – Uptime Monitoring Tool” (Show HN, Nov 5, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.

Who is affected

Identify the existing workflow this change affects before recommending an upgrade. Launch attention does not establish improvement; an API, pricing or availability change may instead create migration work.

Missing comparison points

Missing checks: old versus new behavior, affected plans and regions, availability date, compatibility, rollback path and cost under the same workload.

Migration check

Save the release or policy notice, run the same task on the old and new option, and compare outputs and the full bill. For retirement notices, verify the deadline before scheduling migration.