stigmem-node

Persist OpenClaw agent context across sessions via a Stigmem node.

4|1|Updated May 2, 2026
One-click install
npx skills add https://github.com/eidetic-labs/stigmem --skill stigmem-node
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stigmem-node
Source: https://github.com/eidetic-labs/stigmem/tree/main/adapters/openclaw/skill
Command: npx skills add https://github.com/eidetic-labs/stigmem --skill stigmem-node

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stigmem node-backed persistence provides OpenClaw agents with a durable memory layer that preserves context, handoffs, and decisions across sessions, improving continuity and auditability.

Core Features & Use Cases

  • Boot handshake: synchronize user preferences and pending handoffs at session start.
  • Handoff, decision, and escalation surfaces: record durable context for seamless resumption and governance.
  • Provenance and audit: attach timestamps, sources, and governance constraints to recallable facts.

Quick Start

Boot your agent to retrieve boot context from your Stigmem node and begin a session with persistent, connected memory.

Frequently Asked Questions about stigmem-node

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retain context for OpenClaw agents across sessions?

To retain context for OpenClaw agents across sessions, you can use a persistent memory layer that synchronizes boot handshakes, handoffs, and decisions, ensuring continuity and auditability throughout your workflows.

What is federated memory for agent handoffs and escalations?

Federated memory for agent handoffs and escalations is a durable context layer that records timestamps, sources, and governance constraints, allowing seamless resumption and provenance tracking across distributed agent nodes.

How do I set up persistent agent memory using a Stigmem node?

To set up persistent agent memory, configure your environment with a Stigmem node URL via STIGMEM_URL and a least-privilege API key via STIGMEM_API_KEY, then boot your agent to retrieve boot context and begin a connected session.

Can I track provenance and audit decisions for OpenClaw agents?

Yes, you can track provenance and audit decisions by attaching timestamps, sources, and governance constraints to recallable facts, providing a durable record for escalation and decision workflows.

Do I need specific environment variables to enable agent boot handshakes?

Yes, enabling agent boot handshakes requires setting STIGMEM_URL and STIGMEM_API_KEY, while optional variables like STIGMEM_SOURCE_ENTITY and STIGMEM_OPENCLAW_ALLOWED_HANDOFF_TARGETS configure source identity and handoff targets.

What are the limitations of using a persistent memory layer for agent continuity?

Limitations of using a persistent memory layer include the dependency on external node availability via STIGMEM_URL and the strict requirement for a least-privilege API key to govern access during boot and handoff workflows.