AI Dev Workspace

Switch between Claude Code and Codex without re-explaining your decisions. Your assistant remembers work between sessions in Markdown you own. It keeps decisions, the next step and what not to retry, and warns when files it names changed or disappeared. Try it before connecting a repo: ws demo · 5-minute tutorial · remove it

Quick start

pipx install ai-dev-workspace --pip-args='--pre'  # beta; omit --pip-args after a stable release
cd ~/code/myapp && ws start

Without pipx: python3 -m venv ~/.local/share/ai-dev-workspace && ~/.local/share/ai-dev-workspace/bin/pip install --pre ai-dev-workspace; put its bin directory on PATH before ws start. Prefer a Claude Code plugin? See the plugin preview.

Example

Session 1 — You: “Empty email returns missing_email; leave signup unchanged.”
Assistant: “I’ll trace login and keep the decision with this task.”
You: “Stop here; I’ll resume tomorrow.”
Session 2 — You: “Continue the login fix.”
Assistant: “The saved note says return missing_email and leave signup unchanged.”
You: “Yes, continue.”

Results (small synthetic samples, not general productivity)

Later Codex → Codex runs (n=5 each) were less favourable: the workspace passed 1/5 and 2/5, while a plain HANDOFF.md control passed 4/5 and 5/5. See bench/README.md.

Team sharing

Your notes stay private. Share only what you approve, and your teammates' assistants start with it: after ws start, ws team init <private-repo> --attest-private (--yes in scripts) · ws know add "Payments API rejects floats" --category domain --team · ws sync. A teammate runs ws team link <private-repo>; their next brief shows the note, labelled as shared team context, and their own decisions still win. Team quick start

Compatibility

Testers on Cursor, Copilot (VS Code), or Gemini CLI: please share problems through Something broke. · Overview · Setup · Commands · Keeping corrections · Measurements · Client verification · Packs · Team use · Windows · Roadmap · License