Ícaro Galvão
Senior QA Engineer · AI Agents
I build devin-* — twenty local-first tools that turn Devin's own session data into backups, search, metrics, memory and QA. No cloud, no telemetry, nothing to sign up for.
Ecosystem
About
Senior QA Engineer, post-graduated in Software Testing and Software Engineering. I work at the intersection of quality engineering and developer tooling — and I spend my open-source time building instruments for the thing most agent platforms leave opaque: their own local data.
The devin-* ecosystem is that work in public: twenty MIT-licensed, local-first utilities for the Devin CLI — diagnostics, history export, backup, metrics, memory, evaluation and a calibrated decision layer that runs on Devin's own model. Every tool is read-only by default, documented in English and Portuguese, and works with no VM, tunnel or extra services.
See it live
Selected work
devin-internals-spec
Understand the system — Devin's store internals documented: schema detection, typed parsers, fixtures.
01 · understand · ★1 · v0.1.0devin-qa-pack
Verify the agent — claims vs. reality, reported as PASS / PARTIAL / UNVERIFIED.
02 · verify · ★1devin-evals
Measure the agent — replay recorded sessions against rubric graders, deterministically.
03 · measure · ★1devin-bridge
Control the agent — policy-gated ACP client with allow / deny / ask rules.
04 · control · ★1poordjaevin
Judge the decision — calibrated answer layer; ECE 0.170 → 0.071 through Devin's own model via ACP.
05 · judge · ★1 · v0.1.0Insight
devin-doctor
brew doctor for a Devin install — stores, locks, config, disk → concrete fixes.
diagnostics · ★1 · v0.1.0devin-history
Session history → Markdown, JSON, CSV, Obsidian-ready.
export · ★1 · v0.1.0devin-pm
Project manager over sessions — rollups, milestones, status reports.
reporting · ★1Safety
devin-backup
Snapshot, verify, restore, rotate — with schema-version manifests.
backup · ★1devin-redact
Secret/PII redaction that understands tool-call semantics, in-place in SQLite.
security · ★1devin-metrics
Cost, tokens, sessions per project/model/day — local only.
analytics · ★1Memory & recall
devin-graph
Knowledge graph — sessions ↔ projects ↔ files ↔ tools.
graph · ★1devin-search
FTS5 full-text search across every session.
search · ★1devin-memory
Anti-poisoning memory — provenance, versioning, quarantine.
memory · ★1Ops
devin-janitor
Session lifecycle — export-then-delete, tiered, dry-run first.
automation · ★1devin-orchestrator
Background-worker fan-out — deterministic planner, caps, no nesting.
orchestration · ★1devin-powerups
Maintainer hub — registry, scaffolder, weekly reports.
meta · ★1Related
devin-office
Live Devin activity as an animated SVG circuit board — sessions, subagents, tools.
dashboard · ★1 · v0.1.0qwenpaw-suite
Optional add-on — Ollama ↔ OpenAI bridge for self-hosted model operators.
optional · ★1awesome-devin
Curated list of Devin resources and the devin-* open-source tooling ecosystem
new · ★1Why devin-*?
Where does the Devin CLI store its session data?
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.
How do I export Devin sessions?
devin-history reads the sessions DB and exports Markdown, JSON or CSV — including Obsidian-ready notes.
How do I back up and restore Devin's local data?
devin-backup snapshots the stores with schema-version manifests, then verifies, restores and rotates them.
How do I remove secrets from exported history before sharing?
devin-redact understands tool-call semantics, not just plaintext patterns — redacting in place inside SQLite, with a .bak safety copy.
Can I run all of this on a locked-down corporate machine?
Yes — the whole catalog needs only the Devin CLI and Python ≥ 3.10: no VM, no tunnel, no model server, no Slack, no Obsidian. The only Node.js dependency is devin-bridge, an ACP client for the Devin CLI itself. An external runtime (hooks, scheduler, Slack) can recreate proactivity locally, but four losses are irreducible: wake-while-idle when the machine is suspended, remote reach without a notification channel, heavyweight offload to a VM, and multi-machine dashboard topologies without a tunnel.
Does any of this send telemetry or need an account?
No. Everything is local-only, read-only by default, and MIT-licensed. Nothing phones home; there is nothing to sign up for.