Feature request: configurable agent view — project scoping, group sessions by repo (fold .claude/worktrees), settings surface like statusLine

Open 💬 0 comments Opened Jul 4, 2026 by misganawFolio

Environment

  • Claude Code v2.1.201 (claude agents TUI and desktop app Code tab)
  • macOS, multi-project + git-worktree workflow (worktrees under <repo>/.claude/worktrees/, created by Claude Code)

Feature request

Make the agent view configurable, the way the status line already is (statusLine in settings.json runs a user command and renders its output). Today the agent view has exactly one lever — the --cwd <path> launch flag — and no settings surface at all.

Concretely, in priority order:

  1. Scope to the current project from inside the view. claude agents --cwd works, but there is no in-UI toggle or settings key (e.g. agents.scope: "project" | "all"). When you live in one repo, sessions from every other project on the machine are noise.
  2. Group sessions by project, folding worktrees under their parent repo. Sessions running in <repo>/.claude/worktrees/<name> belong to <repo> — show them under one project header with the worktree name as a tag. Currently rows from all projects are interleaved within the state sections, and you cannot tell which project a row belongs to without opening it (#69449 is the open per-row-repo ask; #61134 asked for directory grouping and was closed).
  3. A settings surface for the view (settings.json agents.* keys), so preferences like the above persist instead of requiring launch flags — the same philosophy as statusLine: the harness owns the chrome, the user owns the layout/scope.

Why

The agent view is the control plane for the parallel-session workflow Claude Code promotes. The cwd for every session is already in the data model (claude agents --json exposes it), so filtering and grouping are presentation-layer changes. Users who want a project-scoped, grouped view currently have to build their own UI on top of claude agents --json — which most won't do, and shouldn't need to.

Related: #69449 (open), #61134, #61546, #60975 (closed), and #74138 (worktree recognition bug in the @ dispatch picker, filed separately).

View original on GitHub ↗