Skip to content

Add support for settling threads - #408

Merged
Tryanks merged 1 commit into
Tryanks:mainfrom
guivieiras:pr/settled-threads
Sep 11, 2026
Merged

Tryanks merged 1 commit into
Tryanks:mainfrom
guivieiras:pr/settled-threads

Conversation

@guivieiras

Copy link
Copy Markdown
Contributor

Finished threads currently stay mixed with work that still needs attention. This adds a Settled status so you can set them aside without archiving them or losing their conversation, agent connection, terminals, or working folder.

A thread’s menu can mark it and its child threads as Settled, or make them active again. Threads cannot be settled while they or their children are working, have messages waiting to send, or need input or approval. New work makes the receiving thread and its settled parents active again.

Recent and By project show settled threads in separate groups on wide and narrow screens. The groups start closed and open when you select a settled thread. Active child threads remain visible. Settled threads stay searchable and are not archived automatically. English and Simplified Chinese labels and the design guide have been updated.

The new tests cover keeping the settled status after a restart, refusing to settle busy threads, making threads active when new work arrives, showing the groups correctly, and keeping settled threads out of automatic archiving.

Before After
image image

Implemented with GPT-6 Astra in Tcode

Persist settled state separately from archive state, guard busy thread families, and reactivate them when input is accepted. Add shared-client actions, collapsible groups, translations, and lifecycle coverage.

(cherry picked from commit 0bafaac)
@Tryanks
Tryanks merged commit ca523aa into Tryanks:main Sep 11, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants