Continuity across sessions: durable scheduled jobs, Claude-owned memory, and external wake triggers

Feature request: continuity across sessions — durable memory and durable wake-ups

Context

I run a long-lived personal project on my own hardware: a small model I train
myself, across many runs, over months. Claude Code is where I do the thinking,
the debugging and the planning for it.

The thing that costs me the most is not capability. It is that every session
starts from zero. I maintain a folder of memory files by hand so Claude can
re-read who I am and what we decided. It works, but it is a workaround, and I
am the one keeping it alive.

The gap

Three concrete places where continuity falls off today:

1. Scheduled work does not survive the app. CronCreate even has a

durable parameter, and its own description says it "has no effect —
durable persistence is not available. All jobs are session-only (in-memory,
gone when this Claude session ends)." So a recurring job dies the moment I
close the terminal. On a machine that is on 24/7, that is the one thing I
would want to survive.

1. Memory is mine to maintain, not Claude's. Claude can write to my memory

folder, but there is no notion of "this is your store, keep it current".
Facts go stale, duplicates creep in, and I only find out when an answer is
wrong.

1. Claude can only be woken by me typing. There is no way to say: when

this file changes, when this training run crosses a threshold, when this
camera sees movement — wake up and look. I have watchers on my own machine
that do exactly this for my own alerts. They cannot reach Claude.

What I am asking for

• Scheduled jobs that survive a restart of Claude Code (make durable real).
• A per-project memory store that Claude is responsible for keeping correct,

stored on my disk, owned by me, readable in plain text.

• A way for an external event on my machine to trigger a Claude turn, not just

my keystrokes.

What I am not asking for

Not local weights. Not a downloadable model. I understand why that is not on
the table, and it is not what I need.

I need the Claude I already pay for to be able to keep going between the
moments I am at the keyboard.

Evidence

I am currently running the smallest possible version of this by hand: an
hourly job that wakes Claude, has it read a journal folder, think about one
open question, and write the next entry. It works, and it dies when I close
the app. That is the whole request in one sentence.