regin

A workbench for building software with AI coding agents.
Plan the feature, run the agents, see what they did, count what they got wrong.

🌐 regin.ccday.top — the official project site.

⚠️ Early beta. regin is under active development and breaking changes are expected at any time. Database schemas, settings keys, hook contracts, skill bundles, and CLI flags may all change without backward-compatible shims. Pin a commit if you need stability.

regin runs one loop around the coding agent you already use:

Spec  →  Run  →  Watch  →  Count
 │        │        │         └─ defects declared against the done-claim; rounds-to-done per feature
 │        │        └─ every session traced: tools, edits, tokens, time, grades
 │        └─ task runs launched on Claude or Kimi, steered and stopped from /live
 └─ a feature row carries the spec, its acceptance tests, and the slices cut from it

It is organized in four layers. The first two are where you spend the day; the last two make the runs inspectable and keep the agent on-spec.

Workbench — features, tasks, defects

A feature is a row. Its spec lives on that row (or on its tracker issue when the feature is tracked remotely), and its acceptance items are named tests in the repo — red before the build, green at ship. The spec is cut into slices; each slice becomes a task with its dependencies, and tasks run in dependency order. When the work is called done, that is a done-claim, and anything found wrong afterwards is a defect declared against the feature.

The number the pipeline is held to is rounds-to-done: one build plus each time a done-claim was walked back. Only declarations feed it — nothing is inferred from prose, branch names or timing.

• Dashboard: /overview is the Pipeline — Overview, Features and Tasks behind one tab strip; defects are reached from the Overview and the Features triage rail. /features/:id is a feature's ledger.
• CLI: regin feature (where a feature stands and what it cost), regin task (capture, inspect, check a slice table); runs are armed and launched from the dashboard, regin defects (what a feature got wrong, and what escaped).
• Internals: Feature pipeline, and docs/defect-task-feature.md for how the three join.

Runs — launch, steer, hear back

A task is armed with a provider, a model and a launch mode, then started from the dashboard. Claude runs go through the Python Claude Agent SDK, so regin owns the process and keeps a typed channel to it — an AskUserQuestion is answered from the browser rather than by typing into a terminal. Kimi Code runs over ACP or in a tmux pane on regin's own tmux server.

• /live follows a running session: its current state, recent steps, any question it is blocked on, with steer and Stop.
• Agent bridge — a guarded channel that relays a prompt or steering message into a live session's terminal. Off by default; see docs/setup.md.
• Inbox — agents report progress, results and lessons through the send_to_user tool; messages land in /inbox and can fan out to a webhook, Telegram or Lark. CLI: regin messages, regin bridge.
• Mobile card — experimental. /live renders a phone-sized card that can answer permission prompts while you are away from the desk. Rough edges and breaking changes are expected; see docs/agent-bridge-design.md.

Internals: Agent SDK tier, Provider launch capabilities, Agent Messages.

Observability — what the agents actually did

Hooks and transcripts produce a stream of events: tool calls, model thoughts, file edits, hook decisions, token usage. regin ingests that stream into a session trace you can filter by tool, agent and phase, replay, and roll up (tokens by tool, skill reads, MCP calls).

• /trace/sessions lists sessions; each opens into a timeline and a conversation view.
• regin stats time shows where build time goes (attended vs. agent vs. human); regin stats session <trace-id> ranks why one session was slow; regin stats sessions exports per-session rows.
• regin grade scores finished sessions against a rubric. /audit is the ops history of regin itself.

Internals: Turn & Token Tracing, Session Grader.

Guidance — what steers the agent

The supporting layer: what the agent is told before it acts, and what pushes back when it drifts.

• Patterns & skills — local procedure guides for recurring implementation shapes, deployed into the active provider's skills directory; regin pattern promote packages a proven pattern as a versioned skill. Dashboard: /patterns, /skills.
• Rule engines — GritQL, Radon and bundle checkers wired into PostToolUse hooks, so a violation is reported to the agent in the same turn as the edit. Dashboard: /rules; CLI: regin rules, regin hooks.
• Agent memory — lessons captured from past sessions, ranked, consolidated and superseded as they go stale, then recalled into later sessions when they match the task. Dashboard: /memory; CLI: regin memory.
• Topic wikis — per-repo knowledge as a reviewed graph of topics; an agent proposes drafts, you approve them, and drift detection flags pages whose files have moved on. Dashboard: /repos/:name/topics; CLI: regin topics, regin wiki.

Internals: Patterns, Rule engines, Agent Memory, docs/topics/proposals.md.

Quick start

git clone https://github.com/caiuswang/regin && cd regin
./scripts/setup.sh                       # needs Python ≥ 3.11 and Node; asks to wire the Claude Code hooks
.venv/bin/python cli/regin.py serve      # dashboard on http://localhost:8321

• Windows — run .\scripts\setup.cmd instead (PowerShell or cmd; ./scripts/setup.sh there only opens the file in an editor), then regin serve in a new terminal. Same steps, except the live-session terminal and agent bridge, which need tmux. See docs/setup.md.
• Hooks — setup offers to wire them; otherwise run regin hooks install --provider claude. Without them no session is recorded.
• Upgrade — git pull && ./scripts/setup.sh; it keeps your database, settings and users and runs regin migrate.
• Uninstall — regin uninstall (--dry-run to preview, --purge-data to drop data too), then delete the checkout.

Manual setup, settings, server mode and the CLI reference: docs/setup.md.

Supported agents

What regin is not

Not a chat UI, not a model, not a hosted service. It assumes you already have a coding agent and a codebase, and runs locally beside them.

Acknowledgements

• Qoder Repo Wiki — inspiration for the per-repo topic wiki design.
• SkillRouter — inspiration for embedding-based skill/pattern routing.
• GritQL — the query language powering regin's grit rule engine.

Further reading

• docs/setup.md — install, configuration, modes, Kimi task runs, CLI reference, troubleshooting.
• ARCHITECTURE.md — system internals, module layout, each subsystem's contracts.
• CONTEXT.md — the glossary: what a feature, a plan and "done" mean here.
• docs/spec-notation.md — the notation regin specs are written in: types, state machines, decision tables and invariants instead of prose.
• docs/defect-task-feature.md — how a defect, a task and a feature join.
• docs/topics/proposals.md — topic graph proposals via external tool-using agents.
• docs/topics/multi-user.md — sharing approved topics across users via git without a shared database.
• website/README.md — the standalone Vue 3 marketing/docs site.
• CLAUDE.md — instructions for AI agents working in this codebase.