Files
msd-core/.changeset/503-antigravity-agent-local-detection.md
Tom Boucher b0c5d86aba fix(#503): detect local Antigravity (.agent) installs in /gsd:update (#512)
* fix(#503): detect local Antigravity (.agent) installs in /gsd:update

The installer places local Antigravity installs in ./.agent/
(bin/install.js getDirName('antigravity') === '.agent'), but the
/gsd:update detection cascade in update.md only knew the global
Antigravity layout (.gemini/antigravity{,-ide,-cli}). A local .agent
install fell through to the `Otherwise -> claude` default, so the
update refreshed Claude artifacts instead of the Antigravity install.

Add `.agent` -> antigravity to all four runtime-dir surfaces in
update.md: the execution_context path classifier, the RUNTIME_DIRS
candidate array, the local-scope discovery loop, and the post-update
cache-clear loop (the last otherwise left a stale update indicator on
local Antigravity installs).

Note: the issue also cited update-context.cjs, which does not exist on
`next` (it is introduced by the still-open PR #499). The same .agent
fix should be carried into update-context.cjs when #499 lands.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* chore(#503): add changeset for Antigravity .agent detection fix

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
2026-05-30 12:00:55 -04:00

532 B

type, pr
type pr
Fixed 512

/gsd:update now detects local Antigravity (.agent) installs — local Antigravity installs live in ./.agent/, but the update detection cascade in update.md only knew the global .gemini/antigravity{,-ide,-cli} layout, so a local install was misclassified as claude and refreshed Claude artifacts instead. .agent → antigravity is now mapped across all four runtime-dir surfaces (path classifier, RUNTIME_DIRS, local-scope discovery loop, and the post-update cache-clear loop). (#503)