Home › Situations

Feedback the agent reads and answers

Reviewers pin comments to the screenshot. The agent reads them, fixes what was returned, walks the steps again and answers each comment with what changed.

The problem

Feedback lives in Slack threads, e-mails and calls, and the agent that should fix it never sees any of it.

Ask your agent

Go through the open Kaloko feedback on TASK-123: fix what reviewers rejected, run the affected steps again, share, and answer each comment with what changed.

The agent reads threads with kaloko feedback, replies with kaloko comment --reply and resolves them with the commit that fixed them.

What comes out

The run after the fix: the returned steps walked again, each comment answered.

LIVE · today 14:44 CEST · 7 of 11 passed · 7/11 steps · Open the live run ↗

• Failed

• OK

• OK

• OK

Waiting for a person· 2 Oct 2026· 36 screens· CS, EN

• OK passed or approved by a person
• Returned a person sent it back with a note
• Failed a check failed
• ? a person decides

Why it holds

• Comments where the problem is

  Pinned to a spot on the screenshot, per step, language and viewport, in threads. A step can be returned with a note.

• The agent picks them up

  The same list over the CLI, the API and the MCP server. Every write of an agent carries its name, so you know who answered.

• Closed with evidence

  Resolved with “Fixed in <commit>”; the next run shows the steps again for the reviewer to approve.

• Nobody has to chase

  The author gets an e-mail right away when a run is returned; everyone else a daily or weekly digest of what needs them.

Step-by-step guides