A practical Codex pattern separates two kinds of continuity:
- pulse threads run on a cadence and check a bounded area;
- a log thread records the ongoing activity that future work needs to understand.
The official scheduled-tasks model supports both independent recurring runs and tasks that return to an existing chat with its context. Skills can package the repeatable action, while the schedule controls when it runs.
Why the split matters
A pulse is a sensor. It should answer a narrow question such as:
- what changed in the monitored sources?
- which release broke an assumption?
- which draft is approaching its deadline?
- which deployment or metric needs attention?
A log is not another sensor. It is the durable explanation of decisions, corrections, and unresolved work.
If every recurring run writes an unstructured essay into one endless chat, the system eventually creates the context noise it was meant to solve. The stable record should live outside the conversation in structured state or versioned files.
New Runtime Read
The newsroom can use three morning pulses:
- source freshness and 24-hour editorial deadlines;
- system health, failed ingestion, and publication receipts;
- trend deltas that gained or lost evidence.
Each pulse should report only changes and exceptions. The project log and operational database should retain the durable state. A scheduled chat may carry continuity, but it must not become the sole database.
The power-user pattern is valuable because it turns the agent from an on-demand answer box into a maintained operating rhythm. Its production version needs idempotency, stop conditions, and an explicit place where memory survives the thread.