docs(ai-sessions): bedrock/vertex blocks apply on record-based launches - #443
Merged
Merged
Conversation
The `bedrock:` and `vertex:` blocks on `ai_agent` records are applied on every launch path — D&R rules, UI actions and `ai start-session --definition` — as well as on a direct SessionRequest. Both pages still carried warnings saying record-based launches ignored the blocks and pointed readers at the manual environment-variable mode instead, which left Claude-on-Vertex documented as unreachable from a Hive record entirely (the manual mode cannot carry a service-account JSON). Remove the three stale warnings, make the structured blocks the recommended form, and correct the dr-sessions field table: bedrock and vertex are applied, and anthropic_secret is not required when a provider block supplies the credentials. Also document the one case that does still route to Anthropic with no error — records written before the mutual-exclusion rule that carry anthropic_secret alongside a provider block, where anthropic_secret takes precedence. Co-Authored-By: Claude Opus 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.
What
The
bedrock:andvertex:blocks on anai_agentrecord are applied on every launch path — D&R rules, UI actions andai start-session --definition— as well as on a directSessionRequest. Both AI Sessions pages still carried warnings saying record-based launches ignored the blocks, and pointed readers at the manual environment-variable mode instead.That was worse than a stale note for Vertex: the manual mode cannot carry a service-account JSON, so the docs effectively said Claude-on-Vertex was unreachable from a Hive record at all. A customer read it that way and asked us to confirm.
Changes
docs/9-ai-sessions/alternative-providers.mdanthropic_secretalongside abedrock:/vertex:block.anthropic_secrettakes precedence there, with no error — worth flagging for anyone with a data-residency requirement.docs/9-ai-sessions/dr-sessions.mdbedrock/vertexfield descriptions: "Accepted and validated, but not applied" → applied.anthropic_secretRequired:Yes→No, since a provider block can be the sole credential source.Not covered
docs/9-ai-sessions/providers.mdsays storing a non-Claude provider choice on the record "is still rolling out". The record schema and both launchers do support theprovider+credentialsenvelope, but non-Anthropic providers sit behind a deployment-level flag and I could not confirm its state in production — left alone rather than make a claim I can't back. Worth a follow-up once that's settled.🤖 Generated with Claude Code