Immortal agents

The agent is the memory, not the process. Kill it, redeploy it, resurrect it anywhere.

error_outline

Without memory

An agent’s identity usually dies with its process: redeploy the service and the “assistant” that knew your infrastructure is a stranger again. Everything it learned was in a context window that no longer exists.

check_circle

With Rekall

A husk is a persistent agent identity — memory, expertise, preferences, run history — that any process can inhabit. Kill the container, upgrade the model, switch frameworks: resurrect the husk and the agent picks up mid-thought.

How it works

Create the husk once

The husk holds the agent’s durable self: identity, memory scopes, expertise profile, and execution history.

Processes come and go

Each run inhabits the husk, records thoughts and checkpoints against it, and exits. The husk persists.

Resurrect anywhere

A new process — different host, framework, or model — resumes the identity with everything intact, including half-finished runs.

See it in action

Death is an implementation detail

// Friday: the process dies mid-migration
// Monday: a NEW process, NEW host, newer model
const agent = await rekall.agents.resurrect('husk_dbops')

agent.memory   // → everything it ever learned
agent.runs     // → the migration, paused at step 4
await rekall.execution.resume(agent.runs[0].id)
// picks up mid-thought, three days later