Antigravity CLI 1.5.10: sandboxed commands no longer read ~/.config by default
By default, commands run in the sandbox can no longer read the folder where other programs store their settings and access tokens. In the default mode, the remote agent asks for permission before every file edit.
Antigravity CLI is a command-line coding agent that uses Google’s Gemini models. The developers published the release notes for version 1.5.10 on GitHub on 17 November.
A sandbox is a restricted environment in which commands run by the agent have limited permissions. Until now, those commands could still read the ~/.config folder and, on Windows, the AppData\Roaming folder. Other programs keep their settings and access tokens there, so the developers have blocked reading by default.
The block does not cover everything. Settings for common developer tools such as Git, Go, npm and Python stay readable. However, ~/.git-credentials, which holds Git login details, is now blocked. If a workflow needs other paths, users can allow them separately in the sandbox rules.
Remote agent sessions change too. In the default mode, the agent now asks for permission before each file edit in its workspace, so users may see approval prompts they did not get before. Shift+Tab switches to accept-edits mode, in which the agent edits files without asking.
Gemini Enterprise accounts and sign-ins with Application Default Credentials get Orchestrator in the model menu. It is not a single model but a division of labour: Gemini 4 Carbon (High) draws up a plan and Gemini 4 Hydrogen (High) carries it out. The option appears only if the user can select both models.
The CLI now handles rate limits differently. If the model’s API asks it to wait four minutes or less, the CLI waits and retries. Previously, the turn stopped at any delay over 30 seconds. A spending cap, an exhausted prepaid balance or a full weekly quota stops the turn immediately.
Other changes reduce memory use in long sessions and improve the Remote Control browser view and the editor integration. If an organisation has turned plugins off, their processes no longer start before sign-in. They also stop as soon as an administrator turns plugins off mid-session.
Read more: How an agent works · Agent map