Use this when actors run through kind: codex-app-server.
This service is only the Codex runtime listener. The workflow tick loop is
managed by hermes sprints daemon ....
hermes sprints codex-app-server up
hermes sprints codex-app-server status
hermes sprints codex-app-server doctorDefault endpoint:
ws://127.0.0.1:4500
Logs:
hermes sprints codex-app-server logs --lines 100Stop:
hermes sprints codex-app-server downruntimes:
codex:
kind: codex-app-server
mode: external
endpoint: ws://127.0.0.1:4500
ephemeral: false
keep_alive: truemode: external means Sprints connects to an existing listener. keep_alive: true keeps the WebSocket connection open for reuse.
Loopback listeners usually do not need WebSocket auth. Non-loopback listeners should use a token:
hermes sprints codex-app-server up \
--ws-token-file /absolute/path/to/codex-app-server.tokenThen reference the token in the runtime profile:
runtimes:
codex:
kind: codex-app-server
mode: external
endpoint: ws://127.0.0.1:4500
ws_token_file: /absolute/path/to/codex-app-server.token