Review-Driven Workflow

Kavi's review system is more than code comments — review threads can directly drive agent behavior through follow-up tasks.

Adding Review Notes

From the Tasks view (3), navigate to a completed task and cycle through changed files (,/.) and hunks ({/}). Then:

Assignees

Review threads can be assigned to:

• codex — Codex should address this
• claude — Claude should address this
• operator — You'll handle it yourself

Press a to cycle the assignee on a thread.

Converting to Follow-Up Tasks

The most powerful feature: press F on a concern thread to automatically create a follow-up task assigned to the appropriate agent.

The follow-up task includes the review context, the specific diff hunk, and the concern text — giving the agent full context for the fix.

Thread Lifecycle

Open → Resolved → Landed
         ↑          ↓
         └── Reopened (on reply)

• Threads start open when created
• Mark as resolved with R or let them auto-resolve when the follow-up task completes
• Resolved threads become landed after kavi land
• Replying to a resolved thread reopens it

Special Dispositions

• Press w to mark a thread as won't fix — acknowledged but not acting on it
• Press x to mark as accepted risk — known issue, consciously accepted

Filtering Reviews

In the TUI:

• u — Cycle assignee filter
• v — Cycle status filter
• d — Cycle disposition filter

From the CLI:

kavi reviews --assignee operator --status open
kavi reviews --disposition concern --agent codex

Workflow Pattern

1. Agent completes a task
2. You review the diff in the Tasks view
3. Add concerns where needed (C)
4. Queue fix tasks from concerns (F)
5. Agent addresses the concerns
6. Review threads auto-resolve
7. Land when all threads are resolved