[FEATURE] Agents view: add search/filter to find sessions by name or prompt
Status Open
Maintainer reply ✓ Yes — bcherny
Workaround ✓ Mentioned in description ↑
Activity 4 comments · opened Jun 1, 2026
💡 Likely answer: A maintainer (bcherny, collaborator)
responded on this thread — see the highlighted reply below.
Summary
The claude agents view (FleetView) has no way to search or filter the session list. When you have many sessions running or in history, there's no way to quickly find one by name or task description.
Desired behavior
Add a search/filter input to the agents view — similar to how the session picker (/resume) supports pressing / to filter by name or first prompt content. Ideally:
- Press
/or start typing to enter search mode - Filter sessions by name or task description in real time
- Works across all sessions visible in the current view
Current workaround
None — you have to scroll through the full list manually.
Related issues
- #60437 — sessions from daemon-fleet don't appear in agent view at all
- #61134 — request to group sessions by working directory
4 Comments
This would be helpful for sure :)
This is a must have IMHO, I spend too much time searching for prompts.
What makes this worse is that there's no way to rename a session automatically when it opens. Session names are derived from the session, so running the same command twice can produce different names, and spotting the right session becomes guesswork.
Agent view already has some filtering: type in the dispatch input with a prefix, e.g.
s:workingors:blockedfor state,a:<name>for the agent,#123or a PR URL for the session on that PR, or any other URL to find the session whose first prompt contained it. You can add extra words after a prefix to narrow by name or task text. Bare text without a prefix is treated as a new task to dispatch, so there isn't a dedicated free-text search yet; leaving this open for that. Docs: https://code.claude.com/docs/en/agent-view#filter-sessions🤖 Generated with Claude Code
Thank you for the tips but in practice this is not enough. I usually launch sessions with:
After tens of sessions, it becomes very hard to spot the right one in Agent View — sessions launched with the same command end up with similar generated names (which cannot be specified in the command unfortunately), and the current filters (a:, s:, #<number>/PR URL) don't
help: a: matches agent name, and #<number> only matches a PR the harness has separately linked as "working on," not the ticket/PR argument the session was actually launched with.
Ideally, I would like to filter by identifier — e.g. JIR-3064 or \#1217 — or by any text that was given as input to the first prompt or slash-command args. Essentially, extend the existing "any other URL matches the first prompt" behavior to a general substring match, so ticket keys, PR numbers, and arbitrary text all work as session filters.