Guardrails to stop AI coding agents from looping

What to build

A lightweight CLI/CI tool or IDE plugin for solo devs and small teams that lets you write simple specs/invariants (e.g. 'this function must never mutate X', 'API contract must match schema Y') and automatically checks AI coding agent diffs (from Claude Code, Cursor, Copilot, Windsurf) against them before the change lands, blocking or flagging violations pre-merge.

AI coding agents frequently loop through costly rework when they silently break existing contracts; a cheap pre-commit guardrail that checks agent diffs against a few hand-written invariants could catch this early without requiring full formal verification.

Demand

Developers running heavy agentic coding workflows (Claude Code, Cursor, Copilot, Windsurf users) are hitting repeated agent failures on the same task and are actively looking for ways to stop agents from re-breaking things; the Show HN post surfaced this pain directly.

• Hacker News (Show HN post)News

  Show HN: AxiomCode Graph, Reducing coding agent rework with formal methods — 10 points, 8 comments on HN.

• Opportunity brief (internal signal analysis)Analysis

  Internal framing identifies target users as developers/teams running heavy agentic coding workflows who are frustrated by repeated agent failures on the same task.

Stack

• Tree-sitter (for lightweight static parsing of diffs)
• Claude Code hooks / Cursor rules API
• GitHub Actions (CI gate)
• SQLite or JSON for spec/invariant storage
• Python or TypeScript CLI framework (e.g. Commander, Click)

Solo + AI difficulty

Easy to ship a v0 that checks simple, user-authored invariants (e.g. 'file X must not import Y', 'function signature must not change') against agent diffs via regex/AST rules in a pre-commit hook or CI gate — doable in a few days. Hard part is generalizing beyond narrow rule types into anything resembling real formal verification, and getting users to actually write specs upfront; expect 1-2 weeks to a usable MVP if scope stays to lightweight invariants rather than full formal methods.

Entry threshold

No capital or licensing needed, but requires enough technical depth to express useful lightweight specs or invariants; a focused version (not full formal verification) is buildable solo in a few weeks using existing LLM and static-analysis tooling.

Window

6-12 months

Where to find first users

• Show HN launch
• r/ClaudeAI and r/cursor subreddits
• Indie hackers / Twitter dev communities posting about agentic coding pain
• Direct outreach in Claude Code / Cursor Discord servers

Counter-signals & risks

• Formal methods and invariant-checking tools have historically faced adoption friction due to the upfront cost of writing specs, which may offset time saved on agent rework.

• Major coding agent vendors (Anthropic, Cursor, GitHub Copilot, Windsurf) could build similar guardrail/verification features natively into their platforms, eliminating the need for a third-party layer.

• A single Show HN post with no historical match or track record provides weak validation that the approach generalizes beyond a narrow demo use case.