Statewright: state-machine guardrails so coding agents can't skip plan→test
At a glance
Show HN: Statewright's Rust engine enforces plan/implement/test states for Claude Code (and other CLIs) via MCP hooks—wrong tools are blocked structurally, shrinking death spirals for both small and frontier models. This workflow is listed under Agent-Harness, State-Machines, Claude-Code, Guardrails, MCP.
Adam keeps HA automations in git; Claude Code uses an MCP server to search entities, read traces, edit YAML, scp to the hub, reload, and commit—fixing a noisy camera automation in under two minutes.
Show HN: `npx subagent-reuse --setup` adds an MCP that scans ~/.claude/projects/, builds SHA-256 Merkle trees of files each subagent already read/modified, and route_task decides REUSE vs CREATE_NEW before spawn—structural overlap only, no embeddings; ~1k LOC JS + 52 tests.
Rust MCP server makes Claude Code the team lead over Claude/Codex/Gemini workers; Stop-hook + asyncRewake pushes replies (~50ms) into the lead session, with a local live team UI.
MCP server plus local hooks route agent-written commits, PR text, emails and support replies into one editable queue; you rewrite and approve, then the agent sends exactly your version—Claude Code tested; Codex/Gemini/Copilot/Cursor installer-configured; free tier then paid.