Claude Code
Claude Code credentials are stored under the `claude-agent` provider. The registry alias map resolves both `claude-code` and `claude_code` to `claude-agent`.
Purpose
Configure Claude Code access in ActsAsGeek through the authenticated integration routes, then use the project monitoring, secret storage, and usage-ingestion surfaces that already exist in the product.
Prerequisites
- A signed-in Supabase session.
- A CSRF token for POST and PATCH requests.
- An Anthropic API key used by the Claude Agent SDK.
Setup
1
Create the credential with POST /api/integrations using provider `claude-agent` (or the alias `claude-code`).
2
Attach the credential to the target project or environment in the integrations settings surface.
3
Send usage events through /api/v1/costs/usage-events or /api/llm/log when your agent makes model calls.
API & contracts
| Field | Type | Description |
|---|---|---|
| claude-agent | api_key | Aliases `claude-code` and `claude_code` both resolve here. |
- The verifier expects an `api_key` with the `sk-ant-` prefix.
- Project connector bindings accept the `claude-agent` connector type.
- The agentic connector registry uses a generic API-key connector for `claude-agent`.
Failure modes
| 400 | when the API key is missing or uses an invalid prefix. |
| 401 | without a session and 403 for unauthorized project references. |
| 403 | when the CSRF token is missing on mutation routes. |
Partial
Credential storage, verification, connector binding, and usage ingestion are implemented. A Claude Code specific resource fetcher and webhook handler are not implemented in the current codebase.