[Feature Request] Please add Agent management - pin, hide, duplicate
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 42/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
- 领域
- frontend
调研方向
从现有的 /agents 列表 UI 开始，跟踪当前如何处理用户偏好、Agent 复制和审计跟踪。确认固定、隐藏和复制操作应放在哪里，然后验证每个用户的状态、唯一的重复 Agents、隐藏和固定分区以及审计条目的验收标准。
由索引模型根据 Issue 内容生成。
描述
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
- 主要语言
- TypeScript
- 星标
- 6.3k
- 派生
- 863
- 平均合并
- 17 小时 52 分钟
- 30 天内合并 PR
- 155
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
CopilotKit/OpenBot 的其他 Issue
-
Wrong key location at startup可能已有人在做 @charan-rathore 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 68/100
CopilotKit/OpenBot#800 ·
维护者通常 1 天内回复
-
setup-learning.ts fails on Windows with "spawn npx.cmd EINVAL"可能已有人在做 @Caldas 于 3 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 80/100
CopilotKit/OpenBot#792 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 68/100
CopilotKit/OpenBot#804 ·
维护者通常 1 天内回复
-
Five out-of-subject findings from PR #770's tier-3 review (credential-revoking tests, single-user boot gate, OAuth client rotation, shared-use atomicity, untyped server/tests)可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 4/5 一周以上 新手友好度 22/100
CopilotKit/OpenBot#786 ·
维护者通常 1 天内回复
-
server/tests leaks database connections: 55 files open a pool and never close it可能已有人在做 @adamsiwiec1 于 2 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 70/100
CopilotKit/OpenBot#785 ·
维护者通常 1 天内回复
查看 CopilotKit/OpenBot 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
auth: agent-bearer --manager-call is told to use the MCP instance argument on an ambiguous manager未关闭
难度 2/5 1-3 小时 新手友好度 80/100
维护者通常 1 天内回复
-
bug module: playback
难度 2/5 1-3 小时 新手友好度 68/100
chthollyphile/folia-major#739 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 90/100
-
难度 2/5 1-3 小时 新手友好度 78/100
agilepathway/label-checker#773 · 2 条评论 ·
维护者通常 1 天内回复