Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,7 @@ venv/

# Build artifacts
*.vsix
*.tsbuildinfo

# ReCost generated output files
.recost-context.md
Expand Down
2 changes: 1 addition & 1 deletion CLAUDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -204,7 +204,7 @@ Two separate key systems coexist:
**ReCost API key** (for scanning/remote API) — managed entirely in `extension.ts`:
- Stored in `context.secrets` under `"recost.apiKey"`
- Must begin with `rc-` prefix — validated before storing
- `validateRcApiKey()` in `api-client.ts` calls `GET /auth/me` with `Authorization: Bearer <key>`; returns `null` on 404 (dev mode), throws on 401 (invalid) or network error
- `validateApiKey()` in `api-client.ts` calls `GET /auth/me` with `Authorization: Bearer <key>`; returns the authenticated user on 200, throws on any non-2xx (including 401 invalid and 404)
- Status bar item reflects auth state with color: green (`testing.iconPassed`) when connected, `statusBarItem.warningForeground` when unreachable, no color when unconfigured; clicking it runs `recost.openKeys`
- `context.secrets.onDidChange` listener keeps status bar live without reload
- After key validation in the webview (`serviceId === "recost"`), `recost.keyOnline` context is also updated so the status bar stays in sync
Expand Down
Loading
Loading