Skip to main content
Open Diffs to inspect code changes captured from agent Runs. You can also open an Issue’s Diffs section to find its captures.

​
Inspect a Run’s changes

Search diffs or filter by Project and Issue status, then open a diff. In Overview, read the summary, commits, reported tests, and activity. Test results identify whether they came from a verified receipt or were agent reported. If no tests were reported, Longoz says so; a diff alone does not show that the work passed checks. Open Files to inspect changed files. Narrow the view by commit, file category, or diff status. Some files have only basic details, such as binary files or changes omitted by capture limits. A Partial or Capture failed state means you do not have a complete captured diff to inspect. Each diff contains only that Run’s new commits. A later Run does not replace earlier captures. A Run with no new commit has no new Review. Use View this Issue’s Reviews to inspect earlier work before accepting the whole Issue.

​
Request changes

Add reply on a diff adds an Issue comment. It does not send instructions to the agent or dispatch work. To request rework, open the Issue, describe the required changes in its composer, and use Send changes when available. Be specific about the file or behavior and the expected result. For example:
The empty search result still shows the previous count. Clear the count when no results match, and add a check for that case.
Follow the Issue’s activity and next Run to see the response. Use Inbox to return to review notifications.

​
Accept the Issue

When the work meets its requirements, move the Issue from In review to Done using its status control or a permitted Board move. This accepts the work. There is no separate merge action on the diff page. For a repository-backed Project, marking the Issue Done starts integration into the Project base. Acceptance includes changes from every Run in the Issue. Routine Issues without a reviewer can reach Done automatically; assign a reviewer if you want to inspect them before integration. Read the integration notice after acceptance. Done and successful integration are separate states: Longoz can still be adding the changes, or integration can fail. If changes conflict with the Project base, reopen the Issue for the agent to resolve the conflict, then mark it Done again. For other failures, follow the notice to check permissions, the source Computer, or the repository binding. Changes that depend on earlier unaccepted work must wait for that work to reach the Project base. For delivered reports or other files, inspect Artifacts alongside the Issue’s requirements.