session start: detected repo context, default-config resolution print, --connect degrade#59
Merged
Conversation
…n, degrade --connect for non-interactive configs - Sends repository (owner/name from the origin remote) on POST /v1/sessions, unconditionally: it selects the repo rung of the server's default-config ladder and is merged into the sandbox clone set even with --config - Prints 'using config "X" (repo default|account default)' when a default resolved - --connect degrades to --watch with a note when the resolved config sets interactive: false
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.
Companion to the monorepo default-configs PR (documents/eng/DEFAULT_CONFIGS.md).
agent session start(and the bareagentalias) sendsrepository("owner/name" from the origin remote) on POST /v1/sessions, unconditionally: with no config source it selects the repo rung of the server's default-config ladder, and either way the server merges the repo into the sandbox clone set at its default branch. Outside a git repo, nothing is sent.using config "CI failure triager" (repo default)/(account default); unchanged output when nothing resolved.--connectdegrades to--watchwith a printed note when the resolved config setsinteractive: false(the backend refuses stream/messages for non-interactive sessions).Requires the monorepo PR to be deployed for the new request/response fields; harmless against older backends (unknown request fields are ignored there, and the resolution print only fires when the response carries the fields).