Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

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

未關閉
#323 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 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.6k
分支
914
平均合併
19 小時 22 分鐘
30 天內合併 PR
140

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 有 Pull Request 範本
  • 沒有貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

CopilotKit/OpenBot 的其他 Issue

查看 CopilotKit/OpenBot 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。