Enable fact and instruction memories from Chat admin settings without agents or actions
メンテナーはふだん 1 日以内に返信
@paullizer がすでに取り組んでいます。
2026年8月25日 から。
評価
この issue はまだ評価されていません。
説明
Summary
Move the fact/instruction memory control out of Agents & Actions → Actions and surface it in Chat → Chat Experience, so admins can enable memory for the normal chat experience without turning on agents or actions.
This follows the same pattern already used for Tabular Processing: the capability is owned by the tab it actually belongs to, and the Actions pane keeps a read-only dependency note pointing at it.
User Value
Today enable_fact_memory_plugin is only reachable from the Actions tab and is labeled "Enable Fact Memory Action". An admin who never enables agents has no reason to open that tab, so they never discover the switch — even though memory recall already works in plain chat and users can manage entries in Profile.
Framing memory as a chat capability makes it discoverable for the large set of deployments that run plain chat, and removes the false implication that agents are a prerequisite.
Proposed Behavior
enable_fact_memory_pluginremains the single settings key (no new key, no migration).- Admin Settings → Chat → Chat Experience gains a Fact Memory card (
fact-memory-section) containing the live toggle, with copy stating plainly that it works without agents or actions, that users manage entries in Profile, and that the assistant can save or remove memories when asked. - Admin Settings → Agents & Actions → Actions replaces its toggle with a read-only note pointing at Chat, matching the existing
tabular-processing-dependency-notetreatment. - The Chat toggle saves through the main admin settings form;
POST /api/admin/plugins/settingsmoves the key from required to deprecated-optional so it is accepted but no longer written by that endpoint. - With the toggle on and agents off, normal chat also supports explicit memory creation and removal ("remember that I prefer bullet points", "stop calling me Paul") using the existing Semantic Kernel machinery via a small memory-only kernel pass, gated by a cheap intent pre-filter so ordinary turns take no extra model call.
Acceptance Criteria
- The fact memory toggle renders in Chat → Chat Experience and saves through the admin settings form.
- The Actions pane shows a read-only note instead of a toggle, and reflects current state.
- Toggling any other core plugin no longer clobbers
enable_fact_memory_plugin. -
POST /api/admin/plugins/settingsaccepts requests that omit the key, and ignores it when present. - With agents disabled, an explicit user request to remember, change, or forget something persists through
FactMemoryStorein the authorized chat scope. - Standard and streaming chat paths behave consistently, and memory activity surfaces as a chat thought.
- Memory writes never break the chat response — failures degrade silently and are logged.
- Functional regression coverage validates admin placement, save wiring, intent detection, and the memory pass.
- Documentation, docs inventory, and release notes are updated at the configured app version.
Notes
Related to #1153, which covers the broader normal-chat memory creation experience including inferred memory proposal cards with approve/deny/edit. This issue delivers the admin-settings relocation plus the explicit save/update/forget path; the inferred-proposal card UI remains tracked in #1153.
Relevant areas:
application/single_app/templates/admin/_panes/chat-experience.htmlapplication/single_app/templates/admin/_panes/actions.htmlapplication/single_app/admin_settings_nav.pyapplication/single_app/static/js/admin/admin_settings.jsapplication/single_app/route_backend_plugins.pyapplication/single_app/route_frontend_admin_settings.pyapplication/single_app/route_backend_chats.pyapplication/single_app/semantic_kernel_plugins/fact_memory_plugin.pydocs/admin/chat.md,docs/admin/agents-actions.md,docs/_data/features.yml
Hazard found during planning: the Actions toggle currently saves through POST /api/admin/plugins/settings, where enable_fact_memory_plugin is a required field. Removing the input without updating admin_settings.js would make the payload send false, so changing any unrelated core plugin would silently disable fact memory.
- 主要言語
- Python
- スター
- 157
- フォーク
- 117
- 平均マージ
- 4時間 15分
- マージ済み PR（30日）
- 208
環境構築
このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
microsoft/simplechat のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
microsoft/simplechat#1491 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
microsoft/simplechat#1370 ·
メンテナーはふだん 1 日以内に返信
-
Simple Chat - NLRオープン
難易度 3/5 1〜2日 初心者へのやさしさ 55/100
microsoft/simplechat#1804 ·
メンテナーはふだん 1 日以内に返信
-
Simple Chat - NLRオープン
難易度 3/5 1〜2日 初心者へのやさしさ 48/100
microsoft/simplechat#1803 ·
メンテナーはふだん 1 日以内に返信
-
V2: triage multi-turn UI failures and make saved-memory orchestration validation reliable対応中かも @paullizer が 1 日前に担当しました。 オープンbug P1
microsoft/simplechat#1785 · 担当者 1 名 ·
メンテナーはふだん 1 日以内に返信
microsoft/simplechat の issue をすべて見る
似ている issue
-
[Bug] Unit tests reach real Bedrock call paths without patching the model対応中かも @proton0210 が今日担当しました。 オープンbug
難易度 2/5 1〜3時間 初心者へのやさしさ 67/100
aws-samples/sample-aws-genai-db-modernizer#1318 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
pyarrow-25.0.1-cp310-cp310-manylinux_2_28_x86_64.whl: 1 vulnerabilities (highest severity is: 5.3)オープンMend: dependency security vulnerability
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
capitalone/locopy#394 ·
-
[Bug] Unhandled ValueError terminates watchdog thread when GISRC value contains multiple colonsオープンbug
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
メンテナーはふだん 1 日以内に返信
-
sdk-typescript: unquoted COPY globs in shell form are silently dropped from the image build contextオープンbug javascript
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
enhancement
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
ietf-tools/datatracker#11922 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信