Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Workspace memory: personal and organization memory for AI clients

クローズ
#1,151 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

関連するプルリクエストがすでにマージされています。

  • #1152 @helpcodeai による — マージ済み

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
github, postgresql, sql, typescript

調査の方向性

Read the follow-up issues #1145 and #1148, then inspect ee/licensing, the /mcp/:serverId tool registration, organization_members, and the Settings > Users and Memory areas. The proposal specifies scopes, access levels, approval flow, secret detection, and PostgreSQL full-text storage, but does not identify existing implementation files or tests. Done means delivering the licensed workspace memory feature across storage, MCP tools, access controls, and UI.

索引モデルが issue の本文から書いたものです。

説明

Follow-up to #1145 and #1148. Skills tell an AI client how a company works. What is missing is what it has learned: facts ("STAMMKUNDE means a customer with a framework agreement"), preferences of a person ("answer in Italian, numbers as tables") and notes an assistant should find again next week, in any client, for the same user or for the whole team.

Proposal

Workspace memory, available with an Enterprise licence (Cloud and self-hosted), gated like single sign-on: the code is in core, the licence check lives in ee/licensing.

Scopes

  • Personal: one member. Only that member can read it, admins included; admins can erase it (data protection) but not read it.
  • Organization: the company memory.
  • (Team scope via roles comes later.)

Kinds: fact, preference, note. Memory is served as data, never as instructions; skills stay the only instruction-grade content.

MCP tools (only on /mcp/:serverId; the shared /mcp toolset is unchanged), registered per member level:

  • memory_search(query, scope?): full-text search over the caller's personal memory and the active organization memory.
  • memory_save(content, kind, scope, tags?): personal directly; organization as a proposal or directly, depending on the workspace switch.
  • memory_forget(id): the caller's own personal items only.

Per-member access (organization_members.memory_access): inherit (workspace default) | none | read | personal | contribute. Default for the workspace is personal. Set one by one or in bulk under Settings > Users.

Workspace switch for organization writes from AI clients: approval (default, an admin or editor approves under Memory) or auto. Provenance (who, which server and client) is kept either way.

Safety: content that looks like a secret (API keys, tokens, passwords, private keys) is refused; size limits per item and per workspace; no cross-workspace access.

UI: a Memory page with "My memory", "Company memory" and "Pending" tabs, plus the workspace settings; a Memory column on Settings > Users.

Storage

New table memory_items (organization, scope, owner, kind, content, tags, status, source, author, approver, timestamps) with a Postgres full-text tsvector (simple configuration, multilingual) and a GIN index; new column organization_members.memory_access. No new dependency. Embeddings can come later as an option.

主要言語
TypeScript
スター
856
フォーク
82
平均マージ
7時間 39分
マージ済み PR(30日)
227

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

HelpCode-ai/anythingmcp のほかの issue

HelpCode-ai/anythingmcp の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。