[Feature]: Add an environment filter to the Sidebar

[ArionStudio]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

apps/desktop

Problem or use case

The Sidebar can currently filter threads by project, but it cannot filter them by environment. I need to narrow the thread list to one connected environment.

Proposed solution

Add an environment filter alongside the existing project filter in the Sidebar.

The filter should offer:

• All environments
• Each configured environment

Selecting an environment should filter the existing thread list by that environment. The environment and project filters should work together when both are selected.

Why this matters

This would let users with multiple connected environments focus on the threads from one environment while keeping every environment connected and available.

Smallest useful scope

Add a single-select environment filter with All environments as the default.

It should apply consistently to drafts, search results, and the existing pinned, active, snoozed, and settled thread sections. It should not introduce new grouping or sorting behavior.

Alternatives considered

None.

Risks or tradeoffs

The environment filter must interact predictably with the existing project filter. If changing environments makes the selected project unavailable, the project filter should reset to All projects.

Changing the environment filter should also clear any selected thread rows so hidden threads cannot remain selected for bulk actions. If the selected environment is removed, the filter should reset to All environments.

Examples or references

None.

Contribution

• I would be open to helping implement this.

[juliusmarminge]

#8915 adds a Windows 11 reproduction: when multiple environments share a project, the desktop sidebar cannot filter by environment even though Android already offers that filter. Consolidating the report here so the desktop/Android parity case stays with this request.

[SwiggitySwerve]

Following up from #18504 with one filter case I hit while running several machines. I've left it as review notes on #8530:

• Hiding the environment a scoped project lives in clears the persisted project scope, but the environment filter itself is session-only. After a reload the filter is back to "All environments" and the scope is gone. Keeping the scope and showing the existing empty state while it's filtered out would avoid that.

The single-select prototype I built for reference is here. It isn't a competing PR.

[tobiasheckmann]

+1, with an orchestration use case that isn't in this thread yet.

I use T3 Code on my Mac as the front door and a remote Linux server as the worker. From the Mac I send many agent threads to the server. I want to be able to reach them, but I don't want to watch them all the time, and they bury the few Mac threads I'm actively steering. The same repos are cloned on both machines, so filtering by project doesn't separate them. The iOS app already filters by environment, so on my phone this is solved; the macOS app is where it's missing.

What would fix it: the environment filter proposed here, remembered across reloads (as noted in the #8530 review), and ideally multi-select so I can hide one environment.

[boblangley]

I have a similar use case - but it is work vs personal.

I occasionally want to check my personal remote threads during work, but having my work computer show all of the personal threads is distracting when I don't want it to be. Adding this functionality to the desktop app would be a god send.

[ArmandoRl1]

+1, and here's a variation that I don't think anyone has suggested yet: an option to hide threads from disconnected environments automatically.

I connect my work machine to T3 Code on my personal setup. When I'm off work, the work machine is off or unreachable, but its threads still fill up my sidebar. I don't want to see them then, and they're no use anyway because I can't act on threads from an offline environment (see #24563).

A manual environment filter (#8530 / #25069) would help, but I'd have to remember to switch it every evening and every morning. What I'd really like is a setting like:

• Settings -> Environments -> "Hide threads from disconnected environments" (global or per environment)

With it on, a disconnected environment's projects and threads would disappear from the sidebar and come back when it reconnects.

[psicilia5179]

+1 from a desktop user with seven environments: this laptop, five Linux servers and a Windows PC, all connected to one desktop app. Several repos are cloned on more than one of them, so filtering by project doesn't separate them.

The iPhone app already does this. Same threads, two clients:

On iOS there's an "All environments" filter next to "All projects", and it stays available while searching. On the Windows desktop app (0.1.5) there's only the project filter.

#8530 was verified as-is on 2026-10-31, and #25069, #29686 and #30730 take other approaches. As I read CONTRIBUTING, none of them can land until the direction here is approved. Could a maintainer pick one? A single-select filter like #8530 covers my case; per-environment checkboxes like #25069 would be even better with this many machines.

Drafted with Claude Code (Claude Opus 5.5).

[vycdev]

Adding a related use case: I'd love an option to hide threads from machines that aren't reachable.

I have a PC that's often off, and its threads just sit in my list even though I don't care about them right now. I can't snooze or settle them either, because that needs the machine to be connected (#24532 / #24917, #24563). So they're stuck in my face until I turn that PC back on.

A manual environment filter would help, but what I really want is something like:

• A toggle like "Hide offline machines" (or a per-machine "hide while offline" option)
• The threads come back on their own once the machine reconnects
• Maybe a small "N threads hidden from offline machines" note so they're not completely invisible

This plus letting snooze/settle work offline (#24917) would fix most of my annoyance with multiple machines.

[prince-eventual]

I built a working version of this in the web client and use it locally. Short demo attached.

• Environment chips sit inside the existing project filter popup, and only show when projects live on 2 or more environments.
• They narrow the thread list, folders, search and the drafts count. The choice is saved per client, next to the project filter. No server or contract change.
• Same idea as the environment filter that the iPhone and Android apps already have.

My case: several machines connected, with the same repos cloned on more than one, so the project filter can't separate them.

Would you approve this direction and scope? If yes, I'll open a focused PR for the environment filter only. I also made project rows act as checkboxes ("All projects" shows all checked, a click toggles one, the popup stays open). That overlaps #30775, so I'd keep it separate or leave it to that PR.

[Haim098]

+1 from a Windows desktop user. I have both my desktop PC and my laptop connected to the same T3 Code app, and several of the same repos exist on both machines. When I'm working on the desktop I only want to see the desktop's threads, but the sidebar mixes in everything from the laptop, and the project filter can't separate them because the projects have the same names on both.

An environment/machine filter next to the project filter (ideally multi-select, like the project filter) would solve this. The mobile apps already have it; the desktop app is where it's missing.

[chomamateusz-agent]

🤖 Notes on behalf of Mateusz (chomamateusz), who has used a multi-select machine filter in the desktop app every day since late October, across five environments (two Macs, three Linux servers). This is not a competing PR. These are the behaviour choices that settled the open questions in this thread, in case they help pick a direction for #8530 / #25069 / #29686:

• Multi-select, persisted per client. A plain click shows only that machine, and a second plain click on the only selection clears it. Cmd-click on macOS (Ctrl-click elsewhere) adds or removes one machine. Selecting every machine is the same as "All machines". The project filter uses the same click model, so one habit covers both.
• Saved machines survive going offline. An offline or unknown machine stays in the saved set but is ignored for filtering, so the filter survives reloads and machines dropping off (the problem raised in the feat(web): filter sidebar threads by environment #8530 review). A saved set with no known member behaves as "All machines" instead of showing an empty sidebar.
• Machine and project filters intersect. A project stays selectable if any copy of it lives on a selected machine. If the intersection is empty, the project filter is ignored instead of showing nothing.
• One filter, applied everywhere the list is derived: drafts and their counts, search, settled pagination and counts, folders, and keyboard/jump order.
• With one machine selected, project names, icons and the settings target describe that machine's copy of the project.
• Opening a hidden thread (link, command palette) clears only the machine filter, not the project filter.
• New thread from the sidebar starts on the selected machine (an online one first when several are selected).
• Shown only with two or more known environments; no server or contract change.

The "hide threads from offline machines" request above fits as a separate toggle on top of a manual filter, since a manual filter alone has to be switched every morning and evening.