Problem
OpenBot has persistent coworkers, per-Agent computers, governed tool use, and auditability, but it lacks basic Agent management controls in the UI.
For users running multiple Agents for different tasks (e.g., newsletter, site monitoring, research), there is no way to pin frequently-used Agents to the top, hide inactive ones, or duplicate an existing Agent to create a variant. This makes it harder to organize a growing Agent roster and slows down daily workflows.
Feature request
Add Agent management controls — pin, hide, and duplicate — to the existing /agents list UI. This should be a UI-layer feature, not a new data model.
Proposed behaviour
Allow pinning an Agent to the top of the /agents list for quick access.
Allow hiding an Agent from the main list (still accessible via a "show hidden" toggle).
Allow duplicating an Agent to create a new Agent with the same configuration (role, tools, grants, skills, instructions), editable after creation.
Persist pin/hide state per user, not per deployment.
Show pinned Agents in a dedicated "Pinned" section at the top of the list.
Show hidden Agents in a collapsible "Hidden" section at the bottom.
Required controls
Disabled by default; enabled per user.
Pin/hide state stored in user preferences, not Agent configuration.
Duplicate creates a new Agent with a unique name and ID (no collision).
All pin/hide/duplicate actions appear in the existing audit trail.
Never automatically grant additional tools or permissions on duplicate — grants are copied as-is.
Configurable limit on pinned Agents (e.g., max 10) to prevent UI clutter.
Why this matters
This would make OpenBot more competitive for users managing multiple Agents while preserving its core advantages: per-Agent isolation, gateway policy enforcement, and action-level auditability. It would be particularly useful for a self-hosted team that runs 5+ Agents for different workflows and needs to organize them efficiently without recreating configuration from scratch.
Acceptance criteria
A user can pin an Agent to the top of the /agents list.
A user can hide an Agent from the main list.
A user can duplicate an Agent to create a new Agent with the same configuration.
Pinned Agents appear in a dedicated "Pinned" section.
Hidden Agents appear in a collapsible "Hidden" section.
All pin/hide/duplicate actions appear in the audit trail.
Duplicated Agents have unique names and IDs, with no configuration collisions.
Suggested name
Agent Management or Agent Organization Controls
Problem
OpenBot has persistent coworkers, per-Agent computers, governed tool use, and auditability, but it lacks basic Agent management controls in the UI.
For users running multiple Agents for different tasks (e.g., newsletter, site monitoring, research), there is no way to pin frequently-used Agents to the top, hide inactive ones, or duplicate an existing Agent to create a variant. This makes it harder to organize a growing Agent roster and slows down daily workflows.
Feature request
Add Agent management controls — pin, hide, and duplicate — to the existing /agents list UI. This should be a UI-layer feature, not a new data model.
Proposed behaviour
Allow pinning an Agent to the top of the /agents list for quick access.
Allow hiding an Agent from the main list (still accessible via a "show hidden" toggle).
Allow duplicating an Agent to create a new Agent with the same configuration (role, tools, grants, skills, instructions), editable after creation.
Persist pin/hide state per user, not per deployment.
Show pinned Agents in a dedicated "Pinned" section at the top of the list.
Show hidden Agents in a collapsible "Hidden" section at the bottom.
Required controls
Disabled by default; enabled per user.
Pin/hide state stored in user preferences, not Agent configuration.
Duplicate creates a new Agent with a unique name and ID (no collision).
All pin/hide/duplicate actions appear in the existing audit trail.
Never automatically grant additional tools or permissions on duplicate — grants are copied as-is.
Configurable limit on pinned Agents (e.g., max 10) to prevent UI clutter.
Why this matters
This would make OpenBot more competitive for users managing multiple Agents while preserving its core advantages: per-Agent isolation, gateway policy enforcement, and action-level auditability. It would be particularly useful for a self-hosted team that runs 5+ Agents for different workflows and needs to organize them efficiently without recreating configuration from scratch.
Acceptance criteria
A user can pin an Agent to the top of the /agents list.
A user can hide an Agent from the main list.
A user can duplicate an Agent to create a new Agent with the same configuration.
Pinned Agents appear in a dedicated "Pinned" section.
Hidden Agents appear in a collapsible "Hidden" section.
All pin/hide/duplicate actions appear in the audit trail.
Duplicated Agents have unique names and IDs, with no configuration collisions.
Suggested name
Agent Management or Agent Organization Controls