Skip to content

Dashboard: per-agent workspace nesting + collapse-a-whole-agent #101151

Description

@100yenadmin

Organize the dashboard by agent, not by whichever tab happened to get added last.

Part of the Modular Dashboard roadmap — see the tracker #101136. Builds on Wave 1 (#101093; PRs #101094 / #101097 / #101098).

Problem

Operators running many agents end up with sprawling tab strips and widget grids where it's unclear which agent produced what. There's no way to see, or collapse, a whole agent's surface at once — every tab competes for the same flat space.

What this adds

  • Group tabs and widgets by the agent that created them.
  • A collapse/expand control for an entire agent's tabs in the tab strip.

How it'd be built

createdBy provenance already exists on tabs and widgets in workspace.json — this is a grouping layer on top, not a new data model. Add a group-by-agent view plus a collapse-agent control in the tab strip (ui/src/pages/plugin/dashboard-view.ts).

References

Tier 3 — control-hub / multi-user.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:ux-frictionUser-facing flow adds avoidable confusion or support burden without fully blocking progress.issue-rating: 🌊 off-meta tidepoolIssue quality rating does not apply to this item.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions