MYRRAZOR

Tickets are Markdown, history is an append-only event log, and SQLite is a rebuildable index. The work stays with the repo. Leases and review gates make ownership explicit when several agents work at once. Agents use CLI help or MCP tools to find work, claim tickets, and update status with machine-readable results.

Loop state, queues, and saved artifacts live in Markdown and JSONL files. Planner, implementer, reviewer, and QA roles can use different coding agents, with CLI and MCP tools advancing the same queue. Implementation gates and project-scoped human decisions make handoffs explicit.

Eight Python plugins share a local CLI and a browser hub bound to localhost. They profile files, replace detected PII, generate seeded demo data, compare datasets, and check drafts and AI workload specs. JSON reports support agent workflows, while Netwatch can observe and gate HTTP connections through a local proxy.

A loopback-only broker checks token scope and policy before decrypting a provider key and attaching it to an outbound request. Apps hold Locker tokens instead of raw provider keys in proxy mode. Private pre-release; there is no public installable release, and it is not ready for production secrets.

A local daemon connects the browser to durable tmux sessions, so closing a tab leaves the underlying work running. One device controls a session while others can observe. Private remote access uses Tailscale Serve, with application login still required. The project is in pre-release.

Markdown taste files guide a local Python CLI that compares candidate outputs and records its choices in JSONL. Coding agents can call the CLI, and opted-in session history can propose taste rules for review. The current critic uses inspectable lexical rules; it remains an experiment in output selection.