Skip to main content
GSD Pi preferences live in a YAML-frontmatter markdown file that you can edit directly or manage through the interactive wizard. Global preferences apply to all projects on your machine, while project-level preferences apply only to the current project and take priority over global values. This gives you a sensible baseline for all work with per-project overrides when needed. Open the interactive preferences wizard from inside a GSD session:

Preferences File Format

Preferences use YAML frontmatter in a markdown file. Everything between the --- delimiters is parsed as YAML; any markdown below is ignored by GSD but useful for your own notes.

Merge Behavior

When both a global and a project preferences file exist, GSD merges them with these rules:
  • Scalar fields (e.g., budget_ceiling, token_profile): the project value wins if set
  • Object fields (e.g., models, git, auto_supervisor): shallow-merged, project overrides per-key
  • Array fields (e.g., always_use_skills, custom_instructions): concatenated, global first then project

Model Settings

Control which LLM model GSD uses for each phase of the auto-mode pipeline.
Use the provider/model format to target a specific provider (e.g., bedrock/claude-sonnet-4-6). Add a fallbacks list to continue automatically if a model is unavailable:

Token Profile

token_profile coordinates model selection, phase skipping, and context compression in one setting:

Planning Depth

Controls how much upfront discovery runs before milestone planning:
Use deep for complex greenfield projects. Enable it for a specific project with /gsd new-project --deep rather than setting it globally.

Budget and Safety

Auto-Mode Supervision Timeouts

GSD sends a “wrap up” signal at the soft timeout, detects stalls at the idle timeout, and pauses the session at the hard timeout if recovery steering can’t make durable progress.

Notifications

On macOS, install terminal-notifier for reliable notification delivery: brew install terminal-notifier. Without it, GSD falls back to osascript, which may not have notification permissions in System Settings.

Custom Instructions

Durable instructions that GSD appends to every session prompt. Use these for project-wide coding standards or conventions you want the agent to follow consistently.
For project-specific knowledge that evolves over time — architectural patterns, lessons learned, recurring pitfalls — use the GSD knowledge system (/gsd knowledge rule) instead of custom_instructions. Knowledge entries are memory-backed and selected contextually; custom_instructions appear in every prompt regardless of relevance.

Skill Routing

Control which skills GSD uses during auto mode. Skills are optional extensions that provide domain-specific behavior.

Skill Discovery

Full Example