sequenceDiagram
participant A as Agent A
participant OB1 as OB1 Agent Memory
participant B as Agent B
A->>OB1: Recall prior attempts, blockers, and constraints
A->>A: Complete one TaskFlow step
A->>OB1: Write compact work log
B->>OB1: Recall the work log
B->>B: Continue without raw transcript
This workflow makes OpenClaw TaskFlows durable across agents and model choices. The handoff lives in OB1 as compact operational memory, not in one model's context window.
Built by Nate B. Jones / OB1. Follow Nate for practical AI systems, agent workflows, and implementation notes: Substack and natebjones.com.
-
Complete NBJ OB1 Agent Memory for OpenClaw.
-
Install the live OpenClaw skill for TaskFlow workers:
openclaw skills install nbj-ob1-agent-memory-openclaw
-
Require recall at TaskFlow start and step resume.
-
Require write-back at step completion, pause, or failure.
-
Review high-impact constraints before they become instruction-grade.
-
Use Safe Agent Memory and Provenance for review and scope decisions.
Recall these memory types:
- prior task attempts
- blocking issues
- relevant decisions
- current project constraints
- owner and channel context
- unresolved questions
Write back:
- what was attempted
- what changed
- what failed
- what remains open
- what should be reviewed
- what the next agent should know
The memory should let a second agent continue in minutes without reading the raw transcript.
- A second agent can continue from the work log without duplicated attempts.
- Failures are retrievable, but they do not become permanent rules.
- Confirmed project constraints outrank inferred step notes.
- Recall traces show which memories informed the resumed TaskFlow.