SOBA is a local-first engineering agent for teams that want more than code edits. It remembers the project, works inside bounded tool loops, verifies outcomes, and turns work into evidence.
01Execution model
Local control, visible proof, repeatable habits.
SOBA keeps memory, tools, MCP, skills, sessions, capsules, and proof receipts in the same local workflow.
Read
Looks at code, docs, session state, memory receipts, and MCP context first.
Do
Edits through bounded tools, skills, shell checks, and MCP integrations.
Prove
Maps checks, claims, risks, and permissions into a visible proof trail.
02SOBA / DIFFERENCE
What makes SOBA different
Evidence-first finishes
Proof receipts map changed files, checks, claims, risks, and permissions to the final answer.
Session time machine
Continue, rewind, branch, and inspect past turns without losing the work trail.
Portable handoff capsules
Capsules keep goals, decisions, files, risks, and next steps compact enough to resume elsewhere.
Memory with provenance
Project facts can carry source files, verification time, confidence, and stale-if-changed rules.
MCP without losing control
Connect stdio or Streamable HTTP servers while SOBA keeps permissions and tool results visible.
Permission receipts
Risky operations show scope, alternatives, and the decision that allowed or denied them.
Skill evolution lab
Markdown skills have evals, bench, trace, revision history, promotion, and rollback.
Three languages
English, Russian, and Chinese UI/docs, with release messaging kept aligned.
03TUI preview
A terminal surface for verifiable work
Use one-shot prompts for small tasks or the TUI for long work. Slash commands, model switching, proof summaries, memory, permissions, and MCP status stay visible.