{"version":"2.1.295","anchor":"session-list-api-accepts-statuses-and-a-request-reason","canonical_anchor":"session-list-api-accepts-statuses-and-a-request-reason","heading":"Session lists can be filtered by status on the server","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/session-list-api-accepts-statuses-and-a-request-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Session lists can be filtered by status on the server\n\nClaude Code can now ask the server for only sessions with certain statuses, and says why it is making the request\n\n**What**\n\nA session is one conversation with Claude Code. When Claude Code asks the server for a list of sessions, it can now ask for only those with certain statuses. It also sends a short note with the request saying why it is being made.\n\n**Why**\n\nThe server can now do the filtering, instead of Claude Code fetching every session and picking out the ones it needs.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}