How AIClaw Keeps Multi-File Reviews in Place with Docked Tabs

Description and use

AIClaw now preserves review context across multiple files, keeping view state and scroll positions, and preventing background reads from changing the active tab.

Problem

Reviewing an agent’s work requires switching between multiple files, and each switch can lose the reviewer’s place or replace the conversation being checked.

Outcome

AIClaw now maintains continuous review context across multiple files, preserving view state and scroll positions, and preventing background reads from disrupting the active tab.

Workflow

• 1. Open AIClaw v3.7.14.
• 2. The Electron host adds up to 640px width for the reader, bounded by display area.
• 3. Open a file; a tab is created or reused if already open.
• 4. Switch between tabs using mouse or keyboard (←, →, Home, End).
• 5. Each tab stores view, diff layout, and scroll positions for source, rendered Markdown, before/after snapshots, and diff layout.
• 6. Background reads are assigned request identifiers; on completion they update the tab only if it still exists and the session matches.
• 7. Closing a tab removes its state; closing the last tab dismisses the reader.
• 8. The desktop smoke test verifies tab reuse, scroll restoration, diff retention, keyboard switching, and background completion behavior.

Evidence

AIClaw's v3.7.11 release introduced a docked reading area with multiple file tabs.

Source

The tab bar supports mouse selection and keyboard movement with the left/right arrows, Home, and End.

Source

The store assigns each read a request identifier. On completion, it checks that the corresponding tab still exists and that the session still matches, then updates the tab without unconditionally activating it.

Source