Memory Delete

goodmem memory delete

Delete one or more memories

Synopsis

Delete memories from the GoodMem service in one of two modes:

ID mode: provide one or more memory IDs as positional arguments.
Filter mode: provide --space-id and at least one of --status or --filter, with no positional IDs.

goodmem memory delete [memory-id...] [flags]

Examples

  # Delete a single memory (with confirmation prompt)
  goodmem memory delete 123e4567-e89b-12d3-a456-426614174000

  # Delete multiple memories at once (with confirmation prompt)
  goodmem memory delete 123e4567-e89b-12d3-a456-426614174000 456e4567-e89b-12d3-a456-426614174001

  # Delete by status within a space
  goodmem memory delete --space-id 123e4567-e89b-12d3-a456-426614174000 --status FAILED

  # Delete by metadata filter within a space
  goodmem memory delete --space-id 123e4567-e89b-12d3-a456-426614174000 --filter "CAST(val('$.source') AS text) = 'email'"

  # Delete by status and metadata filter within a space
  goodmem memory delete --space-id 123e4567-e89b-12d3-a456-426614174000 --status COMPLETED --filter "CAST(val('$.kind') AS text) = 'invoice'"

  # Delete without confirmation prompt
  goodmem memory delete --force 123e4567-e89b-12d3-a456-426614174000

Options

      --filter string     Filter-based delete: server-side metadata filter expression
  -f, --force             Skip confirmation prompt
  -h, --help              help for delete
      --space-id string   Space ID for filter-based deletes (required when no memory IDs are provided)
      --status string     Filter-based delete: processing status (PENDING, PROCESSING, COMPLETED, FAILED)

Options inherited from parent commands

      --api-key string   API key for authentication (can also be set via GOODMEM_API_KEY environment variable)
      --server string    GoodMem server address (gRPC API)

Memory Delete

goodmem memory delete

Synopsis

Examples

Options

Options inherited from parent commands

SEE ALSO

On this page