Repository navigation
feat(web): collapse agent activity in standing threads - #148
Merged
nullStack65 merged 3 commits intoNov 20, 2026
Merged
Conversation
A coordinator thread buries the founder's own messages under agent relays,
automations and system notices. Standing threads now collapse each run of
that activity into one expandable pill ("14 agent updates · click to expand")
so his messages and the model's replies to them stay where he left off.
Nothing is dropped: expanding a pill shows exactly the rows it replaced, and
the header toggle switches back to everything, remembered per thread.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
…plans Review of the collapse found four defects. A pill was keyed to its first row, so a live turn settling or earlier history loading renamed it and dropped both the expansion and the scroll anchor; it is now keyed to the human message the run follows. Find and scroll restore land inside a collapsed run, so that run opens the way a matched turn fold does, and a sender filter no longer collapses the rows it just kept. Plans, renders and viewed images stay on screen instead of reading as one update. Expansion resets when the thread changes, since pill ids repeat across threads. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
A secret or a link is answered only on its own card, and every other fold already leaves those cards on screen. The activity collapse folded them in with the surrounding agent work, so a standing thread showed a count instead of the form. They now stay visible. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A coordinator thread (CoS and the other standing bots) buries the founder's own messages under agent relays, automations, system notices and the work between them, so it is hard to see where he left off.
14 agent updates · click to expand. The founder's messages, guests' messages and the model's replies to them stay in place.Human conversation(the default for a standing thread) andAll activity. The choice is remembered per thread in local storage; ordinary threads are unchanged and show everything.Test plan
collapseTimelineActivityunit tests: collapsing runs between human turns, restoring rows exactly on expand, a thread of only activity, mixed-kind summaries, and a human-only thread left untouched.pnpm --filter @t3tools/web typecheckclean.useThreadActionMenu.test.ts, fails to load with avi.mockofreactmissingcreateContext; verified failing identically onrelease/native-0.1.10before this change.vi.mockrejection aborts the run. The two suites this change touches passed on their own.Deploy: web
🤖 Generated with Claude Code