Repository navigation
fix(antigravity): the agy CLI runtime runs commands in the workspace and reports upstream errors - #120
Merged
Conversation
…m the managed runtime The agy CLI serves ACP itself and keeps its sessions and login under the user's home, not in the instance profile. These tests give the adapter a CLI runtime and expect that: - a CLI session opens without additional directories, because the CLI runs shell commands in an additional directory instead of the workspace; - a turn whose CLI session log ends in an upstream API error fails with that error's status and message; - the account key comes from the refresh token in the CLI's login file; - session instructions go into the system prompt when the agent advertises `systemPrompt.append`. All four fail until the fix. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…and reports upstream errors The agy CLI ignores the GEMINI_HOME that T3 Code sets and keeps its sessions and login in the user's own `.gemini/antigravity-cli` folder. The adapter assumed the managed runtime's profile layout everywhere, so with the CLI: - shell commands ran in the attachments folder, because the CLI uses an additional directory as its working folder; - a turn that ended on an upstream API error was recorded as completed, because the turn-end check found no session log; - the account-change check never saw a login; - the pull request linking instructions were sent as user text on every turn, because only one managed release was known to append them to the system prompt. One value now says where the running runtime keeps its state. The driver builds it from the resolved executable and the user's home, and the session log reader and the account reader take it instead of building managed paths. A CLI session opens without additional directories; attachments still reach the agent as absolute paths. The failure parser also reads the CLI's `STATUS (code NNN): message` form, and the system prompt append is used whenever the agent advertises it. The session log is still read only when no component below the state root is a link, so the check reads this session's own database. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
1 task
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
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.
This pull request fixes four defects of the Antigravity CLI runtime, the runtime T3 Code uses when an instance's Binary path names the
agyexecutable.What a user ran into:
The fix adds one value that says where the running runtime keeps its sessions and its login. The driver chooses it, and both checks read from it. For the CLI, sessions open without additional directories, the error parser reads the CLI's form, and the instructions go into the system prompt.
The first commit adds four tests that fail for these reasons; the second makes them pass. Real turns confirmed the first, second and fourth fix. The user guide gains a section on the CLI runtime.
Not covered: usage limits, session cleanup and the native subagent view still read the private profile.
Claude Fable 5.2, Claude Code in T3 Code.