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

memory: add POST /api/v2/memory/delete so everos-mcp forget_session works on self-hosted servers

オープン
  • 何か問題がありますか？
#483 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

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

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
12/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
活発
技術スタック
python, sqlite
領域
api, backend, databases

調査の方向性

Design work, not a first task. The issue says the Cloud side is a placeholder and the three open questions (derived-data handling, cascade through the markdown/SQLite/LanceDB stores, filter semantics) are unresolved. Read the existing cascade path for deleted change events in this repo to see how a batch delete would reuse it. Done means those questions are answered in the issue thread and the POST /api/v2/memory/delete contract is agreed with the maintainers.

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

説明

enhancement

Context

The official MCP server everos-mcp exposes a forget_session tool that calls POST /api/v2/memory/delete with {session_id, app_id, project_id} to delete everything one connection stored. Self-hosted EverOS has no such route, so the tool currently degrades to a message ("this deployment does not support deleting memories through the API"), verified against a local server on 2026-10-10. No crash, but self-hosted users cannot delete through MCP.

Cloud contract to align with

evermind-everos-cloud/docs/api.md §7 defines the endpoint:

  • POST /api/v2/memory/delete, success 204 with no body
  • filters: user_id XOR agent_id, session_id, sender_id; at least one of user_id / agent_id / session_id
  • three-state semantics per field: omitted = skip the filter, null/"" = match empty, value = exact match

The same doc marks the Cloud implementation as a placeholder (returns 204, deletes nothing; semantics to be landed by the pipeline owner). So this is not yet a contract gap to close in a hurry; it is a feature both sides still have to define.

Open questions before implementing

  1. What a session-scoped delete removes. Episodes under the session are the obvious part. Atomic facts, profile clusters and agent cases were derived from those episodes by the offline pipeline — delete them too, recompute them, or leave them? (everos-mcp documents that the profile and learned skills survive forget_session.)
  2. Three stores, one delete. Markdown is the source of truth; SQLite state and LanceDB rows must follow. The cascade already handles deleted change events for single files; a batch delete should go through the same path rather than touch the index directly.
  3. Filter semantics. Whether to implement the full three-state filter from day one or only the session_id (+ owner) shape that everos-mcp sends.

Suggested path

Wait for the Cloud pipeline owner to land the deletion semantics, then implement the same contract here (route + service + markdown delete + cascade propagation), and remove the "not supported" branch in everos-mcp's forget_session. Until then the MCP docs state the limitation.

Refs: EverOS-MCP src/everos_mcp/client.py::delete_session, src/everos_mcp/server.py::forget_session.

主要言語
Python
スター
13.3k
フォーク
926
平均マージ
17時間 8分
マージ済み PR（30日）
32

環境構築

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

はじめの一歩

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

EverMind-AI/EverOS のほかの issue

EverMind-AI/EverOS の issue をすべて見る

似ている issue

Python の issue をもっと見る

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

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