Infrastructure for AI coding agents

In local SQLite stores under ~/.local/share/devin/cli/ plus ~/.config/Devin/ on Linux, or %APPDATA%\devin\ and %APPDATA%\Devin\ on Windows. devin-internals-spec documents the schema and detection logic — sessions.db drift tracked through v18 plus the Desktop GUI stores — and ships deterministic synthetic fixtures.

devin-history reads the sessions DB and exports Markdown, JSON or CSV — including Obsidian-ready notes.

devin-backup snapshots the stores with schema-version manifests, then verifies, restores and rotates them.

devin-redact understands tool-call semantics, not just plaintext patterns — provider tokens, connection URIs and webhook URLs included — redacting in place inside SQLite with a .bak safety copy and an HTML diff report.

The DevKit-installable core can. Corporate Windows is an explicit local-only environment: no VM, no tunnel, no model server, no Slack, no Obsidian. The registry marks qwenpaw-suite unsupported there, and devin-control needs Node.js ≥ 20 because it is an ACP client for the Devin CLI itself. Heavy offload, wake-while-idle and remote reach remain outside the corporate guarantee.

No. Everything is local-only and MIT-licensed. Nothing phones home; there is nothing to sign up for. Inspection tools are read-only; the tools that write (backup, janitor, redact) do so explicitly and visibly.