Skip to content

Latest commit

 

History

History
68 lines (50 loc) · 1.24 KB

File metadata and controls

68 lines (50 loc) · 1.24 KB

Codex App-Server

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 ....

Managed Listener

hermes sprints codex-app-server up
hermes sprints codex-app-server status
hermes sprints codex-app-server doctor

Default endpoint:

ws://127.0.0.1:4500

Logs:

hermes sprints codex-app-server logs --lines 100

Stop:

hermes sprints codex-app-server down

Workflow Config

runtimes:
  codex:
    kind: codex-app-server
    mode: external
    endpoint: ws://127.0.0.1:4500
    ephemeral: false
    keep_alive: true

mode: external means Sprints connects to an existing listener. keep_alive: true keeps the WebSocket connection open for reuse.

Auth

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.token

Then 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