Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#483 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
python, sqlite
Área
api, backend, databases

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
13.3k
Forks
926
Merge medio
17 h 8 min
PR fusionados (30 d)
32

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de EverMind-AI/EverOS

Todos los issues de EverMind-AI/EverOS

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.