Yomiracle/trinity-lite

**Local AgentOps for cross-vendor CLI coding agents. Route work, recover state, and accept only with evidence.**
Trinity Lite is a local control plane for Codex, Claude Code, Hermes, and custom
CLI agents. It connects the tools you already use; it does not ask you to
rebuild them inside another framework.
中文 README · Docs · Why Trinity Lite? · Recipes
The problem
You already use more than one capable coding agent. The hard part is no longer
starting another agent; it is preserving task truth across tools, recovering
after a client disconnects, preventing duplicate work, and deciding when a
result is actually accepted. Trinity Lite is that local operations layer.
What it does
- **Route by capability, not name.** You describe the task. The router matches it to the right agent — no hardcoded agent names, no fragile dispatch logic. *"Implement a rate limiter" lands on the agent you tagged implement. "Review the auth module" goes to the agent tagged review.*
- **Give every agent a pull queue.** Workers read pending tasks from the shared bus, execute them via CLI, and write results back. Each agent polls on its own schedule. You never copy-paste an output between terminals again.
- **Remember every decision.** Every task, status change, result, error, and inter-agent message lands in a local SQLite database. Query who did what, when, and what happened — without setting up a logging pipeline.
- **Review, verify, then accept.** orchestrate runs primary work, routes the required review, runs local verification, and writes acceptance evidence back to SQLite.
- **Block footguns before they fire.** Self-routes become explicit local-work decisions instead of creating loops. Delegation depth has a hard cap. Working directories must be in the allowlist.
Quick start
30 seconds, no agents required:
Mock agents are built in. You see the full route → work → review → verify → accept cycle before you wire up anything real.
Not another framework
Trinity Lite does not build agents. It operates the agents you already have.
LangGraph and CrewAI give you primitives for building agents from scratch — graph definitions, role abstractions, and tool wrappers. Trinity Lite starts from the opposite end: Claude Code is running in one terminal, Codex is running in another, and their work needs reliable handoff, recovery, independent review, and an acceptance trail. No new agent abstraction. Just local AgentOps for the CLIs you already use.
Who this is for
| You are... | Trinity Lite helps you... |
|------------|---------------------------|
| An advanced solo developer using two or more agent CLIs | Replace manual terminal handoffs with one durable workflow and evidence trail |
| A small AI-native engineering team | Separate implementation, review, verification, and acceptance without deploying a control server |
| A local-first or privacy-sensitive developer | Keep task state in an inspectable SQLite database on your machine |
| An agent-tool integrator | Connect existing CLIs through a neutral bus and MCP surface |
Features
- **Route by capability.** Tag agents with implement, review, audit — the router matches tasks to the agent that can do them. No agent names in your dispatch logic.
- **Dispatch directly when you need control.** Bypass the router and send a task straight to claude_code or codex. Best of both worlds.
- **Persist everything in SQLite.** Tasks, statuses, results, errors, and messages in one local file. Query it with sqlite3 or any tool that speaks SQL.
- **Accept with evidence, not vibes.** The review flow records route decisions, review links, verification results, acceptance reasons, and accepted_at in SQLite. A reviewed task is accepted only after the local verifier passes.