You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Agent-first view: one continuous conversation per project, sessions hidden
#24351
Use case: I run one long-lived assistant per project (about 20, one per role). I want to open a project and talk to it as one continuous conversation, like a chat bot. Today every new session becomes a new thread in the sidebar, so each project ends up with a pile of near-identical threads that I archive by hand.
What I would like:
A per-project option ("Agent mode" / "Single conversation").
The sidebar shows one entry per project; opening it resumes the same conversation.
New sessions, compactions and provider restarts happen under the hood and are not listed; old sessions stay reachable from a history view.
Orchestrator child tasks (delegate_task) already stay out of the sidebar, which is the behaviour I want for the main conversation too.
Workaround today: one project and one thread per bot, idleCompaction: onReturn, manual archiving.
Related:#19657 (hidden subagent threads), #24342 (orchestrator MCP can't reorder threads). I found no existing request for this.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Use case: I run one long-lived assistant per project (about 20, one per role). I want to open a project and talk to it as one continuous conversation, like a chat bot. Today every new session becomes a new thread in the sidebar, so each project ends up with a pile of near-identical threads that I archive by hand.
What I would like:
delegate_task) already stay out of the sidebar, which is the behaviour I want for the main conversation too.Workaround today: one project and one thread per bot,
idleCompaction: onReturn, manual archiving.Related: #19657 (hidden subagent threads), #24342 (orchestrator MCP can't reorder threads). I found no existing request for this.
All reactions