Git. Ship.Done. forAI-assistedengineering.

Open GSD keeps agentic work from dissolving into context bloat: explicit plans, clean execution contexts, real verification, and git history that tells the truth.

Standalone CLI
Framework
Read the docs
Built for agentic engineering

From intent to shipped, without losing control.

GSD is not another chat prompt. It is an operating loop for getting useful work out of AI coding tools without losing scope, state, or verification.

Explicit plans

Structured task graphs keep agents aligned and auditable.

Clean execution contexts

Right-sized context for every step. No bloat, no drift.

Real verification

Automated checks and human-readable evidence you can trust.

Choose the surface. Keep the loop.

Use the framework where you already work, the CLI when you want orchestration, the desktop app when you want visible state, and the cloud when project state needs to follow you.

Browse docs
Framework

gsd-core

Drop the GSD loop into Claude Code, Codex, Gemini CLI, Cursor, Windsurf, Copilot, or another existing runtime.

Standalone CLI

gsd-pi

A terminal-native harness for autonomous milestones, context hygiene, worktrees, checks, cost, and recovery.

Native UI

gsd-workbench

Coming soon

A local desktop workspace for projects, threads, plans, backlog, evidence, and ship handoffs.

$Desktop app, download coming soonComing soon
Hosted cloud

gsd-cloud

Coming soon

A managed workspace for cross-device project state, remote milestones, and team visibility.

$Hosted cloud, coming soonComing soon

Browser proof lives beside GSD.

gsd-browser is the companion product for deterministic Chrome control: MCP tools, semantic actions, assertions, recordings, traces, visual evidence, and human takeover when the work calls for it.

View gsd-browser
verification backend@opengsd/gsd-browser
Snapshot refs
@v12:e7
Assertions
pass
Evidence
trace.har
Viewer
takeover ready

$ gsd-browser mcp

navigate → snapshot → act → assert → export

What changes when GSD is doing its job.

01

Context stops rotting

Heavy research, planning, and implementation work happen in scoped contexts instead of one exhausted session.

02

State survives

Plans, current position, decisions, and handoffs become durable project artifacts the next run can load.

03

Verification has teeth

The work is checked at the behavior level, evidence is captured, and failures turn into actionable repair plans.

Built in the open, with receipts.

The roadmap, docs, promise, and community stay visible because trust is part of the product. Push back, test the tools, and help shape the next surface.

public trail
Nowgsd-pi trust and recovery work
NextWorkbench project state and guided planning
ThenHosted continuity across devices