Skip to content

HTTP forget reports success for a memory that does not exist #596

Description

@kevintseng

POST /v1/forget for a memory that does not exist returns HTTP 200 with success: true and archived: false. The MCP forget tool returns an error for the same request, and the CLI exits 1.

Expected: HTTP reports a missing memory as an error, like MCP and the CLI.

Activity

  1. added
    needs-triageNot yet judged — the default entry point for a new issue
    on Oct 6, 2026
  2. kevintseng commented on Oct 9, 2026

    @kevintseng
    ContributorAuthor

    Fixed in #604 (c105280), shipped in v4.10.12.

    HTTP forget now returns 404 for a missing memory and 400 for a non-matching observation, instead of reporting a successful no-op. Successful operations and repeat archives retain their documented behavior.

    The corresponding regression tests are included in the verified release candidate and the successful release CI. Closing as completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-triageNot yet judged — the default entry point for a new issue

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions