v0.8.1

Four fixes on top of 0.8.0. No new features.

0.8 was about runs you start and then walk away from. This is the pass over the things that got in the way while you were away: a transcript that scrolled through black gaps, a task bar that outstayed its purpose, a warning nobody could act on, and a changed-files count that disagreed with git.

Scrolling a long transcript is smooth again

• The black gaps while flinging past older turns are gone. Historical rows carried content-visibility: auto, so each one was laid out as it entered the viewport — a frame that missed its deadline showed the container's background instead of the row.
• The containment also cost more than it saved. Measured in the packaged app against a real 17-turn transcript — 33 rows, ~12k elements, 20 viewports of scroll — it ran ~25% heavier per frame on average and nearly double on the worst frame. Without it: 7.5–8.2 ms average against a 16.7 ms budget, and zero blank frames per fling, across three repeats.
• React.memo on the group components and the structural sharing in the row builder stay — they were doing the actual work.

The task bar steps out of the way

• It renders only while a step is still in progress or pending. "Task 6/6 · All tasks completed" used to keep floating over the transcript for the rest of the run — covering the text you were reading to say nothing you could act on, and expanding over it on hover.

Rate-limit noise stays out of the transcript

• Only a rejection reaches the transcript now. Once usage got high the Claude SDK emitted an allowed-warning every turn, and each one became an orange "Approaching rate limit" row — two per exchange, one before the answer and one after. A percentage is not something you can act on mid-run; the turn that actually gets stopped still says so.

The changed-files count follows git again

• A run's diff is anchored to HEAD, not to the sha the run started from. Work the agent committed mid-run stayed inside the stored diff, so the sidebar and the changed-files panel kept counting changes that were already in history while the session panel — which reads live git status — had moved on.
• The old guard only fired for the CommitChanges tool, so a git commit run through Bash, or one made in a terminal outside the app, went unnoticed. Snapshots now read HEAD per capture, falling back to the run's base ref only when HEAD is unreadable.

---

Platform: macOS only (Apple Silicon and Intel).

Full changelog: v0.8.0...v0.8.1