Concept / Continuity

Sessions end. Runs continue.

A coding-agent session is the conversation you can close. A Yield run is the workflow record that remains in your project.

01 / Difference

Two lifetimes. One workflow.

Coding-agent session

The interface around the work.

Owns the conversation and question UI.
May end when you close or restart the agent.
Can be Cursor, Codex, Claude Code, or another registered host.

Yield run

The durable execution record.

Owns ordered operations, accepted responses, checks, and the outcome.
Stays under the canonical skill workflow.
Can be inspected and continued by a new agent session.

Session is not a Yield object.Yield does not preserve the old conversation. It preserves enough workflow state that the old conversation is not required.

02 / Handoff

One run can cross agent sessions.

Session ACoding agent

› /release

Build passed
Review returned
Approval requested

Session closes

Yield run

run_01J…

01run.started
02operation.completed
03operation.requested

skills/release/.yield/runs/

Session BAny registered agent

› inspect run_01J…

Saved steps replayed
Approval still pending
Continue from step 03

Same run continues

Generated adapters discover the canonical workflow. The run-id identifies the durable execution.

03 / Continue

Inspect first. Then answer the pending operation.

Continue a saved run · TypeScript

npm exec -- yskill inspect --skill skills/release
npm exec -- yskill inspect <run-id> --skill skills/release
npm exec -- yskill respond <run-id> --value yes --skill skills/release
npm exec -- yskill replay <run-id> --skill skills/release

inspect without a run ID lists saved runs. With an ID, it prints the append-only event log. respond validates one answer against the current pending operation and advances the run.

04 / Resume

Resume means deterministic re-execution.

01
Start from the top.
The workflow program starts as a new process. Yield does not keep a daemon or suspended function alive.
02
Replay saved operations.
Recorded responses are returned in order only while each operation digest still matches.
03
Stop at the first unanswered step.
The workflow emits the pending operation and exits again.
04
Record one validated response.
The next start replays that response and continues to the next step or terminal outcome.

05 / Boundaries

What survives—and what does not.

Survives: Accepted responses, command results, passed requirements, pending operation, and terminal outcome.
Does not survive: The coding agent’s full conversation or unrecorded actions outside the workflow.
Source changes: Yield refuses resume when the workflow digest changes. Intentional migration requires explicit review.
Other machines: Runs are local project data. Yield does not automatically sync .yield/runs between computers.