Skip to main content
Flowfield keeps planning and execution connected. You discuss the work in a Coordinator conversation, capture agreed outcomes as tasks, and use their results to decide what happens next.

People and agents

You set the direction and decide which code to deliver. The Coordinator helps investigate ideas, maintain shared context and organize tasks. Workers carry out those tasks, and a Reviewer assesses their results against the requirements. The Coordinator can keep planning while Workers run. Flowfield’s service manages the queue, retains the evidence and delivers approved results. Choose Codex, Claude Code or Pi for each role. You can use the same harness throughout or combine them; Agent setup explains the choices.

Workspaces, projects and tasks

A workspace is the home for work you want to plan together. It has one Coordinator conversation, shared documents, a Task Board and an Inbox. Add your existing repositories as projects within it. A task defines an outcome and the criteria for completing it. A code task belongs to a project. Reports and files can belong directly to the workspace. A task keeps its instructions, questions, activity and results together across attempts. Use dependencies when a task needs another task’s delivered result. Use local subtasks when several contributions belong to one outcome and will be reviewed together. Planning effective tasks helps choose a useful scope.

Shared context

Documents hold reusable goals, conventions and specifications. Select the documents a task needs as required sources or reference material. When shared guidance changes, Flowfield checks its effect on unfinished work at execution and review handoffs. The task keeps the sources used for each attempt, so you can understand the requirements behind a result.

The board and queue

Capture ideas in Backlog, then move the work you want executed to Up next. The queue starts eligible tasks in priority order as capacity becomes available. Tasks move through In progress, In review and Done. Automatic work and agent review happen in In progress; In review means a human decision or approved delivery is pending. Open a task to see its current status and next action. Inbox brings together questions and decisions that need you. Its Delivered view collects completed outcomes. You can follow the work from the board without reading every agent turn.

Results and approval

A result contains the proposed outcome, submitted files and verification evidence. The Reviewer checks it against the task and may request corrections. For code, you inspect the result and approve the exact candidate to deliver to your local repository. A changed candidate needs a new decision. Complete reports and files finish after review and remain available in Files. Delivery updates the local branch. Ask the Coordinator when you want to run, push or publish the result. Results, review and delivery explains that workflow.

Agent settings and permissions

Workspace defaults choose the agents and queue capacity. Project settings define setup, checks and the delivery branch. Task settings can override the Worker and Reviewer for subsequent attempts. Native access modes control agent actions on the host; code approval controls delivery of a result. Configuration and permissions is the reference for these settings.