Preserve agent cwd through Codex app server

README.md

@@ -204,14 +204,16 @@ prompt_delivery = "exec"        # {kickoff}=prompt file, {session}=session name,
 
 For an `"arg"` backend the flag *templates* are configurable (so you can point at a non-claude
 CLI): `resume_flag` (default `--resume '{id}'`), `model_flag` (default `--model '{model}'`),
-`remote_control_flag` (default `--remote-control '{session}'`), and `remote_addr_flag` (default
-`--remote '{addr}'`). A backend that sets `process_name`
+`remote_control_flag` (default `--remote-control '{session}'`), `remote_addr_flag` (default
+`--remote '{addr}'`), and `remote_cwd_flag` (default `-C {dir}` whenever `remote_addr` is set).
+A backend that sets `process_name`
 participates in backend-mismatch healing; one that doesn't (e.g. `demo`) never does.
 An optional `preamble` runs first and must succeed before the TUI starts; it supports `{bin}`,
 `{session}`, `{model}`, and `{dir}` templates. The Codex backend uses it to idempotently start the
 shared Remote Control daemon, then uses `remote_addr = "unix://"` to connect each tmux-hosted Codex
-TUI to that daemon. This keeps the app-server as the sole thread-store writer while local and
-Remote clients share the session.
+TUI to that daemon. The accompanying `-C` is required because the daemon's process directory is
+independent of the agent's. This keeps the app-server as the sole thread-store writer while local
+and Remote clients share the session in the configured project directory.
 For an unattended TUI with a deterministic first-run gate, `startup_prompt_re` opts into one
 screen check after `startup_prompt_delay` seconds; on a match, the harness types the explicitly
 configured `startup_prompt_response` and `submit_key`. Codex uses this to trust the agent's