codex-web-console

Minimal local-first web console for Codex.

Current Scope

• Local-only: talks to a single local codex app-server
• Single-token auth: one login field, one access token
• Thread list across all local providers
• URL-addressable threads: / opens a new thread, /?thread=<id> opens an existing one
• Live timeline updates over SSE
• Workspace browser for choosing a local directory
• Approval handling for command, file-change, and permissions prompts
• Turn controls: stop the current turn, jump to previous/next historical turn

This project is intentionally narrow. It does not implement users, remotes, or a second session system on top of Codex threads.

Development

bun install
bun run dev

Auth

Set a single access token before starting, or copy .env.example into your own env setup:

export CODEX_WEB_CONSOLE_TOKEN=your-token

The landing page accepts exactly one token and stores a signed-in cookie locally.

In development, if the variable is missing, a fallback token is enabled:

codex-web-console

Build

bun run build

Requirements

• Codex must be available in PATH
• The UI starts and talks to a single local codex app-server
• The configured token is required outside development

Notes

• Threads are listed via the app-server with modelProviders: [], so the sidebar includes threads across providers.
• Some reasoning content is available live but not fully restored by thread/read; the UI preserves it during the current browser session for continuity.
• The current version focuses on the single-machine path and keeps the architecture thin on purpose.