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
Feature request: allProjects on t3_thread_search #40704
Problem: Called from inside a thread, t3_thread_search only searches the current project when projectId is left out. Unlike t3_thread_list, it has no allProjects option. To find a thread in another project by its message text, an agent has to call t3_project_list and then run t3_thread_search once per project. With N projects that's N+1 calls, and agents easily miss that the default is scoped and decide the thread doesn't exist.
Repro: From a thread in project A, call t3_thread_search({query: "<a phrase in a project-B thread's title>"}). Only project A threads come back. Adding project B's projectId finds it, and so does t3_thread_list({allProjects: true, titleContains: ...}). The list tool only matches titles, though, so it can't search message text.
Ask: Add allProjects?: boolean to t3_thread_search, the same as on t3_thread_list. When it's true, ignore the current-thread scoping and search every project, ranked the same way. Optionally, say in each result that it's scoped, for example by echoing the projectId searched, so agents know they didn't search everywhere.
Thanks for writing this up. It asks for new behaviour rather than reporting a defect, so it does not belong in the bug tracker and I'm closing it as not planned here. Feature ideas are discussed in Discussions: please post it there.
Activity
juliusmarminge commentedon Nov 22, 2026
Thanks for writing this up. It asks for new behaviour rather than reporting a defect, so it does not belong in the bug tracker and I'm closing it as not planned here. Feature ideas are discussed in Discussions: please post it there.