Give agent-written code a second review

Coding tasks can now get a second review after passing your repository's rules. Two independent reviewers look for defects across the changed code, such as a retry that can charge a customer twice or a changed function that breaks its caller. We added this because a change can follow every repository convention and still fail when its parts run together.

Review a claim with a way to reproduce it

Each finding includes the file, changed lines, what the reviewer thinks is wrong, and the input or steps that should trigger the defect. When both reviewers identify the same defect, it becomes a blocking finding. A claim from only one reviewer appears under Potential findings and does not block submission.

The implementing agent checks the reproduction steps before changing the code. It fixes a confirmed defect or dismisses a false positive with a written reason. Later rounds with a clean rule scan check whether the open findings still hold instead of starting another search. If findings remain after the fix limit, they accompany the task into your Inbox for your decision.

Use it for sensitive work or from the terminal

For coding tasks, the second review runs when the approved plan calls for the deepest review or marks the work as highly sensitive. Running tama code-review yourself requests it after every rule scan without blocking findings.

The second step depends on reviewer availability for your workspace region and on the size of the change. It can still miss defects or raise a false positive, and it adds to your tests, pull-request review, and final decision rather than replacing them.

Read Reviews for the task review flow and the CLI reference for tama code-review.