Dreaming

Dreaming in CoWork OS is the periodic AI pass over the memory folder: it reads the folder and recent task conversations, applies safe edits as one undoable commit and puts the rest on a branch you accept or reject as a diff in the Memory Hub Review tab. The design, triggers, budget and settings are in Memory Repo Phase 2.

What it replaced

Earlier versions had a heuristic curator, also called Dreaming, that merged, promoted, decayed and expired rows of memory_items and queued proposals for review. Phase 3 (design §6) retired it, because global and workspace facts now live in the memory folder:

• the curator (DreamingService, MemoryCurator, the optional LLM synthesis step), its proposal queue and the "Run Dreaming now" button are gone;
• the settings dreamingLlmEnabled and dreamingLlmDailyTokenBudget and the Dreaming health checks are gone (the "Memory folder dreaming" health row stays);
• task completion and Box Brain imports no longer start a curation run;
• the dreaming_runs and dreaming_candidates tables stay for history and are pruned by retention; open proposals were closed as dismissed.

Commitment expiry

Commitments (open loops with due dates) still live in memory_items. The Heartbeat pulse runs a commitment sweep once a day (CommitmentExpiryService): a commitment at least a day past due is closed when later activity (task outcomes or the conversation index) says it was done. Commitments you made yourself are never closed automatically, and nothing is queued for review. Each expiry is logged and can be undone under Closed commitments in the Review tab; an undone expiry is never applied again. See memory-engine.md §5b.