docs(build-agent): host-first credential flow with the settings deep link#16
Open
mmabrouk wants to merge 1 commit into
Open
docs(build-agent): host-first credential flow with the settings deep link#16mmabrouk wants to merge 1 commit into
mmabrouk wants to merge 1 commit into
Conversation
…link Resolve the host before asking for the API key: check the environment, then ask EU cloud / US cloud / self-hosting, then link the user straight to <host>/settings?tab=apiKeys to copy the key. Claude-Session: https://claude.ai/code/session_01DjaJLpnLtnoRhgbYe7NTC3
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.
Context
The build-agent first-run flow asked for the API key before knowing which Agenta the user is on, and only mentioned
cloud.agenta.ai. Users on the EU or US cloud (or self-hosting) got a link that does not open their instance, and had to find the API keys page by hand.Changes
The credentials step in
skills/build-agent/SKILL.mdnow resolves the host first, then links straight to the key:AGENTA_API_KEY/AGENTA_HOSTin the environment and.env; never re-ask for a value that is already set.https://eu.cloud.agenta.ai, US →https://us.cloud.agenta.ai, self-hosting → ask for the URL. Unsure → the defaulthttps://cloud.agenta.ai.<host>/settings?tab=apiKeys, which opens the API keys page in the user's own workspace (with a sidebar fallback for older self-hosted versions that 404 on the bare path).The README credentials section says the same thing. Storage rules (write a
.envor hand over an export block, never print or commit the key) are unchanged.Scope / risk
Docs-only: SKILL.md and README. No script changes;
lib.shalready defaultsAGENTA_HOSTtohttps://cloud.agenta.aiand picks up.env.The
<host>/settings?tab=apiKeysdeep link ships with Agenta-AI/agenta#5141; the skill includes the sidebar fallback for instances that predate it.https://claude.ai/code/session_01DjaJLpnLtnoRhgbYe7NTC3