regin-lineage
Hands each subagent spawn's agentId, parent and launching tool call to regin, which uses it as the agent's parent instead of inferring one
newprocessagents
Hands each subagent spawn's agentId, parent and launching tool call to regin, which uses it as the agent's parent instead of inferring one
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 itIt 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.
| Layer | What it covers | Dashboard |
|---|---|---|
| Workbench | feature → spec → acceptance tests → tasks → done-claim; the defect ledger | /overview (Pipeline), /inbox |
| Runs | launching task runs, steering live sessions, the agent's messages back to you | /live, /inbox |
| Observability | session traces, time and cost analytics, post-hoc grades, audit | /trace, /audit |
| Guidance | patterns & skills, rule engines in hooks, cross-session memory, topic wikis | /patterns, /rules, /memory, /repos/:name/topics |
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.
/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./projects/:id holds a project's step stages, each stage's prompt, and the language its task runs write in.regin feature (where a feature stands and what it cost), regin task (capture, inspect, check a slice table, arm a run; runs are launched from the dashboard), regin defects (what a feature got wrong, and what escaped), regin workspace (add, list, remove).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 and CodeBuddy Code runs go over ACP or into 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.send_to_user tool; messages land in /inbox and can fan out to a webhook, Telegram or Lark. CLI: regin messages, regin bridge.regin MCP server — carries send_to_user and the pipeline's tools (features, tasks, defects), so any MCP-speaking agent can read and write the pipeline. regin mcp register wires it, with the memory server, into each provider's config./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.
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; its aspects and judge are configured under Settings → Grading. /audit is the ops history of regin itself.Internals: Turn & Token Tracing, Session Grader.
The supporting layer: what the agent is told before it acts, and what pushes back when it drifts.
regin pattern promote packages a proven pattern as a versioned skill. Dashboard: /patterns, /skills.PostToolUse hooks, so a violation is reported to the agent in the same turn as the edit. Dashboard: /rules; CLI: regin rules, regin hooks./memory; CLI: regin memory./repos/:name/topics; CLI: regin topics, regin wiki.Internals: Patterns, Rule engines, Agent Memory, docs/topics/proposals.md.
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.\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.regin hooks install --provider claude. Without them no session is recorded.git pull && ./scripts/setup.sh; it keeps your database, settings and users and runs regin migrate.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.
| Agent | Status |
|---|---|
| Claude Code | Full: hooks, rule engines, trace, memory, and task runs through the Agent SDK. |
| Kimi Code | Task runs only (ACP or tmux), with known limits — runs are unattended and a steer is cancel-then-re-prompt. See Run a task with Kimi. |
| CodeBuddy Code | Hooks, skills, MCP servers and transcript capture, plus task runs over ACP or tmux with a model and permission mode. |
| WorkBuddy | Hooks, skills, MCP servers and transcript capture; cannot be armed for task runs, and its sessions are not offered Resume. |
| Codex, generic | Provider adapters exist; cannot be armed for task runs. See Agent provider architecture. |
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.
hooks/register.ts 40 lines1import type { AgentSpawnInput, EngineInterface, Register } from 'claude-code'
2
3// Same resolution as regin-agents/bin/regin-mcp.sh: $REGIN_HOME, else ~/regin.
4async function reginHome($: EngineInterface): Promise<string> {
5 return (await $.env.get('REGIN_HOME')) || `${await $.env.get('HOME')}/regin`
6}
7
8async function report($: EngineInterface, e: AgentSpawnInput, agentId: string) {
9 const home = await reginHome($)
10 const session = await $.session.id()
11 const record = {
12 agentId,
13 parentAgentId: e.parentAgentId ?? null,
14 tool_use_id: e.tool_use_id || null,
15 subagentType: e.subagentType,
16 }
17 const { exitCode, stderr } = await $.process.run(
18 [`${home}/.venv/bin/python`, `${home}/cli/regin.py`, 'trace', 'spawn', '--session', session],
19 { cwd: home, stdin: JSON.stringify(record) },
20 )
21 if (exitCode !== 0) $.ui.log(`regin-lineage: trace spawn exited ${exitCode}: ${stderr}`, { to: 'debug' })
22}
23
24// The agent id exists only once core has started the agent, so the report
25// follows next(e). Without a record regin falls back to inferring the parent,
26// so a failed report is a debug line and the spawn's result passes on as is.
27export const register: Register = on => {
28 on('agent.spawn', async ($, e, next) => {
29 const started = await next(e)
30 if (started.agentId) {
31 try {
32 await report($, e, started.agentId)
33 } catch (err) {
34 $.ui.log(`regin-lineage: trace spawn failed: ${String(err)}`, { to: 'debug' })
35 }
36 }
37 return started
38 })
39}
40