CopilotKit / CopilotKit/OpenBot

[Feature Request] Please add Agent management - pin, hide, duplicate

Open
#323 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
5.2k
Forks
655
Avg merge
11h 56m
Merged PRs (30d)
370

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.