Skip to content

Captures & Triage

Introduced in v2.19.0

Captures let you fire-and-forget thoughts during auto-mode execution. Instead of pausing auto-mode to steer, you can capture ideas, bugs, or scope changes and let GSD triage them at natural seams between tasks.

While auto-mode is running (or any time):

/gsd capture "add rate limiting to the API endpoints"
/gsd capture "the auth flow should support OAuth, not just JWT"

Captures are appended to .gsd/CAPTURES.md and triaged automatically between tasks.

capture → triage → confirm → resolve → resume
  1. Capture/gsd capture "thought" appends to .gsd/CAPTURES.md with a timestamp and unique ID
  2. Triage — at natural seams between tasks (in handleAgentEnd), GSD detects pending captures and classifies them
  3. Confirm — the user is shown the proposed resolution and confirms or adjusts
  4. Resolve — the resolution is applied (task injection, replan trigger, deferral, etc.)
  5. Resume — auto-mode continues

Each capture is classified into one of five types:

TypeMeaningResolution
quick-taskSmall, self-contained fixInline quick task executed immediately
injectNew task needed in current sliceTask injected into the active slice plan
deferImportant but not urgentDeferred to roadmap reassessment
replanChanges the current approachTriggers slice replan with capture context
noteInformational, no action neededAcknowledged, no plan changes

Triage fires automatically between tasks during auto-mode. The triage prompt receives:

  • All pending captures
  • The current slice plan
  • The active roadmap

The LLM classifies each capture and proposes a resolution. Plan-modifying resolutions (inject, replan) require user confirmation.

Trigger triage manually at any time:

/gsd triage

This is useful when you’ve accumulated several captures and want to process them before the next natural seam.

The progress widget shows a pending capture count badge when captures are waiting for triage. This is visible in both the Ctrl+Alt+G dashboard and the auto-mode progress widget.

Capture context is automatically injected into:

  • Replan-slice prompts — so the replan knows what triggered it
  • Reassess-roadmap prompts — so deferred captures influence roadmap decisions

Captures always resolve to the original project root’s .gsd/CAPTURES.md, not the worktree’s local copy. This ensures captures from a steering terminal are visible to the auto-mode session running in a worktree.

CommandDescription
/gsd capture "text"Capture a thought (quotes optional for single words)
/gsd triageManually trigger triage of pending captures