feat: run Codex on remote OpenWork workers

[me-kirill]

Summary

• add an experimental per-workspace Codex Server runtime for remote OpenWork workers
• run Codex app-server over private stdio with workspace-scoped CODEX_HOME and ChatGPT device-code authentication
• adapt Codex threads, turns, streamed items, models, approvals, and files to the OpenCode surfaces already consumed by OpenWork
• add remote-worker runtime diagnostics and an end-to-end fraimz flow

Validation

Passed:

• pnpm --filter openwork-server typecheck
• pnpm --filter @openwork/app typecheck
• pnpm evals:typecheck
• pnpm --filter openwork-server exec bun test src/codex-runtime.e2e.test.ts
• pnpm --filter @openwork/app test
• pnpm --filter @openwork/app build
• real codex-cli 0.145.0 smoke: initialize, account/read, model/list, thread/start, thread/delete
• pnpm fraimz --flow codex-server-runtime --cdp-url http://127.0.0.1:36449 — Passed, 8/8 narrated frames

Full server suite result: 544 passed, 10 skipped, 2 unrelated baseline failures:

• legacy-config-sweep.test.ts expects chmod 0444 to be unwritable, which is false when tests run as root
• openwork-capabilities-knowledge.test.ts expects the old Settings > Connect copy while bundled docs now say Settings > OpenWork Connect

Proof

A final fraimz run passed all claims. I will attach the generated proof in a PR comment.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
openwork-landing	Ready	Preview, Comment, Open in v0	Jul 26, 2026 9:32pm

[vercel]

@me-kirill is attempting to deploy a commit to the Different AI Team on Vercel.

A member of the Team first needs to authorize it.