Skip to content

feat: identify the CLI in request headers - #277

Merged
robingenz merged 1 commit into
mainfrom
feat/client-headers
Nov 18, 2026
Merged

robingenz merged 1 commit into
mainfrom
feat/client-headers

Conversation

@robingenz

Copy link
Copy Markdown
Member

Summary

The CLI names itself in a new way:

Header Value Sent on
User-Agent capawesome-cli/<version> every request
X-Capawesome-Client cli/<version>, in CI cli/<version> ci/<provider> Capawesome Cloud API requests only

Before, the User-Agent was Capawesome CLI v<version>. The provider comes from ci-info 4.4.0, pinned, for example ci/github-actions.

Release

  • Release after the Capawesome Cloud API reads the new header. Until then the API knows the CLI only by the old User-Agent.

Verification

  • src/utils/http-client.test.ts: 10 passed, with tests for the User-Agent, the header only on API requests and the CI suffix
  • tsc --noEmit and Prettier pass

🤖 Generated with Claude Code

The CLI now sends `User-Agent: capawesome-cli/<version>` on every
request. Requests to the Capawesome Cloud API also send
`X-Capawesome-Client: cli/<version>`, followed by ` ci/<provider>`
when the CLI runs in CI. The provider comes from `ci-info`.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@robingenz
robingenz marked this pull request as ready for review November 17, 2026 16:11
@robingenz
robingenz merged commit deb4042 into main Nov 18, 2026
3 checks passed
@robingenz
robingenz deleted the feat/client-headers branch November 18, 2026 05:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant