About dream
dream is a retired AgentOps skill retained as a pointer; it no longer runs an in-repository command. Out-of-session knowledge compounding has moved to an adopted substrate, while several on-demand knowledge and daytime code-compounding primitives remain in AgentOps.
Key features
- 01Retired skill retained as a pointer
- 02Former out-of-session cycle moved externally
- 03On-demand knowledge primitives remain
- 04Daytime code compounding via /evolve
- 05Nightly proof job uses retained primitives
Use cases
- 01Locate the replacement lane for scheduled knowledge compounding
- 02Use retained on-demand knowledge primitives
- 03Distinguish /evolve from out-of-session compounding
MCP support
The README says scheduled out-of-session knowledge compounding now runs on an adopted substrate using NTM + MCP + managed-agents; AgentOps does not own that substrate.
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/dreamin Claude Code to confirm it loaded.
Bundled filesreferences/dream.featurescripts/validate.sh
Details
From the project READMEDream - Retired (out-of-session compounding moved to the substrate)
Status: RETIRED (soc-2rtm0). The in-tree out-of-session compounding engine and its whole CLI surface (the former always-on lane) were removed, along with the always-on background process that carried it. AgentOps no longer ships an out-of-session orchestration substrate — scheduled, between-session knowledge compounding now runs on a substrate AgentOps adopts but does not own (NTM + MCP + managed-agents). This skill remains only as a pointer; it no longer drives an in-repo command.
Cross-vendor analog: Anthropic Managed Agents Dreaming (research preview, May 2026) — scheduled session review, pattern extraction, memory curation between runs. AgentOps now delegates that lane to a managed-agents substrate rather than owning it.
What moved
The "dream cycle" (bounded INGEST -> REDUCE -> MEASURE knowledge compounding
between sessions) is no longer an ao command. Drive it through the substrate's
out-of-session scheduling surfaces instead (an NTM cron dispatch or a
managed-agents schedule). Do not invent a replacement ao workflow.
What stays in AgentOps
The KEEP primitives the dream cycle was built on are unchanged and remain on-demand:
/harvest— promote.agents/knowledge across rigs/forge— mine transcripts into learnings/compile— Mine → Grow → Defrag → Lint the wiki corpus/inject— JIT decay-ranked context assembly/evolve— daytime, operator-driven code compounding via/rpi
The nightly-CI dream-cycle proof job in .github/workflows/nightly.yml
(harvest -> forge -> close-loop -> defrag -> metrics health) still runs against
the checked-in corpus; it is built on those KEEP primitives, not on the retired
CLI engine.
Delineation vs /evolve
/evolve owns the daytime code-compounding layer (operator-driven, via /rpi).
The knowledge-compounding layer that /dream used to own now lives outside
AgentOps, on the adopted substrate (NTM + MCP + managed-agents). Both still
share the fitness-measurement substrate via corpus.Compute / ao goals measure.
Reference Documents
- references/dream.feature — Historical executable spec for the retired bounded bedtime loop (harvest→forge→close-loop→defrag), kept for provenance (soc-qk4b)
- How It Works
- CLI Reference
See Also
/harvest,/forge,/compile,/inject- the KEEP knowledge primitives/evolve- daytime code-compounding loop/handoff- capture explicit session closeout