# GSD 2 **The evolution of [Get Shit Done](https://github.com/gsd-build/get-shit-done) — now a real coding agent.** [![npm version](https://img.shields.io/npm/v/gsd-pi?style=for-the-badge&logo=npm&logoColor=white&color=CB3837)](https://www.npmjs.com/package/gsd-pi) [![npm downloads](https://img.shields.io/npm/dm/gsd-pi?style=for-the-badge&logo=npm&logoColor=white&color=CB3837)](https://www.npmjs.com/package/gsd-pi) [![GitHub stars](https://img.shields.io/github/stars/gsd-build/GSD-2?style=for-the-badge&logo=github&color=181717)](https://github.com/gsd-build/GSD-2) [![Discord](https://img.shields.io/badge/Discord-Join%20us-5865F2?style=for-the-badge&logo=discord&logoColor=white)](https://discord.gg/gsd) [![License](https://img.shields.io/badge/license-MIT-blue?style=for-the-badge)](LICENSE) The original GSD went viral as a prompt framework for Claude Code. It worked, but it was fighting the tool — injecting prompts through slash commands, hoping the LLM would follow instructions, with no actual control over context windows, sessions, or execution. This version is different. GSD is now a standalone CLI built on the [Pi SDK](https://github.com/badlogic/pi-mono), which gives it direct TypeScript access to the agent harness itself. That means GSD can actually _do_ what v1 could only _ask_ the LLM to do: clear context between tasks, inject exactly the right files at dispatch time, manage git branches, track cost and tokens, detect stuck loops, recover from crashes, and auto-advance through an entire milestone without human intervention. One command. Walk away. Come back to a built project with clean git history. 
npm install -g gsd-pi@latest
> **📋 NOTICE: New to Node on Mac?** If you installed Node.js via Homebrew, you may be running a development release instead of LTS. **[Read this guide](./docs/node-lts-macos.md)** to pin Node 24 LTS and avoid compatibility issues.
--- ## What's New in v2.37 - **cmux integration** — sidebar status, progress bars, and notifications for [cmux](https://cmux.com) terminal multiplexer users - **Redesigned dashboard** — two-column layout with redesigned widget - **Search budget enforcement** — session-level search budget prevents unbounded native web search - **AGENTS.md support** — deprecated `agent-instructions.md` in favor of standard `AGENTS.md` / `CLAUDE.md` - **AI-powered triage** — automated issue and PR triage via Claude Haiku - **Auto-generated OpenRouter registry** — model registry built from OpenRouter API for always-current model support - **Extension manifest system** — user-managed enable/disable for bundled extensions - **Pipeline simplification (ADR-003)** — merged research into planning, mechanical completion - **Workflow templates** — right-sized workflows for every task type - **Health widget** — always-on environment health checks with progress scoring - **`/gsd changelog`** — LLM-summarized release notes for any version See the full [Changelog](./CHANGELOG.md) for details. --- ## Documentation Full documentation is available in the [`docs/`](./docs/) directory: - **[Getting Started](./docs/getting-started.md)** — install, first run, basic usage - **[Auto Mode](./docs/auto-mode.md)** — autonomous execution deep-dive - **[Configuration](./docs/configuration.md)** — all preferences, models, git, and hooks - **[Token Optimization](./docs/token-optimization.md)** — profiles, context compression, complexity routing - **[Cost Management](./docs/cost-management.md)** — budgets, tracking, projections - **[Git Strategy](./docs/git-strategy.md)** — worktree isolation, branching, merge behavior - **[Parallel Orchestration](./docs/parallel-orchestration.md)** — run multiple milestones simultaneously - **[Working in Teams](./docs/working-in-teams.md)** — unique IDs, shared artifacts - **[Skills](./docs/skills.md)** — bundled skills, discovery, custom authoring - **[Commands Reference](./docs/commands.md)** — all commands and keyboard shortcuts - **[Architecture](./docs/architecture.md)** — system design and dispatch pipeline - **[Troubleshooting](./docs/troubleshooting.md)** — common issues, doctor, forensics, recovery - **[CI/CD Pipeline](./docs/ci-cd-pipeline.md)** — three-stage promotion pipeline (Dev → Test → Prod) - **[VS Code Extension](./vscode-extension/README.md)** — chat participant, sidebar dashboard, RPC integration - **[Visualizer](./docs/visualizer.md)** — workflow visualizer with stats and discussion status - **[Remote Questions](./docs/remote-questions.md)** — route decisions to Slack or Discord when human input is needed - **[Dynamic Model Routing](./docs/dynamic-model-routing.md)** — complexity-based model selection and budget pressure - **[Pipeline Simplification (ADR-003)](./docs/ADR-003-pipeline-simplification.md)** — merged research into planning, mechanical completion - **[Migration from v1](./docs/migration.md)** — `.planning` → `.gsd` migration --- ## What Changed From v1 The original GSD was a collection of markdown prompts installed into `~/.claude/commands/`. It relied entirely on the LLM reading those prompts and doing the right thing. That worked surprisingly well — but it had hard limits: - **No context control.** The LLM accumulated garbage over a long session. Quality degraded. - **No real automation.** "Auto mode" was the LLM calling itself in a loop, burning context on orchestration overhead. - **No crash recovery.** If the session died mid-task, you started over. - **No observability.** No cost tracking, no progress dashboard, no stuck detection. GSD v2 solves all of these because it's not a prompt framework anymore — it's a TypeScript application that _controls_ the agent session. | | v1 (Prompt Framework) | v2 (Agent Application) | | -------------------- | ---------------------------- | ------------------------------------------------------- | | Runtime | Claude Code slash commands | Standalone CLI via Pi SDK | | Context management | Hope the LLM doesn't fill up | Fresh session per task, programmatic | | Auto mode | LLM self-loop | State machine reading `.gsd/` files | | Crash recovery | None | Lock files + session forensics | | Git strategy | LLM writes git commands | Worktree isolation, sequential commits, squash merge | | Cost tracking | None | Per-unit token/cost ledger with dashboard | | Stuck detection | None | Retry once, then stop with diagnostics | | Timeout supervision | None | Soft/idle/hard timeouts with recovery steering | | Context injection | "Read this file" | Pre-inlined into dispatch prompt | | Roadmap reassessment | Manual | Automatic after each slice completes | | Skill discovery | None | Auto-detect and install relevant skills during research | | Verification | Manual | Automated verification commands with auto-fix retries | | Reporting | None | Self-contained HTML reports with metrics and dep graphs | | Parallel execution | None | Multi-worker parallel milestone orchestration | ### Migrating from v1 > **Note:** Migration works best with a `ROADMAP.md` file for milestone structure. Without one, milestones are inferred from the `phases/` directory. If you have projects with `.planning` directories from the original Get Shit Done, you can migrate them to GSD-2's `.gsd` format: ```bash # From within the project directory /gsd migrate # Or specify a path /gsd migrate ~/projects/my-old-project ``` The migration tool: - Parses your old `PROJECT.md`, `ROADMAP.md`, `REQUIREMENTS.md`, phase directories, plans, summaries, and research - Maps phases → slices, plans → tasks, milestones → milestones - Preserves completion state (`[x]` phases stay done, summaries carry over) - Consolidates research files into the new structure - Shows a preview before writing anything - Optionally runs an agent-driven review of the output for quality assurance Supports format variations including milestone-sectioned roadmaps with `
` blocks, bold phase entries, bullet-format requirements, decimal phase numbering, and duplicate phase numbers across milestones. --- ## How It Works GSD structures work into a hierarchy: ``` Milestone → a shippable version (4-10 slices) Slice → one demoable vertical capability (1-7 tasks) Task → one context-window-sized unit of work ``` The iron rule: **a task must fit in one context window.** If it can't, it's two tasks. ### The Loop Each slice flows through phases automatically: ``` Plan (with integrated research) → Execute (per task) → Complete → Reassess Roadmap → Next Slice ↓ (all slices done) Validate Milestone → Complete Milestone ``` **Plan** scouts the codebase, researches relevant docs, and decomposes the slice into tasks with must-haves (mechanically verifiable outcomes). **Execute** runs each task in a fresh context window with only the relevant files pre-loaded — then runs configured verification commands (lint, test, etc.) with auto-fix retries. **Complete** writes the summary, UAT script, marks the roadmap, and commits with meaningful messages derived from task summaries. **Reassess** checks if the roadmap still makes sense given what was learned. **Validate Milestone** runs a reconciliation gate after all slices complete — comparing roadmap success criteria against actual results before sealing the milestone. ### `/gsd auto` — The Main Event This is what makes GSD different. Run it, walk away, come back to built software. ``` /gsd auto ``` Auto mode is a state machine driven by files on disk. It reads `.gsd/STATE.md`, determines the next unit of work, creates a fresh agent session, injects a focused prompt with all relevant context pre-inlined, and lets the LLM execute. When the LLM finishes, auto mode reads disk state again and dispatches the next unit. **What happens under the hood:** 1. **Fresh session per unit** — Every task, every research phase, every planning step gets a clean 200k-token context window. No accumulated garbage. No "I'll be more concise now." 2. **Context pre-loading** — The dispatch prompt includes inlined task plans, slice plans, prior task summaries, dependency summaries, roadmap excerpts, and decisions register. The LLM starts with everything it needs instead of spending tool calls reading files. 3. **Git worktree isolation** — Each milestone runs in its own git worktree with a `milestone/` branch. All slice work commits sequentially — no branch switching, no merge conflicts. When the milestone completes, it's squash-merged to main as one clean commit. 4. **Crash recovery** — A lock file tracks the current unit. If the session dies, the next `/gsd auto` reads the surviving session file, synthesizes a recovery briefing from every tool call that made it to disk, and resumes with full context. Parallel orchestrator state is persisted to disk with PID liveness detection, so multi-worker sessions survive crashes too. In headless mode, crashes trigger automatic restart with exponential backoff (default 3 attempts). 5. **Provider error recovery** — Transient provider errors (rate limits, 500/503 server errors, overloaded) auto-resume after a delay. Permanent errors (auth, billing) pause for manual review. The model fallback chain retries transient network errors before switching models. 6. **Stuck detection** — If the same unit dispatches twice (the LLM didn't produce the expected artifact), it retries once with a deep diagnostic. If it fails again, auto mode stops with the exact file it expected. 7. **Timeout supervision** — Soft timeout warns the LLM to wrap up. Idle watchdog detects stalls. Hard timeout pauses auto mode. Recovery steering nudges the LLM to finish durable output before giving up. 8. **Cost tracking** — Every unit's token usage and cost is captured, broken down by phase, slice, and model. The dashboard shows running totals and projections. Budget ceilings can pause auto mode before overspending. 9. **Adaptive replanning** — After each slice completes, the roadmap is reassessed. If the work revealed new information that changes the plan, slices are reordered, added, or removed before continuing. 10. **Verification enforcement** — Configure shell commands (`npm run lint`, `npm run test`, etc.) that run automatically after task execution. Failures trigger auto-fix retries before advancing. Auto-discovered checks from `package.json` run in advisory mode — they log warnings but don't block on pre-existing errors. Configurable via `verification_commands`, `verification_auto_fix`, and `verification_max_retries` preferences. 11. **Milestone validation** — After all slices complete, a `validate-milestone` gate compares roadmap success criteria against actual results before sealing the milestone. 12. **Escape hatch** — Press Escape to pause. The conversation is preserved. Interact with the agent, inspect what happened, or just `/gsd auto` to resume from disk state. ### `/gsd` and `/gsd next` — Step Mode By default, `/gsd` runs in **step mode**: the same state machine as auto mode, but it pauses between units with a wizard showing what completed and what's next. You advance one step at a time, review the output, and continue when ready. - **No `.gsd/` directory** → Start a new project. Discussion flow captures your vision, constraints, and preferences. - **Milestone exists, no roadmap** → Discuss or research the milestone. - **Roadmap exists, slices pending** → Plan the next slice, execute one task, or switch to auto. - **Mid-task** → Resume from where you left off. `/gsd next` is an explicit alias for step mode. You can switch from step → auto mid-session via the wizard. Step mode is the on-ramp. Auto mode is the highway. --- ## Getting Started ### Install ```bash npm install -g gsd-pi ``` ### Log in to a provider First, choose your LLM provider: ```bash gsd /login ``` Select from 20+ providers — Anthropic, OpenAI, Google, OpenRouter, GitHub Copilot, and more. If you have a Claude Max or Copilot subscription, the OAuth flow handles everything. Otherwise, paste your API key when prompted. GSD auto-selects a default model after login. To switch models later: ```bash /model ``` ### Use it Open a terminal in your project and run: ```bash gsd ``` GSD opens an interactive agent session. From there, you have two ways to work: **`/gsd` — step mode.** Type `/gsd` and GSD executes one unit of work at a time, pausing between each with a wizard showing what completed and what's next. Same state machine as auto mode, but you stay in the loop. No project yet? It starts the discussion flow. Roadmap exists? It plans or executes the next step. **`/gsd auto` — autonomous mode.** Type `/gsd auto` and walk away. GSD researches, plans, executes, verifies, commits, and advances through every slice until the milestone is complete. Fresh context window per task. No babysitting. ### Two terminals, one project The real workflow: run auto mode in one terminal, steer from another. **Terminal 1 — let it build** ```bash gsd /gsd auto ``` **Terminal 2 — steer while it works** ```bash gsd /gsd discuss # talk through architecture decisions /gsd status # check progress /gsd queue # queue the next milestone ``` Both terminals read and write the same `.gsd/` files on disk. Your decisions in terminal 2 are picked up automatically at the next phase boundary — no need to stop auto mode. ### Headless mode — CI and scripts `gsd headless` runs any `/gsd` command without a TUI. Designed for CI pipelines, cron jobs, and scripted automation. ```bash # Run auto mode in CI gsd headless --timeout 600000 # Create and execute a milestone end-to-end gsd headless new-milestone --context spec.md --auto # One unit at a time (cron-friendly) gsd headless next # Instant JSON snapshot (no LLM, ~50ms) gsd headless query # Force a specific pipeline phase gsd headless dispatch plan ``` Headless auto-responds to interactive prompts, detects completion, and exits with structured codes: `0` complete, `1` error/timeout, `2` blocked. Auto-restarts on crash with exponential backoff. Use `gsd headless query` for instant, machine-readable state inspection — returns phase, next dispatch preview, and parallel worker costs as a single JSON object without spawning an LLM session. Pair with [remote questions](./docs/remote-questions.md) to route decisions to Slack or Discord when human input is needed. **Multi-session orchestration** — headless mode supports file-based IPC in `.gsd/parallel/` for coordinating multiple GSD workers across milestones. Build orchestrators that spawn, monitor, and budget-cap a fleet of GSD workers. ### First launch On first run, GSD launches a branded setup wizard that walks you through LLM provider selection (OAuth or API key), then optional tool API keys (Brave Search, Context7, Jina, Slack, Discord). Every step is skippable — press Enter to skip any. If you have an existing Pi installation, your provider credentials (LLM and tool keys) are imported automatically. Run `gsd config` anytime to re-run the wizard. ### Commands | Command | What it does | | ----------------------- | --------------------------------------------------------------- | | `/gsd` | Step mode — executes one unit at a time, pauses between each | | `/gsd next` | Explicit step mode (same as bare `/gsd`) | | `/gsd auto` | Autonomous mode — researches, plans, executes, commits, repeats | | `/gsd quick` | Execute a quick task with GSD guarantees, skip planning overhead | | `/gsd stop` | Stop auto mode gracefully | | `/gsd steer` | Hard-steer plan documents during execution | | `/gsd discuss` | Discuss architecture and decisions (works alongside auto mode) | | `/gsd status` | Progress dashboard | | `/gsd queue` | Queue future milestones (safe during auto mode) | | `/gsd prefs` | Model selection, timeouts, budget ceiling | | `/gsd migrate` | Migrate a v1 `.planning` directory to `.gsd` format | | `/gsd help` | Categorized command reference for all GSD subcommands | | `/gsd mode` | Switch workflow mode (solo/team) with coordinated defaults | | `/gsd forensics` | Post-mortem investigation of auto-mode failures | | `/gsd cleanup` | Archive phase directories from completed milestones | | `/gsd doctor` | Runtime health checks with auto-fix for common issues | | `/gsd keys` | API key manager — list, add, remove, test, rotate, doctor | | `/gsd logs` | Browse activity, debug, and metrics logs | | `/gsd export --html` | Generate HTML report for current or completed milestone | | `/worktree` (`/wt`) | Git worktree lifecycle — create, switch, merge, remove | | `/voice` | Toggle real-time speech-to-text (macOS, Linux) | | `/exit` | Graceful shutdown — saves session state before exiting | | `/kill` | Kill GSD process immediately | | `/clear` | Start a new session (alias for `/new`) | | `Ctrl+Alt+G` | Toggle dashboard overlay | | `Ctrl+Alt+V` | Toggle voice transcription | | `Ctrl+Alt+B` | Show background shell processes | | `Alt+V` | Paste clipboard image (macOS) | | `gsd config` | Re-run the setup wizard (LLM provider + tool keys) | | `gsd update` | Update GSD to the latest version | | `gsd headless [cmd]` | Run `/gsd` commands without TUI (CI, cron, scripts) | | `gsd headless query` | Instant JSON snapshot — state, next dispatch, costs (no LLM) | | `gsd --continue` (`-c`) | Resume the most recent session for the current directory | | `gsd --worktree` (`-w`) | Launch an isolated worktree session for the active milestone | | `gsd sessions` | Interactive session picker — browse and resume any saved session | --- ## What GSD Manages For You ### Context Engineering Every dispatch is carefully constructed. The LLM never wastes tool calls on orientation. | Artifact | Purpose | | ------------------ | --------------------------------------------------------------- | | `PROJECT.md` | Living doc — what the project is right now | | `DECISIONS.md` | Append-only register of architectural decisions | | `STATE.md` | Quick-glance dashboard — always read first | | `M001-ROADMAP.md` | Milestone plan with slice checkboxes, risk levels, dependencies | | `M001-CONTEXT.md` | User decisions from the discuss phase | | `M001-RESEARCH.md` | Codebase and ecosystem research | | `S01-PLAN.md` | Slice task decomposition with must-haves | | `T01-PLAN.md` | Individual task plan with verification criteria | | `T01-SUMMARY.md` | What happened — YAML frontmatter + narrative | | `S01-UAT.md` | Human test script derived from slice outcomes | ### Git Strategy Branch-per-slice with squash merge. Fully automated. ``` main: docs(M001/S04): workflow documentation and examples fix(M001/S03): bug fixes and doc corrections feat(M001/S02): API endpoints and middleware feat(M001/S01): data model and type system gsd/M001/S01 (deleted after merge): feat(S01/T03): file writer with round-trip fidelity feat(S01/T02): markdown parser for plan files feat(S01/T01): core types and interfaces ``` One squash commit per milestone on main (or whichever branch you started from). The worktree is torn down after merge. Git bisect works. Individual milestones are revertable. Commit messages are generated from task summaries — no more generic "complete task" messages. ### Verification Every task has must-haves — mechanically checkable outcomes: - **Truths** — Observable behaviors ("User can sign up with email") - **Artifacts** — Files that must exist with real implementation, not stubs - **Key Links** — Imports and wiring between artifacts The verification ladder: static checks → command execution → behavioral testing → human review (only when the agent genuinely can't verify itself). ### Dashboard `Ctrl+Alt+G` or `/gsd status` opens a real-time overlay showing: - Current milestone, slice, and task progress - Auto mode elapsed time and phase - Per-unit cost and token breakdown by phase, slice, and model - Cost projections based on completed work - Completed and in-progress units ### HTML Reports After a milestone completes, GSD auto-generates a self-contained HTML report in `.gsd/reports/`. Each report includes project summary, progress tree, slice dependency graph (SVG DAG), cost/token metrics with bar charts, execution timeline, changelog, and knowledge base sections. No external dependencies — all CSS and JS are inlined, printable to PDF from any browser. An auto-generated `index.html` shows all reports with progression metrics across milestones. - **Automatic** — generated after milestone completion (configurable via `auto_report` preference) - **Manual** — run `/gsd export --html` anytime --- ## Configuration ### Preferences GSD preferences live in `~/.gsd/preferences.md` (global) or `.gsd/preferences.md` (project). Manage with `/gsd prefs`. ```yaml --- version: 1 models: research: claude-sonnet-4-6 planning: model: claude-opus-4-6 fallbacks: - openrouter/z-ai/glm-5 - openrouter/minimax/minimax-m2.5 execution: claude-sonnet-4-6 completion: claude-sonnet-4-6 skill_discovery: suggest auto_supervisor: soft_timeout_minutes: 20 idle_timeout_minutes: 10 hard_timeout_minutes: 30 budget_ceiling: 50.00 unique_milestone_ids: true verification_commands: - npm run lint - npm run test auto_report: true --- ``` **Key settings:** | Setting | What it controls | | ---------------------- | ----------------------------------------------------------------------------------------------------- | | `models.*` | Per-phase model selection — string for a single model, or `{model, fallbacks}` for automatic failover | | `skill_discovery` | `auto` / `suggest` / `off` — how GSD finds and applies skills | | `auto_supervisor.*` | Timeout thresholds for auto mode supervision | | `budget_ceiling` | USD ceiling — auto mode pauses when reached | | `uat_dispatch` | Enable automatic UAT runs after slice completion | | `always_use_skills` | Skills to always load when relevant | | `skill_rules` | Situational rules for skill routing | | `skill_staleness_days` | Skills unused for N days get deprioritized (default: 60, 0 = disabled) | | `unique_milestone_ids` | Uses unique milestone names to avoid clashes when working in teams of people | | `git.isolation` | `worktree` (default), `branch`, or `none` — disable worktree isolation for projects that don't need it | | `git.manage_gitignore` | Set `false` to prevent GSD from modifying `.gitignore` | | `verification_commands`| Array of shell commands to run after task execution (e.g., `["npm run lint", "npm run test"]`) | | `verification_auto_fix`| Auto-retry on verification failures (default: true) | | `verification_max_retries` | Max retries for verification failures (default: 2) | | `require_slice_discussion` | Pause auto-mode before each slice for human discussion review | | `auto_report` | Auto-generate HTML reports after milestone completion (default: true) | | `searchExcludeDirs` | Directories to exclude from `@` file autocomplete (e.g., `["node_modules", ".git", "dist"]`) | ### Agent Instructions Place an `AGENTS.md` file in any directory to provide persistent behavioral guidance for that scope. Pi core loads `AGENTS.md` automatically (with `CLAUDE.md` as a fallback) at both user and project levels. Use these files for coding standards, architectural decisions, domain terminology, or workflow preferences. > **Note:** The legacy `agent-instructions.md` format (`~/.gsd/agent-instructions.md` and `.gsd/agent-instructions.md`) is deprecated and no longer loaded. Migrate any existing instructions to `AGENTS.md` or `CLAUDE.md`. ### Debug Mode Start GSD with `gsd --debug` to enable structured JSONL diagnostic logging. Debug logs capture dispatch decisions, state transitions, and timing data for troubleshooting auto-mode issues. ### Token Optimization GSD includes a coordinated token optimization system that reduces usage by 40-60% on cost-sensitive workloads. Set a single preference to coordinate model selection, phase skipping, and context compression: ```yaml token_profile: budget # or balanced (default), quality ``` | Profile | Savings | What It Does | |---------|---------|-------------| | `budget` | 40-60% | Cheap models, skip research/reassess, minimal context inlining | | `balanced` | 10-20% | Default models, skip slice research, standard context | | `quality` | 0% | All phases, all context, full model power | **Complexity-based routing** automatically classifies tasks as simple/standard/complex and routes to appropriate models. Simple docs tasks get Haiku; complex architectural work gets Opus. The classification is heuristic (sub-millisecond, no LLM calls) and learns from outcomes via a persistent routing history. **Budget pressure** graduates model downgrading as you approach your budget ceiling — 50%, 75%, and 90% thresholds progressively shift work to cheaper tiers. See the full [Token Optimization Guide](./docs/token-optimization.md) for details. ### Bundled Tools GSD ships with 19 extensions, all loaded automatically: | Extension | What it provides | | ---------------------- | ---------------------------------------------------------------------------------------------------------------------- | | **GSD** | Core workflow engine, auto mode, commands, dashboard | | **Browser Tools** | Playwright-based browser with form intelligence, intent-ranked element finding, semantic actions, PDF export, session state persistence, network mocking, device emulation, structured extraction, visual diffing, region zoom, test code generation, and prompt injection detection | | **Search the Web** | Brave Search, Tavily, or Jina page extraction | | **Google Search** | Gemini-powered web search with AI-synthesized answers | | **Context7** | Up-to-date library/framework documentation | | **Background Shell** | Long-running process management with readiness detection | | **Async Jobs** | Background bash commands with job tracking and cancellation | | **Subagent** | Delegated tasks with isolated context windows | | **GitHub** | Full-suite GitHub issues and PR management via `/gh` command | | **Mac Tools** | macOS native app automation via Accessibility APIs | | **MCP Client** | Native MCP server integration via @modelcontextprotocol/sdk | | **Voice** | Real-time speech-to-text transcription (macOS, Linux — Ubuntu 22.04+) | | **Slash Commands** | Custom command creation | | **Ask User Questions** | Structured user input with single/multi-select | | **Secure Env Collect** | Masked secret collection without manual .env editing | | **Remote Questions** | Route decisions to Slack/Discord when human input is needed in headless/CI mode | | **Universal Config** | Discover and import MCP servers and rules from other AI coding tools | | **AWS Auth** | Automatic Bedrock credential refresh for AWS-hosted models | | **TTSR** | Tool-use type-safe runtime validation | ### Bundled Agents Three specialized subagents for delegated work: | Agent | Role | | -------------- | ------------------------------------------------------------ | | **Scout** | Fast codebase recon — returns compressed context for handoff | | **Researcher** | Web research — finds and synthesizes current information | | **Worker** | General-purpose execution in an isolated context window | --- ## Working in teams The best practice for working in teams is to ensure unique milestone names across all branches (by using `unique_milestone_ids`) and checking in the right `.gsd/` artifacts to share valuable context between teammates. ### Suggested .gitignore setup ```bash # ── GSD: Runtime / Ephemeral (per-developer, per-session) ────────────────── # Crash detection sentinel — PID lock, written per auto-mode session .gsd/auto.lock # Auto-mode dispatch tracker — prevents re-running completed units .gsd/completed-units.json # Derived state cache — regenerated from plan/roadmap files on disk .gsd/STATE.md # Per-developer token/cost accumulator .gsd/metrics.json # Raw JSONL session dumps — crash recovery forensics, auto-pruned .gsd/activity/ # Unit execution records — dispatch phase, timeouts, recovery tracking .gsd/runtime/ # Git worktree working copies .gsd/worktrees/ # Parallel orchestration IPC and worker status .gsd/parallel/ # Generated HTML reports (regenerable via /gsd export --html) .gsd/reports/ # Session-specific interrupted-work markers .gsd/milestones/**/continue.md .gsd/milestones/**/*-CONTINUE.md ``` ### Unique Milestone Names Create or amend your `.gsd/preferences.md` file within the repo to include `unique_milestone_ids: true` e.g. ```markdown --- version: 1 unique_milestone_ids: true --- ``` With the above `.gitignore` set up, the `.gsd/preferences.md` file is checked into the repo ensuring all teammates use unique milestone names to avoid collisions. Milestone names will now be generated with a 6 char random string appended e.g. instead of `M001` you'll get something like `M001-ush8s3` ### Migrating an existing git ignored `.gsd/` folder 1. Ensure you are not in the middle of any milestones (clean state) 2. Update the `.gsd/` related entries in your `.gitignore` to follow the `Suggested .gitignore setup` section under `Working in teams` (ensure you are no longer blanket ignoring the whole `.gsd/` directory) 3. Update your `.gsd/preferences.md` file within the repo as per section `Unique Milestone Names` 4. If you want to update all your existing milestones use this prompt in GSD: `I have turned on unique milestone ids, please update all old milestone ids to use this new format e.g. M001-abc123 where abc123 is a random 6 char lowercase alpha numeric string. Update all references in all .gsd file contents, file names and directory names. Validate your work once done to ensure referential integrity.` 5. Commit to git --- ## Architecture GSD is a TypeScript application that embeds the Pi coding agent SDK. ``` gsd (CLI binary) └─ loader.ts Sets PI_PACKAGE_DIR, GSD env vars, dynamic-imports cli.ts └─ cli.ts Wires SDK managers, loads extensions, starts InteractiveMode ├─ headless.ts Headless orchestrator (spawns RPC child, auto-responds, detects completion) ├─ onboarding.ts First-run setup wizard (LLM provider + tool keys) ├─ wizard.ts Env hydration from stored auth.json credentials ├─ app-paths.ts ~/.gsd/agent/, ~/.gsd/sessions/, auth.json ├─ resource-loader.ts Syncs bundled extensions + agents to ~/.gsd/agent/ └─ src/resources/ ├─ extensions/gsd/ Core GSD extension (auto, state, commands, ...) ├─ extensions/... 18 supporting extensions ├─ agents/ scout, researcher, worker ├─ AGENTS.md Agent routing instructions └─ GSD-WORKFLOW.md Manual bootstrap protocol ``` **Key design decisions:** - **`pkg/` shim directory** — `PI_PACKAGE_DIR` points here (not project root) to avoid Pi's theme resolution collision with our `src/` directory. Contains only `piConfig` and theme assets. - **Two-file loader pattern** — `loader.ts` sets all env vars with zero SDK imports, then dynamic-imports `cli.ts` which does static SDK imports. This ensures `PI_PACKAGE_DIR` is set before any SDK code evaluates. - **Always-overwrite sync** — `npm update -g` takes effect immediately. Bundled extensions and agents are synced to `~/.gsd/agent/` on every launch, not just first run. - **State lives on disk** — `.gsd/` is the source of truth. Auto mode reads it, writes it, and advances based on what it finds. No in-memory state survives across sessions. --- ## Requirements - **Node.js** ≥ 22.0.0 (24 LTS recommended) - **An LLM provider** — any of the 20+ supported providers (see [Use Any Model](#use-any-model)) - **Git** — initialized automatically if missing Optional: - Brave Search API key (web research) - Tavily API key (web research — alternative to Brave) - Google Gemini API key (web research via Gemini Search grounding) - Context7 API key (library docs) - Jina API key (page extraction) --- ## Use Any Model GSD isn't locked to one provider. It runs on the [Pi SDK](https://github.com/badlogic/pi-mono), which supports **20+ model providers** out of the box. Use different models for different phases — Opus for planning, Sonnet for execution, a fast model for research. ### Built-in Providers Anthropic, Anthropic (Vertex AI), OpenAI, Google (Gemini), OpenRouter, GitHub Copilot, Amazon Bedrock, Azure OpenAI, Google Vertex, Groq, Cerebras, Mistral, xAI, HuggingFace, Vercel AI Gateway, and more. ### OAuth / Max Plans If you have a **Claude Max**, **Codex**, or **GitHub Copilot** subscription, you can use those directly — Pi handles the OAuth flow. No API key needed. > **⚠️ Important:** Using OAuth tokens from subscription plans outside their native applications may violate the provider's Terms of Service. In particular: > > - **Google Gemini** — Using Gemini CLI or Antigravity OAuth tokens in third-party tools has resulted in **Google account suspensions**. This affects your entire Google account, not just the Gemini service. **Use a Gemini API key instead.** > - **Claude Max** — Anthropic's ToS may not explicitly permit OAuth use outside Claude's own applications. > - **GitHub Copilot** — Usage outside GitHub's own tools may be restricted by your subscription terms. > > GSD supports API key authentication for all providers as the safe alternative. **We strongly recommend using API keys over OAuth for Google Gemini.** ### OpenRouter [OpenRouter](https://openrouter.ai) gives you access to hundreds of models through a single API key. Use it to run GSD with Llama, DeepSeek, Qwen, or anything else OpenRouter supports. ### Per-Phase Model Selection In your preferences (`/gsd prefs`), assign different models to different phases: ```yaml models: research: openrouter/deepseek/deepseek-r1 planning: model: claude-opus-4-6 fallbacks: - openrouter/z-ai/glm-5 execution: claude-sonnet-4-6 completion: claude-sonnet-4-6 ``` Use expensive models where quality matters (planning, complex execution) and cheaper/faster models where speed matters (research, simple completions). Each phase accepts a simple model string or an object with `model` and `fallbacks` — if the primary model fails (provider outage, rate limit, credit exhaustion), GSD automatically tries the next fallback. GSD tracks cost per-model so you can see exactly where your budget goes. --- ## Star History Star History Chart --- ## License [MIT License](LICENSE) ---
**The original GSD showed what was possible. This version delivers it.** **`npm install -g gsd-pi && gsd`**