Files

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

4.8 KiB

Raw Blame History

GSD Beta Features

Beta features are opt-in and may change or be removed without notice. They are not covered by the stable API guarantees that apply to the rest of GSD. If a beta feature ships to stable, it will be documented in COMMANDS.md and FEATURES.md with a changelog entry.

`/gsd-ultraplan-phase` — Ultraplan Integration [BETA]

Claude Code only · Requires Claude Code v2.1.91+ Ultraplan is itself a Claude Code research preview — both this command and the underlying feature may change.

What it does

/gsd-ultraplan-phase offloads GSD's plan-phase drafting to Claude Code's ultraplan cloud infrastructure. Instead of planning locally in the terminal, the plan is drafted in a browser-based session with:

An outline sidebar for navigating the plan structure
Inline comments for annotating and refining tasks
A persistent browser tab so your terminal stays free while the plan is being drafted

When you're satisfied with the draft, you save it and import it back into GSD — conflict detection, format validation, and plan-checker verification all run automatically.

Why use it

Situation	Recommendation
Long, complex phases where you want to read and comment on the plan before it executes	Use `/gsd-ultraplan-phase`
Quick phases, familiar domain, or non-Claude Code runtimes	Use `/gsd-plan-phase` (stable)
You have a plan from another source (teammate, external AI)	Use `/gsd-import`

Requirements

Runtime: Claude Code only. The command exits with an error on Antigravity CLI, Copilot CLI, and other runtimes.
Version: Claude Code v2.1.91 or later (the $CLAUDE_CODE_VERSION env var must be set).
Cost: No extra charge for Pro and Max subscribers. Ultraplan is included at no additional cost.

Usage

/gsd-ultraplan-phase         # Ultraplan the next unplanned phase
/gsd-ultraplan-phase 2       # Ultraplan a specific phase number

Argument	Required	Description
`N`	No	Phase number (defaults to next unplanned phase)

How it works

Initialization — GSD runs the standard plan-phase init, resolving which phase to plan and confirming prerequisites.
Context assembly — GSD reads ROADMAP.md, REQUIREMENTS.md, and any existing RESEARCH.md for the phase. This context is bundled into a structured prompt so ultraplan has everything it needs without you copying anything manually.
Return-path instructions — Before launching ultraplan, GSD prints the import command to your terminal so it's visible in your scroll-back buffer after the browser session ends:
```
When done: /gsd-import --from <path-to-saved-plan>
```
Ultraplan launches — The /ultraplan command hands off to the browser. Use the outline sidebar and inline comments to review and refine the draft.
Save the plan — When satisfied, click Cancel in Claude Code. Claude Code saves the plan to a local file and returns you to the terminal.
Import back into GSD — Run the import command that was printed in step 3:
```
/gsd-import --from /path/to/saved-plan.md
```
This runs conflict detection against PROJECT.md, converts the plan to GSD format, validates it with gsd-plan-checker, updates ROADMAP.md, and commits — the same path as any external plan import.

What gets produced

Step	Output
After ultraplan	External plan file (saved by Claude Code)
After `/gsd-import`	`{phase}-{N}-PLAN.md` in `.planning/phases/`

What this command does NOT do

Write PLAN.md files directly — all writes go through /gsd-import
Replace /gsd-plan-phase — local planning is unaffected and remains the default
Run research agents — if you need RESEARCH.md first, run /gsd-plan-phase --skip-verify or a research-only pass before using this command

Troubleshooting

"ultraplan is not available in this runtime" You're running GSD outside of Claude Code. Switch to a Claude Code terminal session, or use /gsd-plan-phase instead.

Ultraplan browser session never opened Check your Claude Code version: claude --version. Requires v2.1.91+. Update with claude update.

/gsd-import reports conflicts Ultraplan may have proposed something that contradicts a decision in PROJECT.md. The import step will prompt you to resolve each conflict before writing anything.

Plan checker fails after import The imported plan has structural issues. Review the checker output, edit the saved file to fix them, and re-run /gsd-import --from <same-file>.

/gsd-plan-phase — standard local planning (stable, all runtimes)
/gsd-import — import any external plan file into GSD

4.8 KiB Raw Blame History