fix(chat): smooth worktree setup status

[juliusmarminge]

What changed

Creating a thread with a new worktree could make the timeline jump and leave a "Received 2 updates" group above the running turn.

Web setup now uses a fixed-height status line: shimmering "Setting up worktree…" changes to "Working for…" when the turn starts. The normal Thinking marker then appears below, until assistant content or live tool activity replaces it. Its space stays reserved during setup so the handoff does not shift the timeline. The draft stays mounted through setup and keeps its timeline position when navigation completes.

Routine setup notices are omitted from the web and mobile work logs. Setup errors stay visible. Mobile shows the pending label in its workspace controls. Both shimmer implementations respect reduced motion.

UI changes

The same completed thread on the base version and this branch:

Before	After

Successful worktree setup recording: a real checkout, the shimmer-to-timer handoff with Thinking, and the completed response. The fixture briefly pauses checkout so the transition is visible.

Failed worktree setup recording: a Git checkout hook deliberately exits with an error. Setup feedback clears, the error remains, and the original prompt returns to an editable draft with Send available.

Ordinary turn before its first response: a current-checkout turn shows the working timer and Thinking immediately, then the response.

Failed checkout screenshot

Validation

• Focused web and mobile tests cover setup error retention, draft promotion, timeline anchoring, and composer behavior. Two server startup-ordering tests passed.
• The Thinking follow-up passed 49 timeline logic tests and 38 timeline component tests, including empty assistant placeholders, content/tool handoff, and stable-row updates.
• Targeted lint and formatting passed. React Doctor found no new issues in the changed code.
• Web, mobile, and client-runtime typechecks passed.
• Real browser runs verified successful checkout, checkout failure, an ordinary turn before its first response, and history after reload. The status block kept the same position and height through setup, the first Thinking state, and navigation to the thread. The setup shimmer unmounts at handoff.
• Mobile verification covered logic tests and typechecking; the recordings show the web client.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Medium Risk
Changes draft promotion timing and timeline row derivation, which affect first-send and worktree flows; behavior is covered by new tests but navigation edge cases are user-visible.

Overview
Improves worktree setup so chat stays visually stable: one fixed-height status line shimmers “Setting up worktree…” (web timeline and mobile new-task workspace controls), then hands off to “Working for…” when the turn starts. The composer footer no longer shows a separate “Preparing worktree…” label.

Draft → thread navigation waits until the server has something meaningful to show: the first turn has startedAt, or the session ends in error / stopped / interrupted. That keeps the draft mounted through checkout/setup instead of promoting too early.

Work logs on web and mobile drop routine setup-script.requested / setup-script.started noise via shared isWorktreeSetupActivity; error-toned setup failures still appear in the feed.

The active-turn working row no longer always shows a placeholder “Thinking” line—only when there’s no assistant text and no live tool activity—reducing extra rows at setup-to-turn transitions. Timeline anchoring uses CHAT_TIMELINE_ANCHOR_OFFSET (24px) so promotion preserves scroll position.

^{Reviewed by Cursor Bugbot for commit 4b10ed5. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Smooth worktree setup status across mobile and web chat UI

• Delays draft-to-server thread promotion until the first turn starts or setup ends in an error/stop/interruption, so the draft stays mounted during worktree setup
• Replaces workspace controls on mobile and working timeline rows on web with a shimmering 'Setting up worktree…' status during setup, hiding the elapsed timer and thinking indicator
• Filters routine setup-script.requested and setup-script.started activities from derived work logs unless they are error-toned, via new isWorktreeSetupActivity helper in presentation.ts
• Introduces ActivityShimmerOverlay and increases timeline anchor offset from 16 to 24 in timelineScrollAnchoring.ts
• Risk: resolveDraftPromotionNavigationTarget signature changes from boolean to serverThread object; callers in ChatView.logic.ts and _chat.draft.$draftId.tsx are updated but out-of-tree consumers would break

^{Macroscope summarized 4b10ed5.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 20769c12-fd52-4451-b0a4-c95043d4049e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	−29 B (−0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	+1 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	−30 B (−0.5%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.5 KiB	−44 B (−0.1%)	66.4 KiB	✅
Codex	Live turn messages	10	9	−1 (−10.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+55 B (+0.4%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−2 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+57 B (+0.9%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	+88 B (+0.2%)	66.4 KiB	✅
Claude	Live turn messages	9	11	+2 (+22.2%)	21	✅

Baseline: bba79cc · PR result: 4b10ed5 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit 0e6f80e. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — The change improves worktree setup feedback, but it also changes draft promotion timing, shared activity filtering, and timeline rendering/scroll anchoring across web and mobile. Because these interconnected production paths have a broader behavioral surface than a small isolated UI fix, human review is warranted.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

Reviewed the web UI changes for shared-component/Tailwind ownership and visual behavior. Three findings, one of which is a concrete duplicated-status inconsistency introduced by this patch.

^{Posted via Macroscope — UI Consistency}

[juliusmarminge]

What changed

Creating a thread with a new worktree could make the timeline jump and leave a "Received 2 updates" group above the running turn.

Web setup now uses a fixed-height status line: shimmering "Setting up worktree…" changes to "Working for…" when the turn starts. The normal Thinking marker then appears below, until assistant content or live tool activity replaces it. Its space stays reserved during setup so the handoff does not shift the timeline. The draft stays mounted through setup and keeps its timeline position when navigation completes.

Routine setup notices are omitted from the web and mobile work logs. Setup errors stay visible. Mobile shows the pending label in its workspace controls. Both shimmer implementations respect reduced motion.

UI changes

The same completed thread on the base version and this branch:

Before	After

Successful worktree setup recording: a real checkout, the shimmer-to-timer handoff with Thinking, and the completed response. The fixture briefly pauses checkout so the transition is visible.

Failed worktree setup recording: a Git checkout hook deliberately exits with an error. Setup feedback clears, the error remains, and the original prompt returns to an editable draft with Send available.

Ordinary turn before its first response: a current-checkout turn shows the working timer and Thinking immediately, then the response.

Failed checkout screenshot

Validation

• Focused web and mobile tests cover setup error retention, draft promotion, timeline anchoring, and composer behavior. Two server startup-ordering tests passed.
• The Thinking follow-up passed 49 timeline logic tests and 38 timeline component tests, including empty assistant placeholders, content/tool handoff, and stable-row updates.
• Targeted lint and formatting passed. React Doctor found no new issues in the changed code.
• Web, mobile, and client-runtime typechecks passed.
• Real browser runs verified successful checkout, checkout failure, an ordinary turn before its first response, and history after reload. The status block kept the same position and height through setup, the first Thinking state, and navigation to the thread. The setup shimmer unmounts at handoff.
• Mobile verification covered logic tests and typechecking; the recordings show the web client.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Medium Risk
Changes draft promotion timing and timeline row derivation, which affect first-send and worktree flows; behavior is covered by new tests but navigation edge cases are user-visible.

Overview
Improves worktree setup so chat stays visually stable: one fixed-height status line shimmers “Setting up worktree…” (web timeline and mobile new-task workspace controls), then hands off to “Working for…” when the turn starts. The composer footer no longer shows a separate “Preparing worktree…” label.

Draft → thread navigation waits until the server has something meaningful to show: the first turn has startedAt, or the session ends in error / stopped / interrupted. That keeps the draft mounted through checkout/setup instead of promoting too early.

Work logs on web and mobile drop routine setup-script.requested / setup-script.started noise via shared isWorktreeSetupActivity; error-toned setup failures still appear in the feed.

The active-turn working row no longer always shows a placeholder “Thinking” line—only when there’s no assistant text and no live tool activity—reducing extra rows at setup-to-turn transitions. Timeline anchoring uses CHAT_TIMELINE_ANCHOR_OFFSET (24px) so promotion preserves scroll position.

^{Reviewed by Cursor Bugbot for commit 4b10ed5. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Smooth worktree setup status across mobile and web chat UI

• Delays draft-to-server thread promotion until the first turn starts or setup ends in an error/stop/interruption, so the draft stays mounted during worktree setup
• Replaces workspace controls on mobile and working timeline rows on web with a shimmering 'Setting up worktree…' status during setup, hiding the elapsed timer and thinking indicator
• Filters routine setup-script.requested and setup-script.started activities from derived work logs unless they are error-toned, via new isWorktreeSetupActivity helper in presentation.ts
• Introduces ActivityShimmerOverlay and increases timeline anchor offset from 16 to 24 in timelineScrollAnchoring.ts
• Risk: resolveDraftPromotionNavigationTarget signature changes from boolean to serverThread object; callers in ChatView.logic.ts and _chat.draft.$draftId.tsx are updated but out-of-tree consumers would break

^{Macroscope summarized 4b10ed5.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 20769c12-fd52-4451-b0a4-c95043d4049e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	−29 B (−0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	+1 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	−30 B (−0.5%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.5 KiB	−44 B (−0.1%)	66.4 KiB	✅
Codex	Live turn messages	10	9	−1 (−10.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+55 B (+0.4%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−2 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+57 B (+0.9%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	+88 B (+0.2%)	66.4 KiB	✅
Claude	Live turn messages	9	11	+2 (+22.2%)	21	✅

Baseline: bba79cc · PR result: 4b10ed5 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit 0e6f80e. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — The change improves worktree setup feedback, but it also changes draft promotion timing, shared activity filtering, and timeline rendering/scroll anchoring across web and mobile. Because these interconnected production paths have a broader behavioral surface than a small isolated UI fix, human review is warranted.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

Reviewed the web UI changes for shared-component/Tailwind ownership and visual behavior. Three findings, one of which is a concrete duplicated-status inconsistency introduced by this patch.

^{Posted via Macroscope — UI Consistency}

[juliusmarminge]

What changed

Creating a thread with a new worktree could make the timeline jump and leave a "Received 2 updates" group above the running turn.

Web setup now uses a fixed-height status line: shimmering "Setting up worktree…" changes to "Working for…" when the turn starts. The normal Thinking marker then appears below, until assistant content or live tool activity replaces it. Its space stays reserved during setup so the handoff does not shift the timeline. The draft stays mounted through setup and keeps its timeline position when navigation completes.

Routine setup notices are omitted from the web and mobile work logs. Setup errors stay visible. Mobile shows the pending label in its workspace controls. Both shimmer implementations respect reduced motion.

UI changes

The same completed thread on the base version and this branch:

Before	After

Successful worktree setup recording: a real checkout, the shimmer-to-timer handoff with Thinking, and the completed response. The fixture briefly pauses checkout so the transition is visible.

Failed worktree setup recording: a Git checkout hook deliberately exits with an error. Setup feedback clears, the error remains, and the original prompt returns to an editable draft with Send available.

Ordinary turn before its first response: a current-checkout turn shows the working timer and Thinking immediately, then the response.

Failed checkout screenshot

Validation

• Focused web and mobile tests cover setup error retention, draft promotion, timeline anchoring, and composer behavior. Two server startup-ordering tests passed.
• The Thinking follow-up passed 49 timeline logic tests and 38 timeline component tests, including empty assistant placeholders, content/tool handoff, and stable-row updates.
• Targeted lint and formatting passed. React Doctor found no new issues in the changed code.
• Web, mobile, and client-runtime typechecks passed.
• Real browser runs verified successful checkout, checkout failure, an ordinary turn before its first response, and history after reload. The status block kept the same position and height through setup, the first Thinking state, and navigation to the thread. The setup shimmer unmounts at handoff.
• Mobile verification covered logic tests and typechecking; the recordings show the web client.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Medium Risk
Changes draft promotion timing and timeline row derivation, which affect first-send and worktree flows; behavior is covered by new tests but navigation edge cases are user-visible.

Overview
Improves worktree setup so chat stays visually stable: one fixed-height status line shimmers “Setting up worktree…” (web timeline and mobile new-task workspace controls), then hands off to “Working for…” when the turn starts. The composer footer no longer shows a separate “Preparing worktree…” label.

Draft → thread navigation waits until the server has something meaningful to show: the first turn has startedAt, or the session ends in error / stopped / interrupted. That keeps the draft mounted through checkout/setup instead of promoting too early.

Work logs on web and mobile drop routine setup-script.requested / setup-script.started noise via shared isWorktreeSetupActivity; error-toned setup failures still appear in the feed.

The active-turn working row no longer always shows a placeholder “Thinking” line—only when there’s no assistant text and no live tool activity—reducing extra rows at setup-to-turn transitions. Timeline anchoring uses CHAT_TIMELINE_ANCHOR_OFFSET (24px) so promotion preserves scroll position.

^{Reviewed by Cursor Bugbot for commit 4b10ed5. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Smooth worktree setup status across mobile and web chat UI

• Delays draft-to-server thread promotion until the first turn starts or setup ends in an error/stop/interruption, so the draft stays mounted during worktree setup
• Replaces workspace controls on mobile and working timeline rows on web with a shimmering 'Setting up worktree…' status during setup, hiding the elapsed timer and thinking indicator
• Filters routine setup-script.requested and setup-script.started activities from derived work logs unless they are error-toned, via new isWorktreeSetupActivity helper in presentation.ts
• Introduces ActivityShimmerOverlay and increases timeline anchor offset from 16 to 24 in timelineScrollAnchoring.ts
• Risk: resolveDraftPromotionNavigationTarget signature changes from boolean to serverThread object; callers in ChatView.logic.ts and _chat.draft.$draftId.tsx are updated but out-of-tree consumers would break

^{Macroscope summarized 4b10ed5.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 20769c12-fd52-4451-b0a4-c95043d4049e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	−29 B (−0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	+1 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	−30 B (−0.5%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.5 KiB	−44 B (−0.1%)	66.4 KiB	✅
Codex	Live turn messages	10	9	−1 (−10.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+55 B (+0.4%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−2 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+57 B (+0.9%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	+88 B (+0.2%)	66.4 KiB	✅
Claude	Live turn messages	9	11	+2 (+22.2%)	21	✅

Baseline: bba79cc · PR result: 4b10ed5 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit 0e6f80e. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — The change improves worktree setup feedback, but it also changes draft promotion timing, shared activity filtering, and timeline rendering/scroll anchoring across web and mobile. Because these interconnected production paths have a broader behavioral surface than a small isolated UI fix, human review is warranted.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

Reviewed the web UI changes for shared-component/Tailwind ownership and visual behavior. Three findings, one of which is a concrete duplicated-status inconsistency introduced by this patch.

^{Posted via Macroscope — UI Consistency}

[juliusmarminge]

What changed

Creating a thread with a new worktree could make the timeline jump and leave a "Received 2 updates" group above the running turn.

Web setup now uses a fixed-height status line: shimmering "Setting up worktree…" changes to "Working for…" when the turn starts. The normal Thinking marker then appears below, until assistant content or live tool activity replaces it. Its space stays reserved during setup so the handoff does not shift the timeline. The draft stays mounted through setup and keeps its timeline position when navigation completes.

Routine setup notices are omitted from the web and mobile work logs. Setup errors stay visible. Mobile shows the pending label in its workspace controls. Both shimmer implementations respect reduced motion.

UI changes

The same completed thread on the base version and this branch:

Before	After

Successful worktree setup recording: a real checkout, the shimmer-to-timer handoff with Thinking, and the completed response. The fixture briefly pauses checkout so the transition is visible.

Failed worktree setup recording: a Git checkout hook deliberately exits with an error. Setup feedback clears, the error remains, and the original prompt returns to an editable draft with Send available.

Ordinary turn before its first response: a current-checkout turn shows the working timer and Thinking immediately, then the response.

Failed checkout screenshot

Validation

• Focused web and mobile tests cover setup error retention, draft promotion, timeline anchoring, and composer behavior. Two server startup-ordering tests passed.
• The Thinking follow-up passed 49 timeline logic tests and 38 timeline component tests, including empty assistant placeholders, content/tool handoff, and stable-row updates.
• Targeted lint and formatting passed. React Doctor found no new issues in the changed code.
• Web, mobile, and client-runtime typechecks passed.
• Real browser runs verified successful checkout, checkout failure, an ordinary turn before its first response, and history after reload. The status block kept the same position and height through setup, the first Thinking state, and navigation to the thread. The setup shimmer unmounts at handoff.
• Mobile verification covered logic tests and typechecking; the recordings show the web client.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Medium Risk
Changes draft promotion timing and timeline row derivation, which affect first-send and worktree flows; behavior is covered by new tests but navigation edge cases are user-visible.

Overview
Improves worktree setup so chat stays visually stable: one fixed-height status line shimmers “Setting up worktree…” (web timeline and mobile new-task workspace controls), then hands off to “Working for…” when the turn starts. The composer footer no longer shows a separate “Preparing worktree…” label.

Draft → thread navigation waits until the server has something meaningful to show: the first turn has startedAt, or the session ends in error / stopped / interrupted. That keeps the draft mounted through checkout/setup instead of promoting too early.

Work logs on web and mobile drop routine setup-script.requested / setup-script.started noise via shared isWorktreeSetupActivity; error-toned setup failures still appear in the feed.

The active-turn working row no longer always shows a placeholder “Thinking” line—only when there’s no assistant text and no live tool activity—reducing extra rows at setup-to-turn transitions. Timeline anchoring uses CHAT_TIMELINE_ANCHOR_OFFSET (24px) so promotion preserves scroll position.

^{Reviewed by Cursor Bugbot for commit 4b10ed5. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Smooth worktree setup status across mobile and web chat UI

• Delays draft-to-server thread promotion until the first turn starts or setup ends in an error/stop/interruption, so the draft stays mounted during worktree setup
• Replaces workspace controls on mobile and working timeline rows on web with a shimmering 'Setting up worktree…' status during setup, hiding the elapsed timer and thinking indicator
• Filters routine setup-script.requested and setup-script.started activities from derived work logs unless they are error-toned, via new isWorktreeSetupActivity helper in presentation.ts
• Introduces ActivityShimmerOverlay and increases timeline anchor offset from 16 to 24 in timelineScrollAnchoring.ts
• Risk: resolveDraftPromotionNavigationTarget signature changes from boolean to serverThread object; callers in ChatView.logic.ts and _chat.draft.$draftId.tsx are updated but out-of-tree consumers would break

^{Macroscope summarized 4b10ed5.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 20769c12-fd52-4451-b0a4-c95043d4049e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	−29 B (−0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	+1 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	−30 B (−0.5%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.5 KiB	−44 B (−0.1%)	66.4 KiB	✅
Codex	Live turn messages	10	9	−1 (−10.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+55 B (+0.4%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−2 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+57 B (+0.9%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	+88 B (+0.2%)	66.4 KiB	✅
Claude	Live turn messages	9	11	+2 (+22.2%)	21	✅

Baseline: bba79cc · PR result: 4b10ed5 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit 0e6f80e. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — The change improves worktree setup feedback, but it also changes draft promotion timing, shared activity filtering, and timeline rendering/scroll anchoring across web and mobile. Because these interconnected production paths have a broader behavioral surface than a small isolated UI fix, human review is warranted.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

Reviewed the web UI changes for shared-component/Tailwind ownership and visual behavior. Three findings, one of which is a concrete duplicated-status inconsistency introduced by this patch.

^{Posted via Macroscope — UI Consistency}

[juliusmarminge]

What changed

Creating a thread with a new worktree could make the timeline jump and leave a "Received 2 updates" group above the running turn.

Web setup now uses a fixed-height status line: shimmering "Setting up worktree…" changes to "Working for…" when the turn starts. The normal Thinking marker then appears below, until assistant content or live tool activity replaces it. Its space stays reserved during setup so the handoff does not shift the timeline. The draft stays mounted through setup and keeps its timeline position when navigation completes.

Routine setup notices are omitted from the web and mobile work logs. Setup errors stay visible. Mobile shows the pending label in its workspace controls. Both shimmer implementations respect reduced motion.

UI changes

The same completed thread on the base version and this branch:

Before	After

Successful worktree setup recording: a real checkout, the shimmer-to-timer handoff with Thinking, and the completed response. The fixture briefly pauses checkout so the transition is visible.

Failed worktree setup recording: a Git checkout hook deliberately exits with an error. Setup feedback clears, the error remains, and the original prompt returns to an editable draft with Send available.

Ordinary turn before its first response: a current-checkout turn shows the working timer and Thinking immediately, then the response.

Failed checkout screenshot

Validation

• Focused web and mobile tests cover setup error retention, draft promotion, timeline anchoring, and composer behavior. Two server startup-ordering tests passed.
• The Thinking follow-up passed 49 timeline logic tests and 38 timeline component tests, including empty assistant placeholders, content/tool handoff, and stable-row updates.
• Targeted lint and formatting passed. React Doctor found no new issues in the changed code.
• Web, mobile, and client-runtime typechecks passed.
• Real browser runs verified successful checkout, checkout failure, an ordinary turn before its first response, and history after reload. The status block kept the same position and height through setup, the first Thinking state, and navigation to the thread. The setup shimmer unmounts at handoff.
• Mobile verification covered logic tests and typechecking; the recordings show the web client.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Medium Risk
Changes draft promotion timing and timeline row derivation, which affect first-send and worktree flows; behavior is covered by new tests but navigation edge cases are user-visible.

Overview
Improves worktree setup so chat stays visually stable: one fixed-height status line shimmers “Setting up worktree…” (web timeline and mobile new-task workspace controls), then hands off to “Working for…” when the turn starts. The composer footer no longer shows a separate “Preparing worktree…” label.

Draft → thread navigation waits until the server has something meaningful to show: the first turn has startedAt, or the session ends in error / stopped / interrupted. That keeps the draft mounted through checkout/setup instead of promoting too early.

Work logs on web and mobile drop routine setup-script.requested / setup-script.started noise via shared isWorktreeSetupActivity; error-toned setup failures still appear in the feed.

The active-turn working row no longer always shows a placeholder “Thinking” line—only when there’s no assistant text and no live tool activity—reducing extra rows at setup-to-turn transitions. Timeline anchoring uses CHAT_TIMELINE_ANCHOR_OFFSET (24px) so promotion preserves scroll position.

^{Reviewed by Cursor Bugbot for commit 4b10ed5. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Smooth worktree setup status across mobile and web chat UI

• Delays draft-to-server thread promotion until the first turn starts or setup ends in an error/stop/interruption, so the draft stays mounted during worktree setup
• Replaces workspace controls on mobile and working timeline rows on web with a shimmering 'Setting up worktree…' status during setup, hiding the elapsed timer and thinking indicator
• Filters routine setup-script.requested and setup-script.started activities from derived work logs unless they are error-toned, via new isWorktreeSetupActivity helper in presentation.ts
• Introduces ActivityShimmerOverlay and increases timeline anchor offset from 16 to 24 in timelineScrollAnchoring.ts
• Risk: resolveDraftPromotionNavigationTarget signature changes from boolean to serverThread object; callers in ChatView.logic.ts and _chat.draft.$draftId.tsx are updated but out-of-tree consumers would break

^{Macroscope summarized 4b10ed5.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 20769c12-fd52-4451-b0a4-c95043d4049e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	−29 B (−0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	+1 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	−30 B (−0.5%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.5 KiB	−44 B (−0.1%)	66.4 KiB	✅
Codex	Live turn messages	10	9	−1 (−10.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+55 B (+0.4%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−2 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+57 B (+0.9%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	+88 B (+0.2%)	66.4 KiB	✅
Claude	Live turn messages	9	11	+2 (+22.2%)	21	✅

Baseline: bba79cc · PR result: 4b10ed5 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit 0e6f80e. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — The change improves worktree setup feedback, but it also changes draft promotion timing, shared activity filtering, and timeline rendering/scroll anchoring across web and mobile. Because these interconnected production paths have a broader behavioral surface than a small isolated UI fix, human review is warranted.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

Reviewed the web UI changes for shared-component/Tailwind ownership and visual behavior. Three findings, one of which is a concrete duplicated-status inconsistency introduced by this patch.

^{Posted via Macroscope — UI Consistency}

[juliusmarminge]

What changed

Creating a thread with a new worktree could make the timeline jump and leave a "Received 2 updates" group above the running turn.

Web setup now uses a fixed-height status line: shimmering "Setting up worktree…" changes to "Working for…" when the turn starts. The normal Thinking marker then appears below, until assistant content or live tool activity replaces it. Its space stays reserved during setup so the handoff does not shift the timeline. The draft stays mounted through setup and keeps its timeline position when navigation completes.

Routine setup notices are omitted from the web and mobile work logs. Setup errors stay visible. Mobile shows the pending label in its workspace controls. Both shimmer implementations respect reduced motion.

UI changes

The same completed thread on the base version and this branch:

Before	After

Successful worktree setup recording: a real checkout, the shimmer-to-timer handoff with Thinking, and the completed response. The fixture briefly pauses checkout so the transition is visible.

Failed worktree setup recording: a Git checkout hook deliberately exits with an error. Setup feedback clears, the error remains, and the original prompt returns to an editable draft with Send available.

Ordinary turn before its first response: a current-checkout turn shows the working timer and Thinking immediately, then the response.

Failed checkout screenshot

Validation

• Focused web and mobile tests cover setup error retention, draft promotion, timeline anchoring, and composer behavior. Two server startup-ordering tests passed.
• The Thinking follow-up passed 49 timeline logic tests and 38 timeline component tests, including empty assistant placeholders, content/tool handoff, and stable-row updates.
• Targeted lint and formatting passed. React Doctor found no new issues in the changed code.
• Web, mobile, and client-runtime typechecks passed.
• Real browser runs verified successful checkout, checkout failure, an ordinary turn before its first response, and history after reload. The status block kept the same position and height through setup, the first Thinking state, and navigation to the thread. The setup shimmer unmounts at handoff.
• Mobile verification covered logic tests and typechecking; the recordings show the web client.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Medium Risk
Changes draft promotion timing and timeline row derivation, which affect first-send and worktree flows; behavior is covered by new tests but navigation edge cases are user-visible.

Overview
Improves worktree setup so chat stays visually stable: one fixed-height status line shimmers “Setting up worktree…” (web timeline and mobile new-task workspace controls), then hands off to “Working for…” when the turn starts. The composer footer no longer shows a separate “Preparing worktree…” label.

Draft → thread navigation waits until the server has something meaningful to show: the first turn has startedAt, or the session ends in error / stopped / interrupted. That keeps the draft mounted through checkout/setup instead of promoting too early.

Work logs on web and mobile drop routine setup-script.requested / setup-script.started noise via shared isWorktreeSetupActivity; error-toned setup failures still appear in the feed.

The active-turn working row no longer always shows a placeholder “Thinking” line—only when there’s no assistant text and no live tool activity—reducing extra rows at setup-to-turn transitions. Timeline anchoring uses CHAT_TIMELINE_ANCHOR_OFFSET (24px) so promotion preserves scroll position.

^{Reviewed by Cursor Bugbot for commit 4b10ed5. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Smooth worktree setup status across mobile and web chat UI

• Delays draft-to-server thread promotion until the first turn starts or setup ends in an error/stop/interruption, so the draft stays mounted during worktree setup
• Replaces workspace controls on mobile and working timeline rows on web with a shimmering 'Setting up worktree…' status during setup, hiding the elapsed timer and thinking indicator
• Filters routine setup-script.requested and setup-script.started activities from derived work logs unless they are error-toned, via new isWorktreeSetupActivity helper in presentation.ts
• Introduces ActivityShimmerOverlay and increases timeline anchor offset from 16 to 24 in timelineScrollAnchoring.ts
• Risk: resolveDraftPromotionNavigationTarget signature changes from boolean to serverThread object; callers in ChatView.logic.ts and _chat.draft.$draftId.tsx are updated but out-of-tree consumers would break

^{Macroscope summarized 4b10ed5.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 20769c12-fd52-4451-b0a4-c95043d4049e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	−29 B (−0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	+1 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	−30 B (−0.5%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.5 KiB	−44 B (−0.1%)	66.4 KiB	✅
Codex	Live turn messages	10	9	−1 (−10.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+55 B (+0.4%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−2 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+57 B (+0.9%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	+88 B (+0.2%)	66.4 KiB	✅
Claude	Live turn messages	9	11	+2 (+22.2%)	21	✅

Baseline: bba79cc · PR result: 4b10ed5 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit 0e6f80e. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — The change improves worktree setup feedback, but it also changes draft promotion timing, shared activity filtering, and timeline rendering/scroll anchoring across web and mobile. Because these interconnected production paths have a broader behavioral surface than a small isolated UI fix, human review is warranted.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

Reviewed the web UI changes for shared-component/Tailwind ownership and visual behavior. Three findings, one of which is a concrete duplicated-status inconsistency introduced by this patch.

^{Posted via Macroscope — UI Consistency}

[juliusmarminge]

What changed

Creating a thread with a new worktree could make the timeline jump and leave a "Received 2 updates" group above the running turn.

Web setup now uses a fixed-height status line: shimmering "Setting up worktree…" changes to "Working for…" when the turn starts. The normal Thinking marker then appears below, until assistant content or live tool activity replaces it. Its space stays reserved during setup so the handoff does not shift the timeline. The draft stays mounted through setup and keeps its timeline position when navigation completes.

Routine setup notices are omitted from the web and mobile work logs. Setup errors stay visible. Mobile shows the pending label in its workspace controls. Both shimmer implementations respect reduced motion.

UI changes

The same completed thread on the base version and this branch:

Before	After

Successful worktree setup recording: a real checkout, the shimmer-to-timer handoff with Thinking, and the completed response. The fixture briefly pauses checkout so the transition is visible.

Failed worktree setup recording: a Git checkout hook deliberately exits with an error. Setup feedback clears, the error remains, and the original prompt returns to an editable draft with Send available.

Ordinary turn before its first response: a current-checkout turn shows the working timer and Thinking immediately, then the response.

Failed checkout screenshot

Validation

• Focused web and mobile tests cover setup error retention, draft promotion, timeline anchoring, and composer behavior. Two server startup-ordering tests passed.
• The Thinking follow-up passed 49 timeline logic tests and 38 timeline component tests, including empty assistant placeholders, content/tool handoff, and stable-row updates.
• Targeted lint and formatting passed. React Doctor found no new issues in the changed code.
• Web, mobile, and client-runtime typechecks passed.
• Real browser runs verified successful checkout, checkout failure, an ordinary turn before its first response, and history after reload. The status block kept the same position and height through setup, the first Thinking state, and navigation to the thread. The setup shimmer unmounts at handoff.
• Mobile verification covered logic tests and typechecking; the recordings show the web client.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Medium Risk
Changes draft promotion timing and timeline row derivation, which affect first-send and worktree flows; behavior is covered by new tests but navigation edge cases are user-visible.

Overview
Improves worktree setup so chat stays visually stable: one fixed-height status line shimmers “Setting up worktree…” (web timeline and mobile new-task workspace controls), then hands off to “Working for…” when the turn starts. The composer footer no longer shows a separate “Preparing worktree…” label.

Draft → thread navigation waits until the server has something meaningful to show: the first turn has startedAt, or the session ends in error / stopped / interrupted. That keeps the draft mounted through checkout/setup instead of promoting too early.

Work logs on web and mobile drop routine setup-script.requested / setup-script.started noise via shared isWorktreeSetupActivity; error-toned setup failures still appear in the feed.

The active-turn working row no longer always shows a placeholder “Thinking” line—only when there’s no assistant text and no live tool activity—reducing extra rows at setup-to-turn transitions. Timeline anchoring uses CHAT_TIMELINE_ANCHOR_OFFSET (24px) so promotion preserves scroll position.

^{Reviewed by Cursor Bugbot for commit 4b10ed5. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Smooth worktree setup status across mobile and web chat UI

• Delays draft-to-server thread promotion until the first turn starts or setup ends in an error/stop/interruption, so the draft stays mounted during worktree setup
• Replaces workspace controls on mobile and working timeline rows on web with a shimmering 'Setting up worktree…' status during setup, hiding the elapsed timer and thinking indicator
• Filters routine setup-script.requested and setup-script.started activities from derived work logs unless they are error-toned, via new isWorktreeSetupActivity helper in presentation.ts
• Introduces ActivityShimmerOverlay and increases timeline anchor offset from 16 to 24 in timelineScrollAnchoring.ts
• Risk: resolveDraftPromotionNavigationTarget signature changes from boolean to serverThread object; callers in ChatView.logic.ts and _chat.draft.$draftId.tsx are updated but out-of-tree consumers would break

^{Macroscope summarized 4b10ed5.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 20769c12-fd52-4451-b0a4-c95043d4049e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	−29 B (−0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	+1 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	−30 B (−0.5%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.5 KiB	−44 B (−0.1%)	66.4 KiB	✅
Codex	Live turn messages	10	9	−1 (−10.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+55 B (+0.4%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−2 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+57 B (+0.9%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	+88 B (+0.2%)	66.4 KiB	✅
Claude	Live turn messages	9	11	+2 (+22.2%)	21	✅

Baseline: bba79cc · PR result: 4b10ed5 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit 0e6f80e. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — The change improves worktree setup feedback, but it also changes draft promotion timing, shared activity filtering, and timeline rendering/scroll anchoring across web and mobile. Because these interconnected production paths have a broader behavioral surface than a small isolated UI fix, human review is warranted.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

Reviewed the web UI changes for shared-component/Tailwind ownership and visual behavior. Three findings, one of which is a concrete duplicated-status inconsistency introduced by this patch.

^{Posted via Macroscope — UI Consistency}

[juliusmarminge]

What changed

Creating a thread with a new worktree could make the timeline jump and leave a "Received 2 updates" group above the running turn.

Web setup now uses a fixed-height status line: shimmering "Setting up worktree…" changes to "Working for…" when the turn starts. The normal Thinking marker then appears below, until assistant content or live tool activity replaces it. Its space stays reserved during setup so the handoff does not shift the timeline. The draft stays mounted through setup and keeps its timeline position when navigation completes.

Routine setup notices are omitted from the web and mobile work logs. Setup errors stay visible. Mobile shows the pending label in its workspace controls. Both shimmer implementations respect reduced motion.

UI changes

The same completed thread on the base version and this branch:

Before	After

Successful worktree setup recording: a real checkout, the shimmer-to-timer handoff with Thinking, and the completed response. The fixture briefly pauses checkout so the transition is visible.

Failed worktree setup recording: a Git checkout hook deliberately exits with an error. Setup feedback clears, the error remains, and the original prompt returns to an editable draft with Send available.

Ordinary turn before its first response: a current-checkout turn shows the working timer and Thinking immediately, then the response.

Failed checkout screenshot

Validation

• Focused web and mobile tests cover setup error retention, draft promotion, timeline anchoring, and composer behavior. Two server startup-ordering tests passed.
• The Thinking follow-up passed 49 timeline logic tests and 38 timeline component tests, including empty assistant placeholders, content/tool handoff, and stable-row updates.
• Targeted lint and formatting passed. React Doctor found no new issues in the changed code.
• Web, mobile, and client-runtime typechecks passed.
• Real browser runs verified successful checkout, checkout failure, an ordinary turn before its first response, and history after reload. The status block kept the same position and height through setup, the first Thinking state, and navigation to the thread. The setup shimmer unmounts at handoff.
• Mobile verification covered logic tests and typechecking; the recordings show the web client.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Medium Risk
Changes draft promotion timing and timeline row derivation, which affect first-send and worktree flows; behavior is covered by new tests but navigation edge cases are user-visible.

Overview
Improves worktree setup so chat stays visually stable: one fixed-height status line shimmers “Setting up worktree…” (web timeline and mobile new-task workspace controls), then hands off to “Working for…” when the turn starts. The composer footer no longer shows a separate “Preparing worktree…” label.

Draft → thread navigation waits until the server has something meaningful to show: the first turn has startedAt, or the session ends in error / stopped / interrupted. That keeps the draft mounted through checkout/setup instead of promoting too early.

Work logs on web and mobile drop routine setup-script.requested / setup-script.started noise via shared isWorktreeSetupActivity; error-toned setup failures still appear in the feed.

The active-turn working row no longer always shows a placeholder “Thinking” line—only when there’s no assistant text and no live tool activity—reducing extra rows at setup-to-turn transitions. Timeline anchoring uses CHAT_TIMELINE_ANCHOR_OFFSET (24px) so promotion preserves scroll position.

^{Reviewed by Cursor Bugbot for commit 4b10ed5. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Smooth worktree setup status across mobile and web chat UI

• Delays draft-to-server thread promotion until the first turn starts or setup ends in an error/stop/interruption, so the draft stays mounted during worktree setup
• Replaces workspace controls on mobile and working timeline rows on web with a shimmering 'Setting up worktree…' status during setup, hiding the elapsed timer and thinking indicator
• Filters routine setup-script.requested and setup-script.started activities from derived work logs unless they are error-toned, via new isWorktreeSetupActivity helper in presentation.ts
• Introduces ActivityShimmerOverlay and increases timeline anchor offset from 16 to 24 in timelineScrollAnchoring.ts
• Risk: resolveDraftPromotionNavigationTarget signature changes from boolean to serverThread object; callers in ChatView.logic.ts and _chat.draft.$draftId.tsx are updated but out-of-tree consumers would break

^{Macroscope summarized 4b10ed5.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 20769c12-fd52-4451-b0a4-c95043d4049e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	−29 B (−0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	+1 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	−30 B (−0.5%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.5 KiB	−44 B (−0.1%)	66.4 KiB	✅
Codex	Live turn messages	10	9	−1 (−10.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+55 B (+0.4%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−2 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+57 B (+0.9%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	+88 B (+0.2%)	66.4 KiB	✅
Claude	Live turn messages	9	11	+2 (+22.2%)	21	✅

Baseline: bba79cc · PR result: 4b10ed5 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit 0e6f80e. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — The change improves worktree setup feedback, but it also changes draft promotion timing, shared activity filtering, and timeline rendering/scroll anchoring across web and mobile. Because these interconnected production paths have a broader behavioral surface than a small isolated UI fix, human review is warranted.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

Reviewed the web UI changes for shared-component/Tailwind ownership and visual behavior. Three findings, one of which is a concrete duplicated-status inconsistency introduced by this patch.

^{Posted via Macroscope — UI Consistency}