Start the configured Codex worker during Foundry deployment

2026-11-05 11:36:46 +08:00
parent 9e5d805f5a
commit d80854deae
2 changed files with 16 additions and 4 deletions
@@ -51,10 +51,11 @@ On the deployment host, provision `/opt/endoleap-infra/foundry/codex` with:
  Keep this home dedicated to the worker. Supply the login only and keep user
  configuration, MCP servers, skills, and other workload files out of it.

-Start the single worker with `bash deploy/codex-worker.sh /absolute/path/to/foundry`
-using the Linux binary built by ces-control. To replace the worker, stop and remove
-the existing `foundry-codex-worker` container first. The next normal Foundry
-deployment mounts the worker socket and grants directory read-only. The worker
+With that directory configured, the next normal Foundry deployment starts the
+worker using the Linux binary built by ces-control and mounts the worker socket
+and grants directory read-only. To replace an existing worker, stop and remove
+its container, then run `bash deploy/codex-worker.sh /absolute/path/to/foundry`
+with the desired ces-control build. The worker
 runs the installed Codex CLI with fixed read-only, no-approval arguments and
 disables command execution tools. It receives prompts via stdin and returns
 the final agent message. The worker has no published port and Foundry receives