LoomCycle Memory Backend icon

LoomCycle Memory Backend

Manage versioned loomcycle memory-backend definitions

LoomCycle Memory Backend

AI-generated

Summary

Manage named, versioned LoomCycle memory backend definitions by creating or forking a definition, retrieving the active version, listing its version lineage, or retiring a version. Calls the LoomCycle API using the required LoomCycle API credential.

Inputs

  • Operation (required) — Choose Create, Fork, Get, List Versions, or Retire.
  • Name (required) — Definition name used by agents and memory_backend overlays. Shown for Create, Get, List Versions, and Retire.
  • Parent Def ID (required) — Fork only: ID of the definition row to branch from. Fields absent from the overlay are inherited from this parent.
  • Description — Create or Fork: operator-visible description for the new version.
  • Overlay (JSON) — Create or Fork: JSON backend definition or, for a fork, the diff merged onto the parent. Can include settings such as kind, endpoint, auth references, and ranker configuration. The node parses this as JSON before sending it to LoomCycle.
  • Promote to Active — Create or Fork: whether to automatically make the new version active; defaults to true.
  • Def ID (Optional) — Retire only: specific version ID to retire. Leave empty to retire the active version for the supplied name.

Output shape

A single item containing a result field with the LoomCycle API response.

Create and Fork register new versions; Get returns the active row for the name, List Versions returns its versions, and Retire marks the selected row as retired. API errors are surfaced as node errors unless Continue On Fail is enabled.

Links

Discussion