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

Описание и применение

CLI HTTP Forge позволяет выполнять тесты в CI, интегрироваться с ИИ‑агентами и скриптовать процессы, сохраняя единый ядро и обеспечивая локальное, беззависимое выполнение.

Задача

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.

Источник