[Idea] Add configurable per-space filtering for the Agents panel

[ShankyJS]

Problem

In v0.7.1 the Agents panel workspace/all filter was removed — the panel now always shows all agents across all spaces, with ui.agent_panel_sort only controlling ordering (spaces vs priority).

This becomes hard to use at scale. When running ~15 agents inside a single space, the panel gets crowded with every agent from every space at once, making it difficult to focus on the space I'm actually working in.

Request

Bring back per-space filtering, but as a configurable option rather than the always-on behavior it was before. Grouping/sorting alone doesn't solve crowding — I want the ability to scope the panel to only the agents in the current/active space.

Proposed shape

Something like a new ui.agent_panel_scope key:

• "all" (current behavior, default) — show all agents across all spaces
• "current_space" — show only agents belonging to the active space

This keeps the current default intact for people who preferred the change, while restoring the filtered view for those of us running many agents per space.

Why configurable, not removed

The v0.7.1 note suggests the filter was dropped to simplify the panel, but for high-agent-count workflows the filtered view is essential. Making it a config toggle satisfies both preferences without forcing one behavior on everyone.

---

Update — I built a working prototype 🐑

I went ahead and prototyped this on a branch in my fork: feat/per-space-agent-panel-filter.

It adds the ui.agent_panel_scope config key exactly as proposed above:

• "all" (default) — every agent across every space (unchanged current behavior)
• "current" — only agents in the active space (also accepts "current_space" / "space" as aliases)

On top of the config key there's a click toggle in the Agents panel header, so scope can be flipped without editing config. The default stays all, so nothing changes for people who preferred the v0.7.1 behavior.

Here's the sidebar with it running:

Happy to open a PR if a maintainer thinks this is worth pursuing — hopefully it inspires some interest!

---

Update - I built this as a plugin

#1406 (comment)

[StefanKarpinski]

+1 on this. The ui.agent_panel_scope shape — with all as the default so nothing changes for people who preferred the 0.7.1 behavior — is exactly right: configurable, not a re-removal of the current default.

My setup is the noisy-at-scale case this is about. I run several workspaces at once, each a different project/context, most with multiple agents — a "main" agent I'm actually driving plus background helpers (an unattended PR/CI-watch loop, etc.). When I'm working in one workspace I almost only care about that workspace's agents; the flat all-spaces panel gets long enough that it stops being scannable, which was the whole value of the panel for me.

grouped/priority ordering helps organize but doesn't fix the crowding — I still have to visually filter out every other workspace's agents. A current / current_space scope is the missing piece.

Since you've already got a working prototype on feat/per-space-agent-panel-filter (and there's a second local implementation mentioned in #859), this seems low-risk to land behind the config default. Would love to see it PR'd — thanks for building it!

[ShankyJS]

Thanks for the +1, would love to see this one coming through for sure. I've been using my protoype server for the last 2 days and it's been working flawlessly for me.

cc: @ogulcancelik

[boozedog]

@ShankyJS maybe you could go ahead and open the PR and see if @ogulcancelik accepts it?

love herdr! missing the current filter, it was great for my workflow

[rzssh]

fwiw i also have a patch here, been daily-driving it for a few days, seems to work just fine. just leaving it here as a minimal change example @ogulcancelik @ShankyJS

[iRonin]

We independently landed the exact same shape on our fork — ui.agent_panel_scope with "all" as the default ("current" / "current_workspace" for the filtered view). Three separate implementations converging on this key is a pretty strong signal for it. 🐑

As reference for whichever PR lands: ours scopes inside the single function both the sidebar render and keyboard agent-cycling route through (so nav stays in-space too), applied on live reload; within a space it orders by attention priority.

• Diff: feat: add ui.agent_panel_scope to filter the agents panel by current workspace iRonin/herdr#2
• Build: https://github.com/iRonin/herdr/releases/tag/v0.7.4-ironin.1

@ShankyJS looks furthest along — happy to compare notes or contribute tests.

[ogulcancelik]

next release will have plugin api so you can do any filter/sort logic on agent sidebar :) d30ab1b

[ShankyJS]

Now that the sidebar has proper filter/sort logic under the hood (the transient agent.view.set/clear queries that drive sidebar/keybind ordering), I just built the behavior the way I'd personally want it as a standalone plugin:

👉 https://github.com/ShankyJS/herdr-space-scoped-agents

herdr plugin install ShankyJS/herdr-space-scoped-agents

Fair warning: this is my personal preference, not a proposal for a default — but if you're in the same boat I described up top (running a bunch of agents per space and drowning in the panel), it might scratch the same itch.

What it does:

• Two modes that stick: current (scope the panel to the space you're in) and all (show everything). Your choice persists across space switches and restarts.
• It follows focus automatically, and I flip it with prefix+f — honestly that little toggle is the part I use most and it feels great.
• Drives herdr's agent.view API directly (0.7.5+), so there's no config fork — nothing in config.toml changes.

Cross-platform prebuilt binaries (macOS/Linux/Windows), MIT. Just sharing in case it helps someone with the same requirements.