DevOS

The system of record for engineering decisions. Your agents write the code — DevOS remembers why. It captures what your AI coding agents reasoned about and what your git history actually changed, links them into one decision graph per repo, and surfaces the relevant prior decisions when you (or your agent) start new work — so a settled call never gets silently re-litigated.

The derive store runs locally and privately by default in PostgreSQL 16. devos init provisions it and saves its DSN as DATABASE_URL; there is no SQLite or embedded fallback. Opt into TeamSync when you want teammates to share decisions.

Install

pipx install devos        # isolated CLI install (recommended)
# or
pip install devos         # into the current environment

Requires Python ≥ 3.11 and git. An LLM API key is needed only for the extract step (distilling decisions); capture and ingestion are free and need no key.

Quickstart

devos init

The interactive setup walks you through your model provider + key, provisions the local Postgres derive store, discovers the git repos you work on, and onboards the ones you pick — installing capture hooks and wiring each repo's agent (.mcp.json) in one pass. Then just work normally: DevOS captures git commits and agent sessions in the background.

Prefer one repo at a time, or scripting it?

devos setup                                   # onboard a single repo (enable + ingest + wire)
devos onboard-workspace --root ~/code --yes   # non-interactive bulk onboarding

What it does

• Captures two sources into one graph: AI-agent sessions (Claude Code, Codex, via a Stop hook) and git history (commits, changed files, committed docs, via a post-commit hook).
• Extracts decisions from those sources with an LLM, each traced back to the exact commit or conversation it came from.
• Surfaces a headstart — a task-aware primer of the relevant verified prior decisions, available to your agent over MCP or on the CLI.

Bring your own model

DevOS is provider-agnostic. devos init lets you pick one and stores the key in ~/.devos/.env:

Already have a key exported in your shell? DevOS uses it — an explicit export always wins over the stored file.

Team sharing (optional)

Beyond the solo local store, DevOS can sync a team's decisions into a shared backend so an agent recalls what a teammate already figured out. See devos team and devos teamsync.

Optional extras

(The MCP decision server ships in the base install — no extra needed.)

License

Apache-2.0. See LICENSE.