Why I built a CLI when I already had a VS Code extension

说明与用途

HTTP Forge CLI 允许在 CI 中执行测试、与 AI 代理集成以及脚本化工作流程，同时共享单一核心引擎并在本地无外部依赖运行。

问题

The VS Code extension could not support CI, AI agents, or scriptable workflows, limiting HTTP Forge’s automation potential.

结果

The CLI transformed HTTP Forge into an automatable tool, enabling CI integration, AI agent usage, and scriptable workflows while preserving a single core engine.

工作流

• 1. Install the CLI globally with npm install -g @http-forge/cli.
• 2. Run a suite in CI: http-forge run suite "smoke-tests" --environment staging --reporter junit:results/junit.xml --exit-code.
• 3. Use the CLI for AI agent commands: http-forge run collection "My API" --environment staging --include failedOnly --output json.
• 4. Pipe JSON output for composability: http-forge run suite smoke-tests --output json | jq ".failedRequests[].name".
• 5. Discover and generate suites headlessly: http-forge discover --path ./backend --output table.
• 6. Onboard new users: http-forge launch --examples.

证据

The CLI isn't a separate implementation. It's a thin adapter over the same core (@http-forge/core) as the extension and the MCP server.

来源

The CLI does that: http-forge run suite "smoke-tests" --environment staging --reporter junit:results/junit.xml --exit-code

来源

An agent that has terminal access can run: http-forge run collection "My API" --environment staging --include failedOnly --output json

来源

None of that is possible in a GUI, and all of it is awkward through a tool‑call API. The CLI is where HTTP Forge becomes a Unix citizen.

来源

The CLI runs locally. It doesn't phone home, doesn't need a login, and doesn't start a background service.

来源