Skip to main content
The Coordinator belongs to your workspace and stays with you across its projects. Work through an idea, challenge assumptions and refine the plan as implementation reveals new requirements. You can edit work directly or ask it to maintain documents, milestones, labels and tasks.

​
Start a conversation

Create a workspace, then choose a ready harness, model and supported effort/access controls beside the input. Save and send your message. Enter sends; Shift+Enter or Command/Ctrl+Enter adds a new line. Worker defaults are configured separately. The Coordinator uses a Flowfield-managed working directory and the service host’s tools and credentials. Its Flowfield tools are scoped to the workspace; repository actions identify a member project. Its native access mode still governs filesystem and tool actions. It can help configure project integration before workers start. Direct setup changes you request affect the project or host immediately; they do not become worker results for approval. Route agreed implementation through tasks.

​
Use the work beside the chat

Open a task, document or filtered board beside the same conversation. Each message captures that view when sent: a task’s project and revision, an exact result, a document revision, or the selected project/milestone/label filters. Later navigation does not reinterpret an earlier message. If the intended project is ambiguous, the Coordinator asks. Ask it to sort Inbox, explain blockers, update guidance, adjust priorities, request another pass or help review a result. You can explicitly approve a specific code result here; Flowfield records that exact approval and delivers it without another browser confirmation. Task and Inbox actions follow the same records and approval rules.

​
Attach context

Use the paperclip, drag files onto the input or paste an image. Remove unsent attachments with ×. Sent files remain with the message and can be downloaded. A message accepts up to four UTF-8 text/code files of 64 KiB each or PNG, JPEG and WebP images of 2 MiB each. Image input requires support from the selected harness. Workspace conversation and each project’s task feeds have separate 128 MiB attachment limits; unsent uploads expire after 24 hours. Attachments accompany the message and its native session. Reattach important files after a fresh session or when compaction has omitted their details. Task answers and feedback accompany separate worker attempts; attach files again when later input needs them. Use documents for durable shared context.

​
Controls and commands

Model, effort, access and supported Fast choices apply to subsequent messages; a running turn keeps its captured settings. Fast provides quicker responses with increased usage where the selected model supports it. Changing the model starts at normal speed. The context ring shows the latest reported occupancy, separately from billable token usage. Type /, choose Load commands, select a command and send. Commands take no arguments or attachments: Inventory commands send no model prompt. See the agent pages for native differences. Permission requests appear in the conversation and Inbox; answer while the turn is waiting. Tool permission is separate from approval to deliver worker code.

​
Stop and continue later

One Coordinator turn runs per workspace, independently of worker slots. Replies and tool activity stream as it works; you can draft your next message while it runs. Stop ends that turn, preserving saved work changes. Task workers continue independently. The service saves your messages, public output and turn settings. Older messages load on demand; Read full reply and Retained output expose shortened replies and tool details. A compatible session resumes native context across messages and service restarts. Switching harness, adding a project or changing a member repository path starts a fresh native session on the next message. Other settings changes follow the harness’s continuation rules. Saved Flowfield conversation stays available; fresh sessions receive recent exchanges and can retrieve older history. Native tool history stays with its original session. If a session cannot resume, follow its recovery message or choose Start new session. Interrupted prompts are never replayed automatically. When cleanup is uncertain, inspect and stop remaining native work on the host before Confirm coordinator stopped. Reattach earlier files when a new session needs their contents. Resize Coordinator and Work on wide screens. Switching between their phone views preserves the current draft.