Repository navigation
Let admins list and revoke project API keys - #358
Merged
Merged
Conversation
A leaked project key could not be revoked without editing the database, and signed-in dashboard sessions never re-checked their key. Both stores gain list_api_keys and revoke_api_key (by project and prefix), exposed as admin-only GET/DELETE /v1/api-keys routes, AgentLoopClient methods and local and remote CLI commands; listings never include key values. Project-mode dashboard sessions re-verify their key every minute and sign out when it is revoked, and shared dashboards no longer offer demo generators that write files on the host. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
AgentLoop replay self-testThis required repository check evaluates generated synthetic demo traces. It tests the replay and CI machinery; it does not show that this PR improves application performance. AgentLoop CI Report
Performance Gates
Trace inputsThis comparison includes synthetic data. It does not establish application performance gains from a pull request.
Metric Impact
Top Findings
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #357. On a shared server a leaked project key could not be revoked without editing the database, and signed-in dashboard sessions never re-checked their key.
Revocation
Dashboard (project mode)
Tests: store contract (SQLite + Postgres in CI) incl. cross-project revoke refusal; server routes and that a revoked key gets 401; client URL/header scope; CLI; dashboard session recheck and Ingest page. 218 related tests pass locally. Docs: PRODUCTION, CLOUD_DEPLOY (Revoke a key), DASHBOARD, API_VERSIONING, changelog.
🤖 Generated with Claude Code