Logs
Find you-agent-factory runtime logs under the selected log root, manage rolling retention, and use CLI --verbose / --debug diagnostics without confusing logs with metrics or record/replay.
How To Use
Start from the default log root when you need to inspect recent factory runs. Runtime logs are structured JSON rolling files grouped by UTC start date under that root (default ~/.you-agent-factory/logs). Use the retention and rotation controls below when you need a different root, retention window, backup count, size limit, or compression for rotated files. Pass a runtime-log flag on you run to set or inspect the log root for one invocation. CLI --verbose emits concise command diagnostics to stderr; --debug emits lower-level diagnostics where supported and implies --verbose; --json writes structured success output to stdout while diagnostics remain on stderr. Keep runtime logs separate from metrics files (a separate structured JSONL channel) and from record/replay artifacts when diagnosing a run.Default log root
~/.you-agent-factory/logs| Flag | Effect |
|---|---|
| --runtime-log-dir | Root directory for structured runtime log files grouped by UTC start date (default ~/.you-agent-factory/logs) |
| --runtime-log-max-age-days | Maximum days to retain rotated runtime log files (default 30) |
| --runtime-log-max-backups | Maximum rotated runtime log files to retain (default 20) |
| --runtime-log-max-size-mb | Rotate each runtime log file after this many megabytes (default 100) |
| --runtime-log-compress | Compress rotated runtime log files |
Set the runtime log root for one run
you run --dir ./factory --runtime-log-dir ~/.you-agent-factory/logs| Flag | Effect |
|---|---|
| --verbose | Emit concise command diagnostics to stderr |
| --debug | Emit lower-level command diagnostics where supported (implies --verbose) |
| --json | Emit structured JSON on stdout for supported commands; diagnostics remain on stderr |
Emit concise stderr diagnostics for one run
you run --dir ./factory --verboseChannel boundaries
- System logs include command stdout and stderr only on command failures.
- Environment details are record-channel diagnostics only, not the runtime-log channel.