TASIP-009: Agent labels & grouping

[ryw]

Status: Draft — open for input · Category: Enhancement

Summary

Group the agents list and dashboards by label (sales, support, compliance) so a large agent footprint stays navigable, and use labels to scope things like which Slack app can launch which agents. Labels already exist on agents; this adds the group-by views.

Why

Past ~20 agents, a flat list stops working. Teams think in terms of function and ownership, and the UI should let them slice by that.

Sketch

• A group-by toggle on the agents inventory and dashboard, keyed on labels.
• Filters and saved views by label.
• Reuse labels for access/launch scoping where it helps.
  (Provisional — the shape changes based on the discussion.)

Open questions

• One label or many per group view?
• Should labels drive permissions, or stay purely organizational?
• Default grouping for a new workspace?

How to help

React 👍 if you want this, and comment with your use case, constraints, or pushback. This is a draft Tembo Agent Studio Improvement Proposal (TASIP); your input shapes it before it becomes scheduled work.