Long tasks, recovery and integration
Remote confirmation links T7 to R42 and is recorded separately. An attempt is not a substitute for an outcome.
Links containing ?t= open the video at a specific second.
The ideas to retain
A long-running task is a durable state machine, not an infinite conversation
In a short interaction, we can pretend conversation, plan, workspace, and execution are one object. That simplification breaks down over hours.
“Memory” is not one object
Agent systems use memory to mean several different things:
Context, compaction, checkpoints, and durable state are not synonyms either
Compaction reduces or transforms the context fed back into the model. Its purpose is to keep reasoning within a token budget.
Jump directly to a section
Read the reviewed transcript
This video has no narration. This transcript reproduces its visible explanatory text, not an invented voice.
Record what actually happened
The first record expresses an intention. It does not yet prove that anything was sent.
The journal adds the actual attempt with a stable identity: operation T7.
Remote confirmation links T7 to R42 and is recorded separately. An attempt is not a substitute for an outcome.
A summary does not restore the environment
Compaction reduces the history visible to the model.
The workspace, revision and processes may have changed outside that summary.
Read the operational state again before continuing. Task memory and reality are different objects.
A lost response does not authorize a retry
Publication is sent, but its response is lost. The outcome is unknown.
Before retrying, look up the operation using its stable identity.
If it exists, reconcile the receipt. A blind retry could create a duplicate.
Parallel work still needs integration
Two independent pieces can be built at the same time.
In this example they take four and six minutes, followed by two minutes of integration.
The path takes eight minutes, not six. Gains depend on dependencies, coordination and final tests.
The target can move too
The candidate was verified against base A.
The target branch advances to B while the agent works.
Integration changes the combined state. Review the effective diff and rerun the affected checks.
Deliver with evidence
Delivery identifies the task, final revision and diff of the combined state.
Checks identify their scope and the revision they verified. They are not inherited from an old base.
Delivery includes limits and pending decisions. The reviewer knows what is verified and what is still missing.
