[Feature Request] Please add Agent management - pin, hide, duplicate
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start at the existing /agents list UI and trace how user preferences, Agent duplication, and the audit trail are currently handled. Confirm where pin, hide, and duplicate actions belong, then verify the acceptance criteria for per-user state, unique duplicated Agents, hidden and pinned sections, and audit entries.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- TypeScript
- Stars
- 6.6k
- Forks
- 914
- Avg merge
- 22h 44m
- Merged PRs (30d)
- 137
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CopilotKit/OpenBot
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
CopilotKit/OpenBot#815 ·
Maintainers usually reply within 1 day
-
Wrong key location at startupPossibly taken @charan-rathore claimed this 4 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 68/100
CopilotKit/OpenBot#800 ·
Maintainers usually reply within 1 day
-
setup-learning.ts fails on Windows with "spawn npx.cmd EINVAL"Possibly taken @Caldas claimed this 7 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
CopilotKit/OpenBot#792 ·
Maintainers usually reply within 1 day
-
Remote AG-UI Bots can't use the browser in chat: `computer_*` calls refused as "unavailable for this headless turn"Possibly taken @charan-rathore claimed this 3 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 68/100
CopilotKit/OpenBot#804 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 Over a week Newbie friendliness 22/100
CopilotKit/OpenBot#786 ·
Maintainers usually reply within 1 day
All issues in CopilotKit/OpenBot
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
paperclipai/paperclip#17151 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
AgoraIO-Extensions/agent-infra#3159 ·
Maintainers usually reply within 1 day
-
blocklist addition
Difficulty 1/5 Under an hour Newbie friendliness 66/100
MetaMask/eth-phishing-detect#304596 ·
Maintainers usually reply within 1 day
-
friction
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
kentcdodds/kody#4142 ·
-
[Bug] Statistics | Task statistics are always empty on MikroORM with MySQL or SQLitePossibly taken @NdekoCode claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ever-co/ever-gauzy#11214 ·
Maintainers usually reply within 1 day