Skip to main content
Flowfield has host, workspace, project and task settings. Use the narrowest level that matches what you want to change. Change saved application settings in the GUI or ask the Coordinator through MCP. Appearance and browser permissions stay in the browser.

Where settings live

The Coordinator’s input controls and Workspace settings → Coordinator edit the same saved agent choice. A task inherits workspace Worker and Reviewer choices until you override them; Reset restores inheritance.

Agent choices

Choose a harness and model for each role. Available models, effort, access modes and Fast settings come from the selected harness. Changes apply to subsequent turns or attempts. Fast offers quicker responses with increased usage on supported models. See Agent setup for the controls available in Codex, Claude Code and Pi. Use Settings → Harnesses to override an executable or configuration directory, then choose Verify installation. Native accounts and provider settings remain with the harness.

Queue and capacity

The Coordinator runs independently of worker slots. Tasks and execution explains eligibility and ordering.

Project execution

In Project settings, Delivery selects the local branch; Setup and Validation hold their commands and time limits; Execution supplies defaults for new results, or a reason for No runnable result. Each result retains its own verified recipe. Project setup and checks walks through preparing and validating them. Setup and validation commands run on the machine hosting Flowfield. Workers use separate repository checkouts. Give concurrent tasks separate ports, databases and other mutable resources when their commands need them.

Permissions and approval

Choose a native access mode appropriate to the work. Answer tool permission requests in the conversation or Inbox while the agent is waiting.

Saved project checks

Saving validation commands makes them available to Workers through Flowfield. The service executes the attempt’s frozen commands against its working copy, with time limits, retained logs and process cleanup. This uses service-host access; native shell tools retain their own permission controls. Editing defaults affects new attempts, and final candidate validation remains independent.

Code delivery

Code approval applies to a specific result. Changes to the candidate require fresh approval. Running a result, pushing commits and publishing are separate actions you can request from the Coordinator. See Results, review and delivery.

Document defaults

Use Documents → Edit → Use this document to choose the projects and tasks that inherit shared guidance. Project settings expose the same worker-document defaults. Task-specific selections are managed with the Coordinator. Workspace documents explains required sources, references and how changes reach unfinished work.