Skip to main content

​
Setup

Install the Codex CLI and sign in on the machine running Flowfield. Flowfield uses the installed codex app-server directly. In Settings → Harnesses, keep detected paths or override the executable and configuration directory. Accounts stay in Codex. See shared setup.

​
Models and access

Models, reasoning effort, access modes and Fast availability come from Codex. Tool approval requests offer one-time allow/deny choices; choose the saved access mode for broader policy changes. Persistent permission grants are not exposed. Choose Coordinator and workspace worker defaults independently; task Agent settings can override the next attempt. See worker setup. Workspace member repositories are added to the Coordinator’s writable roots in Agent mode. The managed working directory stays separate. Read only and Full access retain their native permissions; task workers keep their isolated checkout scope.

​
Commands

The Coordinator supports /compact, /status, /mcp and /skills. Compaction uses the native thread control. Status shows the current choice; MCP and skills use native inventories.

​
Sessions and Stop

Compatible model and access choices resume the native Coordinator session. Stop interrupts active turns and checks supported native background work. See Coordinator recovery for saved history, fresh sessions and uncertain cleanup.

​
Native customization

Codex loads its native repository instructions and skills. Flowfield supplies the workspace- or task-scoped MCP connection for each managed session.

​
Standalone conversation

Use the shared connection steps with codex: