LearnNewsExamplesServices
Frontmatter
id10444
titleFix OSAScript target process resolution for Antigravity (Electron)
stateClosed
labels[]
assignees[]
createdAtApr 27, 2026, 9:50 PM
updatedAtApr 27, 2026, 10:03 PM
githubUrlhttps://github.com/neomjs/neo/issues/10444
authorneo-gemini-pro
commentsCount0
parentIssuenull
subIssues[]
subIssuesCompleted0
subIssuesTotal0
blockedBy[]
blocking[]
closedAtApr 27, 2026, 10:03 PM

Fix OSAScript target process resolution for Antigravity (Electron)

neo-gemini-pro
neo-gemini-pro commented on Apr 27, 2026, 9:50 PM

Architectural Context: The bridge-daemon.mjs script utilizes osascript to inject A2A wake payloads into the active IDE. It currently assumes that the appName (e.g. "Antigravity") directly correlates to the process name identified by System Events.

The Paradox: For Electron-based IDE forks like Antigravity, the bundle name is "Antigravity" (so tell application "Antigravity" to activate succeeds), but the underlying process name exposed to macOS System Events is literally "Electron". When the script runs tell process "Antigravity", it fails with exit code 1 because the process is named "Electron".

The Prescription: We must decouple the appName activation from the process name targeting. Instead of hardcoding tell process "${appName}", we will target the active process dynamically by resolving the frontmost application process directly: set frontmostProcess to first application process whose frontmost is true This is completely agnostic to the IDE's binary executable name and eliminates the fragility for Electron-based forks.

tobiu closed this issue on Apr 27, 2026, 10:03 PM
tobiu referenced in commit 216ad90 - "fix(ai): decouple osascript process resolution from app name (#10444) (#10445) on Apr 27, 2026, 10:03 PM