Your coding agent can’t close a ticket until its tests pass.

Aidelix is a ticket tracker for Claude Code and other MCP agents. The agent records each phase of the work on the ticket. When it skips one, the API refuses the move and tells the agent what’s missing.

Start free See pricing

Free for up to 5 people. No card.

complete_phase  HBR-42  green
409 gate_blocked
Every test named in red must appear in green
as passing.

gate            green_tests
unmatchedTests  search-keeps-parcels-without-carrier
remedy          Make these tests pass, then call
                complete_phase for green again.

The reply an agent gets on HBR-42, in the made-up Harbor project, when it marks green with a red test still failing.

The Harbor board at Tidewater Labs: tickets in To do, In progress, Blocked, In review and Done, each card with its agent and phase progress, and two cards waiting on a blocking question.

What the gates check before a ticket moves

Tests: The agent names its failing tests in the red phase. The ticket stays open until each of them passes in green.
Phases: Each ticket type has phases it must record. A bug needs a failing test before the fix. You can waive a phase, and the ticket keeps your reason.
Questions: When the agent needs a decision from you, it asks on the ticket. A blocking question holds its phase until someone answers.

How it works

Connect your agent
Give Claude Code, or any MCP client, a key that acts for you. The ait command-line tool uses the same key.
The agent works the ticket
It claims a ticket and records its phases in order:
refineresearchplanredimplementgreenreview
The API checks each move
A refused move names the gate and the fix, so the agent can go back and do the missing step.
You review the ticket
A closed ticket carries a seal: PROVED, WAIVED 1, REFUSED or BY HAND. The seal reports what the gates enforced.

Your lane and the agent’s, on one ticket

The ticket shows what you asked next to what the agent found, its plan, the tests that failed and then passed, and the questions it asked. The agent can add records but can’t edit old ones.

Read about the work log

The work log of ticket HBR-42 at Tidewater Labs: Maya Okafor's lane beside Claude Code's, showing its second attempt through research, plan, red, implement and green.

Review the pull request, change by change

Aidelix splits a pull request into the changes it makes and flags each one green, yellow or red. Rules decide the floor, so the model never marks a migration or an auth file green. Read the red ones line by line, approve the rest, and start a findings run when you want a second reader on the risky lines.

Read about code review