Windows CI / windows ([bun run --cwd packages/app-core test bun run --cwd packages/elizaos test bun run --cwd packages/cloud/shared test], app-and-cli) (push) Waiting to run
Windows CI / windows ([bun run --cwd packages/scenario-runner test bun run --cwd packages/vault test bun run --cwd packages/security test bun run --cwd plugins/plugin-coding-tools test], framework-packages) (push) Waiting to run
Windows CI / windows ([bun run --cwd plugins/plugin-elizacloud test bun run --cwd plugins/plugin-discord test bun run --cwd plugins/plugin-anthropic test bun run --cwd plugins/plugin-openai test bun run --cwd plugins/plugin-app-control test bun run --cwd plugins/pl… (push) Waiting to run
Windows CI / windows ([node packages/scripts/run-turbo.mjs run build --filter=@elizaos/core --filter=@elizaos/shared --filter=@elizaos/agent --concurrency=4 node packages/scripts/run-bash-linux-only.mjs scripts/verify-riscv64-buildpaths.sh node packages/scripts/run… (push) Waiting to run
Windows CI / windows ([node packages/scripts/run-turbo.mjs run typecheck --filter=@elizaos/core --filter=@elizaos/shared --filter=@elizaos/cloud-shared --concurrency=4 bun run --cwd packages/core test bun run --cwd packages/shared test], core-runtime, 75) (push) Waiting to run
Harness bridge that lets the benchmark orchestrator run benchmarks against the
Codex CLI agent, authenticated per OpenAI-Codex account. Skeleton adapter,
API-shaped like smithers-adapter / hermes-adapter / openclaw-adapter:
select it with --adapters codex and iterate accounts with
--accounts <n|list>.
Each turn spawns a one-shot codex exec subprocess (non-interactive) that reads
the prompt on stdin and prints the assistant output on stdout. The subprocess is
authenticated as a selected account by pointing CODEX_HOME at that
account's materialized home. Not registered as a standalone benchmark — it wraps
other benchmarks run against the Codex harness.
Multi-account CODEX_HOME
The elizaOS runtime materializes one CODEX_HOME per authenticated account so a
spawned Codex process authenticates as that account instead of the machine's
single ~/.codex login. The layout (written by
packages/app-core/src/services/coding-account-bridge.ts):
<stateDir>/auth/_codex-home/<accountId>/
auth.json # chatgpt-mode tokens
config.toml # pinned model (gpt-5.5)
where <stateDir> is $ELIZA_HOME (or the resolved per-user state dir,
default ~/.local/state/eliza). This adapter's codex_adapter.accounts
enumerates those homes and round-robins turns across the selected set — it does
no OAuth and no network; materializing the homes is the TS runtime's job.
--accounts semantics
integer N → the first N discovered accounts (sorted by id);
comma list a,b → exactly those account ids, in order;
omitted → all discovered accounts.
Turns round-robin: turn i uses accounts[i % len(accounts)].
Run (live — credential-gated)
See ../docs/HITL_MULTI_CODEX_RUNBOOK.md.
A live run requires real authenticated Codex homes and the gpt-5.5 model those
accounts are entitled to:
Tests are fully offline — account discovery, --accounts parsing, round-robin
rotation, and client failure modes, with no API keys or real Codex install.