Antigravity runtime, external Context Trees, and more reliable sessions
Highlights
- Run agents with Google Antigravity on supported macOS and Linux hosts after installing and configuring the provider's
agyCLI. Antigravity is now available in runtime selection. (#2375, #2400) - Optionally connect Claude and Codex agents to an external Context Tree with
context_tree.repository, backed by the bundled@first-tree-ai/context-treeCLI. The integration preserves independently installed or edited Skills and provides a controlled path back to First Tree's built-in Context Tree mode. (#2383)
Notable fixes
- Obtain authentication tokens before opening client WebSockets, contain authentication failures, and bound reconnect resource use. (#2393, #2397)
- Prevent session state deadlocks, reduce session-event query work, and report active provider turns more accurately. (#2409, #2386, #2378)
- Accept supported Managed Skills state during publication preflight, and stop repeatedly retrying invalid state that needs operator attention. (#2363, #2399)
- Generate compatible Context Tree source links for older GitLab versions and pass the correct chat Team identity to Context Tree setup. (#2398, #2366)
- Preserve Grok tool names across incremental tool-call updates and clarify chat creation, sending, and asking in agent guidance. (#2388, #2370)
Compatibility and upgrade
- Node.js 22.13 or newer is required for npm installations. Portable builds include Node.js.
- External Context Tree mode is opt-in. Leave
context_tree.repositoryunset to keep the existing mode. Only Claude and Codex switch to the external Skill family. Codex workspace-only sessions may need their owncontext-tree-setupconnection because they use a different home directory. - Antigravity requires provider-owned installation and authentication; Windows is unavailable in this implementation.
- No database schema or migration files changed in this release range. This does not replace release-image boot validation or operational backup checks.
npm install -g first-tree@0.5.23, or use the official portable installer. Existing installations can follow their configured update policy.