Oyo

Oyo scopes reviews to your current Git worktree or jj workspace. You can use the -t or --target flag to explicitly select which diff or branch you are reviewing. If no target is specified, Oyo prefers the current branch's local PR review, falling back to the working tree.

Git Targets

• Working Tree: oy or oy review status -t @
• Staged Changes: oy --staged or oy --staged review status
• Branch/Feature: oy feature or oy review status -t feature
• Pull Request (Range): oy --range main...feature or oy review status -t main...feature
• Specific Commit: oy HEAD

jj (Jujutsu) Targets

• Default/Current Change: oy or oy @
• Bookmark Stack: oy feature
• Current Stack: oy 'trunk()..@'
• Specific Revset Review: oy review comment '@-..@'

# Git examples
oy review status -t @
oy --staged review status
oy review status -t main...feature

# jj examples
oy @
oy review status @
oy review comment '@-..@'

Some oy control commands (like play, target reloads, or animated movement) are asynchronous and return before the TUI has finished applying them. These commands return a response containing queued: true and a seq (sequence number).

How to synchronize:

1. Capture the seq from the command response.
2. Poll the current state using oy control where --session <name> --json.
3. Inspect the lastAppliedSeq field in the JSON output.
4. Wait until lastAppliedSeq is greater than or equal to the returned seq.

Stopping queued work: If you need to stop pending commands or motion immediately, use:

oy control cancel --session <name>

User Intervention: If a user interacts with the TUI (typing or clicking), Oyo will automatically stop any queued agent work.

# Example polling loop logic
oy control target --session review-a feature-branch
# ... wait for 'seq' ...
oy control where --session review-a --json
# ... check lastAppliedSeq >= seq ...

The log consists of a snapshot header followed by per-line entries.

Snapshot Header

Each snapshot begins with a header containing metadata about the current view state, such as pane, file, mode, window_start, and visible_render_range.

Per-line Entries

Each line in the render is logged with specific attributes. When debugging, focus on these fields:

Note: In split mode, logs show old and new display indices instead of a single disp value.

OYO_VIEW_DEBUG ts_ms=... pane=unified file_index=0 file="path/to/file"
mode=UnifiedPane stepping=false line_wrap=false diff_status=Ready placeholder=false view_len=1234 windowed=true window_start=0 window_total=5000 viewport_h=40 viewport_w=120 scroll_global=200 render_scroll=200
state current_hunk=3 total_hunks=8 last_nav_was_hunk=true cursor_change=512 show_extent_step=false scope_hunk=3 scope_from_cursor=true step_direction=None animation_phase=Idle
visible_render_range=200..239 context=2

L raw=210 disp=200-200 gdisp=200-200 h=3 scope=true show=true kind=Context changes=false old=100 new=100 act=false prim=false id=512 wrap=1 txt="..."

Oyo provides three primary ways to visualize changes:

1. Unified View

Shows a single stream of code. The file changes dynamically as you step through it.

• Modified lines: Shows Old text $\rightarrow$ Mixed old/new inline text (on step) $\rightarrow$ New text (after step).
• Insertions: Hidden $\rightarrow$ New text, active $\rightarrow$ New text.
• Deletions: Old text $\rightarrow$ Old text, active $\rightarrow$ Hidden.

2. Split View

Shows the old file on the left and the new file on the right.

• Modified lines: Left shows Old text, Right shows New text. On step, both show the active state.
• Insertions: The right pane shows New text.
• Deletions: The left pane shows Old text with deletion styling.

3. Evolution View

Shows the file changing over time. Deleted lines and markers are hidden. Syntax highlighting is controlled by ui.evo.syntax.

• context: Syntax only on non-diff lines.
• full: Syntax on diff and context lines (active line keeps diff colors).
• Toggle setting with E.