[elie222]

Why

Helpers (run_subagent) that were still working when a run paused for an approval, question or takeover kept showing as running forever, including after the run resumed or finished and after a reload. The helpers did stop, but their terminal events were queued after the executor had stopped reading the runtime stream, so the last stored event for each one stayed running. Every pause left another set of spinners behind.

What changed

• The executor tracks the helpers it has stored as running and stores the existing failed / stopped event for any that are unfinished before a pause and before finishing, with exit cleanup covering cancellation and runtime failures.
• The shared message projection and the web and mobile reducers settle a run's running helpers when the run pauses or ends, so helpers already stored as running before this fix also stop spinning. Helpers started after a resume still show as running.
• Thread snapshots load pause events and pass the active runs into the projection, so reloads settle stale helpers in bot and group chats.

The only visible change is that stopped helpers use their existing stopped state. No copy, layout, migration or auth changes.

Tests

Regression tests were written first and failed before the fix: helper persistence on pause, finish, failure and cancel (executor); projection on input pause, takeover pause, completed, failed and cancelled without reviving old helpers on resume (core, web, mobile); and snapshot reload settlement in bot and group chats, including a resumed run with fresh helpers. All touched-package unit suites, typechecks and Biome pass.

Fixes #1902

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
rakazo-www	Skipped		Oct 22, 2026 11:31pm UTC

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; both previous findings are addressed and no new blocking issues were found.

Summary

Stops unfinished helpers before a run pauses or ends, and settles stale helper cards in shared projections, web, mobile, and snapshot reloads.

• The executor saves unfinished helpers as stopped when a run pauses or ends.
• Thread views settle helpers when their run pauses or ends.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Helper stored as running] --> B[Run pauses or ends]
  B --> C[Build stopped helper block]
  C --> D[Save helper event and message together]
  D --> E[Remove helper from cleanup tracking]
  D --> F[Notify chat]
  G[Pause or terminal event] --> H[Shared and client projections settle running helpers]
  I[Snapshot reload] --> H

Loading

_{Reviews (2) · Last reviewed commit: "fix: settle helpers after cancellation a..." · Reviewed by Greptile}

[github-actions]

Playwright screenshots

No new feature frames; gallery is suite-vs-main drift.

Open screenshot gallery · Dashboard · CI run

Updated for commit 7ae4616.