Name the deployment's public URL in the connect-your-account refusal - #1022
Open
brAperia2025 wants to merge 2 commits into
Open
Name the deployment's public URL in the connect-your-account refusal#1022brAperia2025 wants to merge 2 commits into
brAperia2025 wants to merge 2 commits into
Conversation
When an org requires individual model auth, an unconnected person's first message is refused with directions to 'the web app' — but the refusal is often read in Slack, where nothing says where the web app lives. Build the message from the deployment's configured public URL so it names the exact address; the wording without a configured URL is unchanged in substance. The message moves to a pure helper (connectAccountMessage) beside the routing logic, with the URL plumbed through OrchestratorDeps from config.
A failed turn reaches the person wrapped in the generic 'something went wrong on my end' copy, so the connect instructions (and the URL) never reached them. A refusal's reason is delivered verbatim — the same route the session-busy and security-quarantine copy already takes.
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.
When an org enables individual model auth, an unconnected person's first message is refused with directions to "the web app" — but the refusal is usually read on a chat surface where nothing says where the web app lives, so the person has no path to follow.
The refusal now names the deployment's configured public URL: "…Connect Claude or ChatGPT at https://qm.example.com, then try again." The message moves to a pure helper (
connectAccountMessage) beside the routing logic,publicUrlis plumbed throughOrchestratorDepsfrom the existing config field, and deployments without a configured public URL keep an equivalent of the old wording. Covered by a unit test on both shapes.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.