Replays / Records

Capture a live you-agent-factory run as a replay artifact, find the saved recording after shutdown, or re-run from saved history without dispatching live workers again.

How To Use

A recording is a replay-compatible artifact that stores observed runtime history from a live factory run. Record mode starts a live run and writes that history to an artifact — either the default generated path or an explicit --record path. Replay mode reads an existing artifact with --replay and reuses the saved history instead of dispatching live workers again. Normal live you run invocations record by default when you pass neither --record nor --replay. Start from a normal live you run when you want a recording written by default. On shutdown, the CLI prints Recording saved: <path> so you can find the artifact after a failure or an unexpected stop. Use the run-controls table below to skip recording, write to an explicit path, or replay a saved artifact. Do not combine the incompatible flag pairs on the same invocation. Treat saved recordings as sensitive operator data: the product does not auto-delete old artifacts, so manage retention in your home directory or CI workspace, and do not commit real customer-run recordings. Record and replay stay separate from factory-session pause, resume, or status inspection.

Default recording root

~/.you-agent-factory/recordings/YYYY-MM/YYYY-MM-DD/

Shutdown signal

Recording saved: <path>

Flag	Effect
(none on a live run)	Record to the generated path under ~/.you-agent-factory/recordings/
--no-record	Skip the default recording for one invocation
--record <path>	Write the replay artifact to an explicit path you own
--replay <path>	Replay an existing artifact instead of starting a live run

Incompatible combinations (rejected for the same invocation)

--record with --replay
--no-record with --record

Record to an explicit path

you run --dir ./factory --record ./docs/examples/sample-run.replay.json

Replay a saved artifact

you run --dir ./factory --replay ./docs/examples/sample-run.replay.json

Limits And Assumptions

Replays / Records covers capturing live runs and replaying saved history. It is not a sync of packaged CLI docs, not factory-session pause, resume, or status, not mock-worker selection contracts, not a logs, metrics, or API reference, and not a full factory-authoring walkthrough. Replay artifacts are sensitive because they can contain prompts, payloads, stdout, stderr, and diagnostic metadata. The product does not delete old artifacts automatically — operators manage retention, and real customer-run recordings must not be committed. Sibling links and packaged you docs topics aid discovery only; they are not required to understand record and replay here.

Replays / Records

How To Use

Limits And Assumptions

Tags

On this page