Files
msd-core/docs/manual-update.md
Tom Boucher 8f2ebbe9bf feat(#1928): remove sunset Gemini CLI runtime, redirect to Antigravity (#1996)
* feat(#1928): remove sunset gemini cli runtime, redirect to antigravity

Google sunset Gemini CLI on 2026-06-18; Antigravity CLI is its official successor (already a first-class GSD runtime). Remove the gemini runtime from the enum (16->15), aliases, labels, config-home fragment, install path, converters (convertClaudeToGemini{Markdown,Toml,Agent}, convertSlashCommandsToGeminiMentions), capability descriptor, gemini-extension.json, RULESET.GEMINI.*, and the interactive menu (renumbered, no gap).

--gemini now prints an explicit deprecation notice citing the 2026-06-18 sunset and redirects to --antigravity (no silent alias, per the issue's Hyrum's-Law rejection). Antigravity is preserved throughout: its GEMINI.md contextFileName, .gemini/antigravity config home, the shared convertGeminiToolName/claudeToGeminiTools tool vocabulary, and the 'gemini' hookEvents dialect it declares. GEMINI.md retargeted as Antigravity's context file.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* chore(#1928): backfill changeset PR number (#1996)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* chore(#1928): drop Gemini CLI from issue templates (review nit)

Removes the sunset Gemini CLI runtime from the two GitHub issue-template
runtime lists that the removal PR missed, per @davesienkowski's review nit:
- feature_request.yml: 'Applicable runtimes' checkbox (a user could otherwise
  request a feature for a runtime GSD no longer supports)
- bug_report.yml: 'Runtime' dropdown + the stale ~/.gemini/settings.json
  retrieval-help line

Leaves the post-removal templates fully consistent with the Antigravity redirect.

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

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-04 13:32:51 -04:00

1.8 KiB

Manual Update (Non-npm Install)

Use this procedure when npx @opengsd/gsd-core@latest is unavailable — e.g. during a publish outage or if you are working directly from the source repo.

Prerequisites

  • Node.js installed
  • This repo cloned locally (git clone https://github.com/open-gsd/gsd-core)

Steps

# 1. Pull latest code
git pull --rebase origin main

# 2. Build the hooks dist (required — hooks/dist/ is generated, not checked in as source)
node scripts/build-hooks.js

# 3. Run the installer directly
node bin/install.js --claude --global

# 4. Clear the update cache so the statusline indicator resets
rm -f ~/.cache/gsd/gsd-update-check.json

Step 5 — Restart your runtime to pick up the new commands and agents.

Runtime flags

Replace --claude with the flag for your runtime:

Runtime Flag
Claude Code --claude
OpenCode --opencode
Kilo --kilo
Codex --codex
Copilot --copilot
Cursor --cursor
Windsurf --windsurf
Augment --augment
All runtimes --all

Use --local instead of --global for a project-scoped install.

What the installer replaces

The installer performs a clean wipe-and-replace of GSD-managed directories only:

  • ~/.claude/gsd-core/ — workflows, references, templates
  • ~/.claude/commands/gsd/ — slash commands
  • ~/.claude/agents/gsd-*.md — GSD agents
  • ~/.claude/hooks/dist/ — compiled hooks

What is preserved:

  • Custom agents not prefixed with gsd-
  • Custom commands outside commands/gsd/
  • Your CLAUDE.md files
  • Custom hooks

Locally modified GSD files are automatically backed up to gsd-local-patches/ before the install. Run /gsd-update --reapply after updating to merge your modifications back in.