Agents now review code against your repository's rules

Coding tasks now get a code review against your repository's rules before the work reaches you. When an agent finishes a change, Task Machine scans the added lines for violations such as a test with no assertions or an error handler that catches everything, and the same agent fixes each finding or explains why it does not apply. We built it because repository conventions were where agent-written code drifted most, and catching them by eye in every pull request took more of your review time than the change deserved.

Every changed line is checked against your rules

Each repository starts with a built-in rule set that covers security, correctness, maintainability, failure handling, and test quality. A rule is a yes or no question about the added lines, such as whether a new test makes any meaningful assertion about the behavior under test. The scan covers committed changes, tracked edits, and new files since the work branched from your default branch, so it can run while the pull request is still a draft.

Agents fix findings in the same run

When the scan reports a violation, the implementing agent receives the rule, the question, the file, and the flagged lines. It fixes the code or dismisses the finding with a written reason, for example that a neighboring guard already covers the behavior. A finding counts as fixed only after a rescan stops reporting it, and one task gets an initial scan plus up to five fix rounds. A clean scan hands the task on without starting an agent.

Your rules, approved from the Inbox

Agents can read a repository and propose rules specific to it, such as how your team stores money amounts or writes database migrations. Each proposal reaches your Inbox with its question, its reason, and the files it came from, and you approve or reject it there. You can also add a custom rule or switch off a default one yourself under the repository's Review rules. Task Machine tests every new rule against example code before it can run automatically.

Open findings stay visible to your review

If findings remain after the last fix round, the task continues to review with those findings attached, and the Inbox shows them beside the approve, reject, and request changes actions. A review that ran out of fix rounds never claims the code passed.

Code review covers engineering tasks that have an agent implementer and a connected repository. It adds to pull-request review, the agent's own pre-review, and your final decision. See Reviews for how the checks fit together.