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

[Feature Request] Please add Per-Agent memory panel — view/edit skill files in chat

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

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
38/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
typescript
領域
frontend

研究方向

從聊天介面開始,追蹤所選 Agent、skill 或指示檔案,以及現有稽核軌跡的呈現方式。一起定義面板、內嵌編輯、驗證、版本歷程、存取控制,以及下次執行時的套用;完成表示七項驗收標準全部運作,且不變更授權或啟用任意程式碼執行。

由索引模型根據 Issue 內容生成。

描述

Problem

OpenBot has persistent coworkers, per-Agent computers, governed tool use, and auditability, but it lacks a visible, editable panel for an Agent's skill/instruction files alongside the chat interface.

For users managing multiple Agents with different roles (e.g., newsletter orchestrator, site monitor, research assistant), there is no way to quickly view or edit an Agent's skill file (e.g., SKILL.md-equivalent config) without leaving the chat or editing YAML directly. This makes it harder to refine Agent behavior iteratively or audit what instructions an Agent is operating under.

Feature request

Add Per-Agent memory panel — a viewable, editable panel next to the chat that surfaces an Agent's skill/instruction file. This should be a UI-layer feature, not a new learning infrastructure.

Proposed behaviour

  • Show a collapsible panel next to the chat displaying the Agent's current skill/instruction file.
  • Allow editing the skill file inline, with syntax highlighting for Markdown/YAML.
  • Save edits immediately and apply them to the next run (no reload required).
  • Show version history (last N edits) with timestamps and author.
  • Support optional diff view to compare current vs. previous versions.
  • Preserve all governance settings (grants, policies) — editing the skill file does not change grants.

Required controls

  • Disabled by default; enabled per Agent.
  • Panel scope: per-Agent, visible only to users with access to that Agent.
  • Immutable audit log showing when a skill file was viewed, edited, or reverted.
  • Review, edit, and revert controls for skill file changes.
  • Clear separation between skill file content and runtime state (no arbitrary code execution from edits).
  • Never automatically grant additional tools or permissions on edit — grants are unchanged.
  • Configurable version history retention (e.g., keep last 50 edits).

Why this matters

This would make OpenBot more competitive for users managing multiple Agents with distinct roles 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 wants to refine Agent instructions iteratively (e.g., "add this checklist to the newsletter Agent") without recreating the entire configuration.

Acceptance criteria

  1. A user can view an Agent's skill/instruction file in a panel next to the chat.
  2. A user can edit the skill file inline and save changes.
  3. Edits are applied to the next run without requiring a reload.
  4. Version history shows the last N edits with timestamps and authors.
  5. All skill file views/edits appear in the existing audit trail.
  6. Invalid skill file edits are rejected with clear error messages.
  7. Edited skill files respect the Agent's existing grant boundaries.

Suggested name

Agent Memory Panel or Editable Skill Files

主要語言
TypeScript
星號
6.6k
分支
914
平均合併
22 小時 44 分鐘
30 天內合併 PR
137

環境準備

  • 提供 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 摘要。