Dream and continuous learning: nightly consolidation
A nightly memory consolidation is a personal automation built on top of a scheduled task, not a native Claude feature: it digests notes in four phases, orientation, collection, consolidation through merging and archiving, verification, and only a task that runs on the machine or in an open session can read a folder of notes stored locally.
A nightly memory consolidation is not a function that Claude offers on its own. It is an automation built by a user on top of an ordinary scheduled task, a script that rereads a folder of notes every night and corrects it. The way this task is scheduled decides whether the local notes folder falls within its reading scope.
Three forms of scheduled task, one single access to local disk
A scheduled task exists in three forms, and they are not equal on this precise point. A Cloud task runs without the computer needing to be on, but it works on a fresh copy of the repository, cloned for the occasion: it reaches no file and no database stored locally. A Desktop task, scheduled on the machine itself, does reach local files, provided the computer stays on at the moment it triggers. A loop launched in a session adds one more condition, a conversation left open, and it is lost as soon as a new conversation starts, unless resumed within seven days.
A folder of markdown notes installed on a machine belongs to the second category. Scheduling it in the Cloud because that form works with the computer off amounts to scheduling a read that the task will never be able to carry out: it will start, return a success, and will have read nothing at all.
Four phases to digest a night of notes
Once the right form is chosen, machine on, the pass breaks down into four steps. Orientation rereads recent exchanges and the memory index to place what has changed. Collection extracts the durable facts that deserve a note, leaving aside anything that remains a passing project state. Consolidation merges duplicates found and archives contradictions instead of deleting them. Verification rereads what has just been written and confirms, with a log line, that the pass has finished.
2026-09-02 03:00 orientation ok
2026-09-02 03:04 collection ok, 6 candidate notes
2026-09-02 03:11 consolidation ok, 2 merges, 1 archive
2026-09-02 03:12 verification okA missing line in this log one morning, rather than an error line, remains the most reliable signal of a silent failure: the task may not even have triggered that night. Before scheduling this pass, querying the knowledge graph rather than rereading everything follows the same logic, an index refreshed overnight serves the whole of the following day with no rebuild for every question asked.
Four phases of a nightly consolidation
Three forms of scheduled task, one single access to local disk
| Form of scheduled task | Access to local files | Computer must be on |
|---|---|---|
| Cloud, Routine | No, fresh copy of the repository cloned for the occasion | No |
| Desktop, local task | Yes | Yes, at the moment it triggers |
| In-session loop | Yes | Yes, and the session must stay open |
A cooperative creates a scheduled task in the Cloud to run a script every night that must merge the notes accumulated in the memory folder installed on the office computer. The next morning, the scheduled tasks dashboard shows a success, with a run time of four seconds.
Write in one sentence what this situation establishes, and in one sentence what it does not establish.
What this establishes: The scheduled task ran and returned a success code within a few seconds.
What this does not establish: It does not establish that the script actually read or merged the notes in the local memory folder, since a Cloud task works on a fresh copy of the repository and does not reach files stored on the office computer.
The three most common miscalibrations
- Trop large The cooperative's memory system is now fully automated and no longer needs any human intervention.
- Trop étroit This result only allows the task's existence in the interface to be affirmed, not even that it triggered that night.
- À côté This result shows that the run time of Cloud scheduled tasks generally stays very short, around a few seconds.
- A Cloud scheduled task runs without the computer needing to be on, but it works on a fresh copy of the repository and reads no file stored locally.
- A consolidation that needs to read a local notes folder depends on a Desktop task or an in-session loop, so on a machine that stays on at the moment it triggers.
- The consolidation phase merges duplicates and archives contradictions, it never deletes an existing note.
- A log missing a line one morning signals a silent failure more reliably than a displayed error line.
- This nightly consolidation mechanism is an automation built by a user, not a function that Claude offers on its own.
Open your scheduled tasks settings, identify which form the one that must read a local notes folder currently runs under, and move it to a Desktop task or an in-session loop if it is currently scheduled in the Cloud.
These points depend on an interface or a rule that may have changed since this was written. Check them on your own screen before relying on them.
- Check in your own scheduled tasks settings whether the one you create runs in the Cloud or on your machine: it is this choice, not the content of the script, that decides whether your local files get read.
Every datable claim in this lesson links here to the public text behind it. A source that does not open proves nothing.
- Anthropic, scheduled tasks in Claude Code consultée le 2026-09-02