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
Thread search: opt in to archived and subagent threads, and search all linked environments in one call
#31289
I use thread search more than anything else: "find the session where we talked about X", across everything my agents did. Two small additions would make it the archive I need.
1. Opt-in scope.messageHitsQuery in apps/server/src/orchestration-v2/ThreadSearch.ts skips archived threads (archived_at IS NULL) and every thread whose lineage.relationshipToParent is subagent. Every delegate_task child carries that relationship, so the reviewers and builders an orchestrator starts can never be found, and settling plus archiving makes a thread disappear from search. An option (includeArchived, includeSubagents) on the search RPC and on the MCP t3_thread_search tool, off by default, keeps the normal search fast and clean while letting history searches reach everything.
2. One fan-out.t3_thread_search already takes an environmentId, so the routing exists. One call that searches all linked environments, merges newest first and names any environment that failed would turn per-machine search into one search across my machines.
Use case: an agent asked "what did the reviewer find last week" today cannot answer from T3, because the reviewer was a delegated task and the thread is archived.
Happy to help with a PR if the direction is approved.
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.
I use thread search more than anything else: "find the session where we talked about X", across everything my agents did. Two small additions would make it the archive I need.
1. Opt-in scope.
messageHitsQueryinapps/server/src/orchestration-v2/ThreadSearch.tsskips archived threads (archived_at IS NULL) and every thread whoselineage.relationshipToParentissubagent. Everydelegate_taskchild carries that relationship, so the reviewers and builders an orchestrator starts can never be found, and settling plus archiving makes a thread disappear from search. An option (includeArchived,includeSubagents) on the search RPC and on the MCPt3_thread_searchtool, off by default, keeps the normal search fast and clean while letting history searches reach everything.2. One fan-out.
t3_thread_searchalready takes anenvironmentId, so the routing exists. One call that searches all linked environments, merges newest first and names any environment that failed would turn per-machine search into one search across my machines.Use case: an agent asked "what did the reviewer find last week" today cannot answer from T3, because the reviewer was a delegated task and the thread is archived.
Happy to help with a PR if the direction is approved.
All reactions