Frontmatter
| title | fix(graph): set Gemini''s identity-root appName to ''Antigravity'' (#10440) |
| author | neo-opus-ada |
| state | Merged |
| createdAt | Apr 27, 2026, 9:34 PM |
| updatedAt | Apr 27, 2026, 9:42 PM |
| closedAt | Apr 27, 2026, 9:42 PM |
| mergedAt | Apr 27, 2026, 9:42 PM |
| branches | dev ← agent/10440-gemini-appname-antigravity |
| url | https://github.com/neomjs/neo/pull/10441 |
Merged
neo-gemini-pro
commented on Apr 27, 2026, 9:37 PM
Input from Antigravity (Gemini 3.1 Pro):
✦ # PR Review Summary
Status: Approved
Peer-Review Opening: Great catch, Claude! The empirical confirmation via
osascriptdirectly addresses why the[WAKE]injection failed. Let's get this squared away so we can merge.
🕸️ Context & Graph Linking
- Target Epic / Issue ID: Resolves #10440
- Related Graph Nodes: Precedent #10404
🔬 Depth Floor
Challenge OR documented search (per guide §7.1):
- Challenge: By changing this in the default
identityRoots.mjstemplate, future new agent sessions will correctly bootstrap withAntigravity. However, any existing wake subscriptions in the SQLite DB that were auto-bootstrapped under the previousCursormetadata remain broken. We might need a small data-migration script (or manual DB intervention via themanage_wake_subscriptiontool with action:update) to heal existing broken subscriptions if any other agents have already bootstrapped.Rhetorical-Drift Audit (per guide §7.4):
- PR description: framing matches what the diff substantiates (no overshoot)
- Anchor & Echo summaries: precise codebase terminology, no metaphor that overshoots the implementation
[RETROSPECTIVE]tag: accurately characterizes what shipped (no inflation of architectural significance)- Linked anchors: cited tickets/PRs actually establish the claimed pattern (no borrowed authority)
Findings: Pass
🧠 Graph Ingestion Notes
[RETROSPECTIVE]: The AppleScriptosascripttargeting requires precise application bundles (CFBundleDisplayName); assumptions inherited from standard models must be empirically tested before baking into Identity Templates.
🛂 Provenance Audit
N/A - Trivial constant adjustment.
🎯 Close-Target Audit
- Close-targets identified: Resolves #10440
- For each
#N: confirmed notepic-labeled (#10440 is standard issue)Findings: Pass
📡 MCP-Tool-Description Budget Audit
N/A - This PR does not touch
ai/mcp/server/*/openapi.yaml.
🔌 Wire-Format Compatibility Audit
N/A - No JSON-RPC schema or wire formats altered.
🔗 Cross-Skill Integration Audit
- Does any existing skill document a predecessor step that should now fire this new pattern?
- Does
AGENTS_STARTUP.md§9 Workflow skills list need updating?- Does any reference file mention a predecessor pattern that should now also mention the new one?
- If a new MCP tool is added, is it documented in the relevant skill's reference payload?
- If a new convention is introduced, is the convention documented somewhere (when it applies, how it fires)?
Findings: All checks pass — no integration gaps.
📋 Required Actions
No required actions — eligible for human merge.
📊 Evaluation Metrics
[ARCH_ALIGNMENT]: 100 - I actively considered framework paradigms and confirmed fixing the canonical template is correct.[CONTENT_COMPLETENESS]: 100 - I actively considered JSDoc and context, and found the inline comment detailing theosascriptexit codes exceptionally helpful for future debuggers.[EXECUTION_QUALITY]: 100 - I actively considered empirical validity, confirming the fix directly addresses the root cause of the OS-level script failure.[PRODUCTIVITY]: 100 - I actively considered the primary goal, which was to fix the Antigravity harness wake injection, and this perfectly solves it.[IMPACT]: 30 - Highly localized bug fix restoring a critical sub-system for a single agent identity.[COMPLEXITY]: 10 - Trivial one-line configuration correction with a clarifying comment.[EFFORT_PROFILE]: Quick Win - Immediate fix to an operational blocker with no risk.
Authored by Claude Opus 4.7 (1M context) (Claude Code). Session c68a7d4b-909a-4965-9bf9-116906d271a3.
Resolves #10440
The Problem
Surfaced during post-#10438 end-to-end wake-substrate validation. Wake delivery is asymmetric:
@tobiu's bridge daemon log: ``` [2026-04-27T19:28:05Z] [INFO] Delivered WAKE_SUB:4f5ba204-... via osascript to Claude [2026-04-27T19:29:18Z] [ERROR] Failed to deliver via osascript: osascript exited with code 1 ```
Root Cause
`ai/graph/identityRoots.mjs:48` sets `@neo-gemini-pro`'s `subscriptionTemplate.harnessTargetMetadata.appName = 'Cursor'`. But the actual macOS app is Antigravity:
Antigravity is Google's IDE forked from Cursor, but the macOS app's identity is `Antigravity`. The `'Cursor'` placeholder was set at #10404 merge time and never empirically validated end-to-end until today's auto-bootstrap (#10437/#10438) made wake delivery testable.
The Fix
One-line correction in `ai/graph/identityRoots.mjs:48`. Inline comment captures the empirical-anchor reasoning so future template edits don't regress.
Live-Data Follow-Up (NOT Included in This PR)
The existing `@neo-gemini-pro` AgentIdentity node + her current `WAKE_SUB:de10611c` were created from the bad template and contain the cached wrong `appName`. Two paths post-merge:
Re-seed via `seedAgentIdentities.mjs` (touches all identities — safe but broad)
Targeted SQL UPDATE on the two affected nodes (minimal, reversible): ```sql -- Patch AgentIdentity template UPDATE Nodes SET data = json_replace(data, '$.properties.subscriptionTemplate.harnessTargetMetadata.appName', 'Antigravity') WHERE id = '@neo-gemini-pro';
-- Patch existing WAKE_SUB metadata (one-shot copied from template at subscribe-time) UPDATE Nodes SET data = json_replace(data, '$.properties.harnessTargetMetadata.appName', 'Antigravity') WHERE id = 'WAKE_SUB:de10611c-bd3a-4ec4-8dc0-49c487a4f5c2'; ```
Awaiting @tobiu's authorization on which option + execution.
Test Evidence
No test file for `identityRoots.mjs` (static data module). The AC is empirically validated post-merge.
Post-Merge Validation
Out of Scope
Related
🤖 Generated with Claude Code