> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hyperspell.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Clear (soft-archive) a persisted edit

> Clear an edit — sets cleared_at and removes it from future overlays.

For ADD edits with a corresponding user-prompt stored on
ContextDocConfig.prompts[tier][key], also clear that prompt so the
prompts UI doesn't dangle an entry for a file that no longer exists.

Keeps the row around for audit. To restore, the user re-creates the
edit via PATCH /files.



## OpenAPI

````yaml https://app.stainlessapi.com/api/spec/documented/hyperspell.yaml delete /context-documents/tree/edits/{edit_id}
openapi: 3.1.0
info:
  title: Hyperspell API
  summary: >-
    Hyperspell is the memory layer for AI apps and agents. Through the API, you
    can add memories, connect data sources to index them in real-time, and
    search memories with our natural language query engine.
  termsOfService: https://hyperspell.com/blog/tos
  contact:
    name: Hyperspell
    url: https://hyperspell.com/
    email: hello@hyperspell.com
  version: 0.32.1
servers:
  - url: https://api.hyperspell.com
    description: Production
security:
  - APIKey: []
    AsUser: []
paths:
  /context-documents/tree/edits/{edit_id}:
    delete:
      tags:
        - Context Documents
      summary: Clear (soft-archive) a persisted edit
      description: |-
        Clear an edit — sets cleared_at and removes it from future overlays.

        For ADD edits with a corresponding user-prompt stored on
        ContextDocConfig.prompts[tier][key], also clear that prompt so the
        prompts UI doesn't dangle an entry for a file that no longer exists.

        Keeps the row around for audit. To restore, the user re-creates the
        edit via PATCH /files.
      operationId: clear_tree_edit_context_documents_tree_edits__edit_id__delete
      parameters:
        - name: edit_id
          in: path
          required: true
          schema:
            type: integer
            title: Edit Id
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                type: object
                additionalProperties:
                  type: string
                title: >-
                  Response Clear Tree Edit Context Documents Tree Edits  Edit
                  Id  Delete
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
        - APIKey: []
        - AsUser: []
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
  securitySchemes:
    APIKey:
      type: http
      description: >-
        API Key or JWT User Token. If using an API Key, set the X-As-User header
        to act as a specific user. A JWT User Token is always scoped to a
        specific user.
      scheme: bearer
      bearerFormat: Bearer <token>
    AsUser:
      type: apiKey
      description: >-
        Optionally set this header to act as a specific user when using an API
        Key, equivalent to first exchanging the API Key for a User Token
      in: header
      name: X-As-User

````