docs: stop advertising project-scoped API keys - #48
Merged
Merged
Conversation
Project-scoped API keys are an unreleased, experimental feature, but the API Keys vs OAuth table said they were "available via API", which led a customer to try to build on them. Describe API key access as full access to the key's workspace, and note that only owners and admins can create keys in a Team workspace. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Contributor
Author
|
@codex review |
|
To use Codex here, create a Codex account and connect to github. |
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Why
The API Keys vs OAuth table on the API Keys page described key access as "Full workspace access (project-scoped keys available via API)". Project-scoped keys are experimental and unreleased. A Team customer read that line and asked how to create them so each of their agents could get its own key. There's no supported way to do that today.
What changed
content/03.cloud/08.api-keys.md:Testing
This is a text-only change. I checked both statements against the cloud code:
apps/web-v2/app/pages/settings/api-keys.vue(canManageApiKeys) andapps/cloud/src/basic_memory_cloud/api/api_keys.py(require_api_key_workspace_owner).🤖 Generated with Claude Code