From 278cbccdb43a459e41549697b0ef8c1aee4fbe27 Mon Sep 17 00:00:00 2001 From: Andrei Hasna Date: Mon, 6 Jul 2026 23:58:58 +0300 Subject: [PATCH] docs: align README exec guidance with durable-by-default persistence codex-rs/README.md still framed `codewith exec --ephemeral` as the generic way to run without persisting session rollout files, nudging automation authors toward lifecycle bypass. Align the exec section with docs/exec.md: headless exec persists rollout files by default, --durable/--persist state that contract explicitly, and --ephemeral is only for intentional one-off runs that should not be materialized on disk. --- codex-rs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/codex-rs/README.md b/codex-rs/README.md index 17498fdd0e..5369f213d6 100644 --- a/codex-rs/README.md +++ b/codex-rs/README.md @@ -51,7 +51,7 @@ You can enable notifications by configuring a script that is run whenever the ag ### `codewith exec` to run Codewith programmatically/non-interactively To run Codewith non-interactively, run `codewith exec PROMPT` (you can also pass the prompt via `stdin`) and Codewith will work on your task until it decides that it is done and exits. If you provide both a prompt argument and piped stdin, Codewith appends stdin as a `` block after the prompt so patterns like `echo "my output" | codewith exec "Summarize this concisely"` work naturally. Output is printed to the terminal directly. You can set the `RUST_LOG` environment variable to see more about what's going on. -Use `codewith exec --ephemeral ...` to run without persisting session rollout files to disk. +Headless `codewith exec` runs persist session rollout files by default so long-running automation can resume or inspect the thread later. Use `--durable` or `--persist` when a workflow needs to state that contract explicitly, and use `codewith exec --ephemeral ...` only for intentional one-off runs that should not be materialized on disk. ### Experimenting with the Codewith Sandbox