Skip to main content
A task produces one outcome: code, files, a report, or a combination. Direct work and assembled subtasks use the same result and review flow. Open a result from Inbox, Delivered, the recent sidebar or its task feed. Each result preserves its own report, evidence and submitted files. An exact code result with its launcher, report and approval controls

​
Independent task review

In Workspace settings → Reviewers, choose the native harness and model for Task reviewer. Assessment defaults on, but no model is selected automatically. A task’s Settings can override the workspace choice or reset to inheritance. Subtasks use their parent task’s worker settings and have no separate reviewer. Complete code and file outcomes receive an independent assessment against their exact assignment, sources, destination and saved validation. Reviews share worker capacity and respect the queue: pausing prevents new rounds, while an active round continues. The reviewer inspects the saved candidate and validation evidence; this review does not execute project checks itself. Reviewer sign-offs appear on the task and in the exact result. The reviewer can ask the implementer a scoped clarification, request an in-scope correction, or send an intent, scope or access question to Inbox. Saved human answers continue the review without another apply step. A correction produces a new candidate and fresh independent assessment. Changes to the agreement or authority require Coordinator reconciliation; an answer does not silently amend them. Waiting for an answer releases capacity. Ask the Coordinator to stop a review; stopping preserves the candidate and findings. Failed or stopped reviews require explicit Retry review. If cleanup is uncertain, inspect Review rounds and diagnostics, confirm the retained processes have stopped, then retry. Uncertain execution keeps its capacity reserved. Changed inputs make an assessment outdated and retain its evidence; questions belonging to that assessment are withdrawn with their saved answers preserved. An independent approval recommends the candidate. Code delivery still needs your exact approval. Complete file and report results finish after the configured review. Stop an active review before making a manual result decision. Assessment alone grants no delivery authority.

​
Review an exact result

Read the worker report, limitations and checks against the task’s success criteria. Project checks and worker-authored tests are useful evidence; try representative inputs or ask the Coordinator to investigate gaps before deciding what ships. Access results opens the selected code result with its copyable launch command directly visible. Code changes shows the candidate’s changed files and diff. Supporting files remain available below the outcome. See worker setup. Trying or inspecting a result grants no approval. Code changes and exact-result review beside the Coordinator Choose Request changes to send concrete feedback for another pass. Attach relevant files or testing observations when needed. Or choose Approve and integrate, confirm the selected result and optionally include a testing comment. Explicit approval in the Coordinator conversation records the same exact decision without a second browser confirmation. Flowfield checks and delivers the approved candidate to the configured project checkout. Conflicting local changes remain intact. Resolve the reported blocker and use its delivery retry action; if the candidate changes, review and approve the new result. A complete report-only result can finish without code approval.

​
Find delivered outcomes

Inbox → Delivered lists completed tasks by delivery time. Opening a result does not remove it or require acknowledgment. Code results show their destination and Access results; file and report results show their retained outputs. Browse outputs across tasks in Files. Delivery updates the configured local branch and registered checkout. It does not push, deploy or publish your project. Tasks in different repositories have separate results and approvals; Flowfield does not deliver them as one atomic change.

​
Earlier results and follow-ups

Completed tasks keep their delivered snapshots when prerequisites change later. Earlier results remain available through the task feed and exact result links. New work does not update a preview you already opened. Ask the Coordinator to create a new task for a new outcome, or reopen a task for a correction. Reopening retains earlier results, files and approvals; the new outcome needs fresh preparation and any required code approval.