Interlint runs the checks your project **already has**, such as ArchUnit, inside the agent's session. When the agent breaks a rule, it hears about it right away and fixes it in the same session, not in CI and not by hand.

**Works with [Claude Code](docs/claude-code.md) and [OpenCode](docs/opencode.md)**, on Maven projects that use ArchUnit, Checkstyle or PMD.

**Status:** 1.4.2. Stable for Maven projects, including multi-module projects and workspaces of several projects.

The problem

Your code rules live in two places that never meet:

• As text in AGENTS.md. The agent may forget it, and nobody enforces it.
• As checks (ArchUnit tests, Checkstyle, PMD). The agent only hears about them when someone builds or CI fails.

By then the agent's session is over, and someone has to fix the code by hand.

What Interlint does

• After each edit, fast checks run and any violation goes straight back to the agent. This needs `mvnd`.
• At task end, the full checks run, for the projects the agent changed. If a rule is broken, the agent cannot finish until everything is green.

This is what the agent sees when it puts infrastructure code in the domain:

✗ architecture · ARCH-01: domain depends on nothing outside domain

  Method  calls constructor ()> in (Order.java:27)
    at src/main/java/com/acme/domain/Order.java:27

Fix these problems before continuing.

The agent reads the rule, removes the dependency and carries on.

Why teams use it

• No new rules to write. Interlint has no rules and no analysis engine of its own. Your existing checks stay the single source of truth.
• Deterministic. Your own build decides, not a prompt the agent may ignore