Context
In Neo's agentic ecosystem, agents often work in isolated Git worktrees. Historically, AGENTS_STARTUP.md only documented the worktree bootstrap protocol for Claude Code (ai/scripts/bootstrapWorktree.mjs), leaving a documentation gap for the Antigravity (Gemini) swarm. This led to Gemini agents lacking clear guidance on maintaining process/environment parity when operating inside a worktree.
The Problem
When Gemini agents (Antigravity) run inside a worktree, they need to ensure the canonical environment (.neo-ai-data/, config.mjs) is correctly symlinked and synchronized to prevent duplicate MCP server processes and fragmented memory states. Without an explicit protocol, Gemini agents may bypass bootstrapWorktree.mjs, causing instability.
The Architectural Reality
The current substrate provides ai/scripts/bootstrapWorktree.mjs to seamlessly orchestrate these symlinks and config copies, but the documentation (AGENTS_STARTUP.md) incorrectly scopes this step as "Claude Code only". Furthermore, Gemini's specific configuration logic (e.g. settings.json) needs an authoritative concept document outlining how worktree bootstrap aligns with its specific harness context.
The Fix
- Broaden
AGENTS_STARTUP.md §5 (Worktree Bootstrap) to explicitly cover both Claude Code and Antigravity, explaining that the bootstrapWorktree.mjs script is harness-agnostic.
- Introduce a new, formal concept file for Gemini (
.gemini/concepts/worktree-bootstrap.md) that codifies the bootstrap protocol from the Antigravity perspective.
Acceptance Criteria
Out of Scope
- Modifying
bootstrapWorktree.mjs logic.
- Addressing non-worktree bootstrap workflows.
Origin Session ID: 1d5d1fd1-ff3f-480d-b267-0dad7dc6c3c7
Retrieval Hint: "Antigravity worktree bootstrap generalization"
Context
In Neo's agentic ecosystem, agents often work in isolated Git worktrees. Historically,
AGENTS_STARTUP.mdonly documented the worktree bootstrap protocol for Claude Code (ai/scripts/bootstrapWorktree.mjs), leaving a documentation gap for the Antigravity (Gemini) swarm. This led to Gemini agents lacking clear guidance on maintaining process/environment parity when operating inside a worktree.The Problem
When Gemini agents (Antigravity) run inside a worktree, they need to ensure the canonical environment (
.neo-ai-data/,config.mjs) is correctly symlinked and synchronized to prevent duplicate MCP server processes and fragmented memory states. Without an explicit protocol, Gemini agents may bypassbootstrapWorktree.mjs, causing instability.The Architectural Reality
The current substrate provides
ai/scripts/bootstrapWorktree.mjsto seamlessly orchestrate these symlinks and config copies, but the documentation (AGENTS_STARTUP.md) incorrectly scopes this step as "Claude Code only". Furthermore, Gemini's specific configuration logic (e.g.settings.json) needs an authoritative concept document outlining how worktree bootstrap aligns with its specific harness context.The Fix
AGENTS_STARTUP.md§5 (Worktree Bootstrap) to explicitly cover both Claude Code and Antigravity, explaining that thebootstrapWorktree.mjsscript is harness-agnostic..gemini/concepts/worktree-bootstrap.md) that codifies the bootstrap protocol from the Antigravity perspective.Acceptance Criteria
AGENTS_STARTUP.mdgeneralized to include Antigravity in the Worktree Bootstrap section..gemini/concepts/worktree-bootstrap.mdcreated with accurate, authoritative instructions for Gemini worktrees.ticket-createandticket-intakediscipline is adhered to for these changes.Out of Scope
bootstrapWorktree.mjslogic.Origin Session ID: 1d5d1fd1-ff3f-480d-b267-0dad7dc6c3c7 Retrieval Hint: "Antigravity worktree bootstrap generalization"