Keep reviews close to the code
Review works best where the work happens. Coldtea keeps editor context, session history, and feedback in one place.
A review is only as good as the context around it. Pulled into a separate tab, away from the editor and the session that produced the change, it turns into guesswork.
Coldtea keeps review next to the work. The diff, the editor, and the agent session that wrote the code sit in the same workspace, so a reviewer can see not just what changed but how it came to be.
Feedback that goes somewhere
Comments left on a change are not just notes. They route back to the agent that owns the branch, which can address them and push an update without a human relaying the message by hand.
Close the loop
When checks fail after a merge, that signal comes back into the same workspace too. The goal is not another review tool, but keeping the whole loop in one place from prompt to merge.