Flowfield v0.6.0

Features

• Tasks replace milestones as the unit of planning and delivery, with optional local subtasks and dependencies. Flowfield assembles contributions into one outcome with one task review and final delivery.
• Give each task an independent Reviewer, with its own harness/model choice. Reviewers assess the whole result, request scoped corrections and bring questions to Inbox. Code still requires your exact approval.
• Create reports, images and datasets without a repository. Browse retained outputs in Files, preview images, CSV, text, Markdown and code, and supply exact files to later tasks.
• Work from an Inbox with Needs me, Delivered and History. Answer requests directly, return to completed outcomes and keep related tasks, documents and results open beside the Coordinator. Work tabs restore their order and navigation history when you return in the same browser.

Improvements

• Keep task purpose, local contributions, questions, corrections and reviewer sign-offs in one chronological feed. Exact requests and results own response actions, while task Settings holds Worker and Reviewer overrides.
• Create a workspace with one agent choice, or customize Coordinator, Worker and Reviewer roles. Workspace and task settings retain independent choices, including supported Fast mode.
• Configure document usage from its editor or through the Coordinator, including defaults for tasks without a project. Prepared assignments keep their selected revisions. Maintain the shared label catalogue in workspace settings.
• Try exact code results through a directly visible launcher, inspect their diffs and approve delivery to the configured local branch. Project settings can explicitly permit workers to run saved validation commands through Flowfield.
• Save queue auto-start as a workspace preference independently of the sidebar’s current Run/Pause state. New workspaces default to five parallel workers.

Bug fixes

• Preserve saved answers and review context through correction and recovery, keep resolved requests historical when reopening work, and retain completed deliveries when prerequisites change later.
• Give Reviewers the exact source files and retained outputs needed to verify reports and assembled task results.
• Retain a subtask's existing code when correcting it against current dependencies, carry correction feedback into dependent contributions, and preserve unaffected work.
• Keep approval controls disabled while saving and apply the saved decision immediately. Preserve unrelated drafts and reading positions during navigation and refresh.
• Render saved Coordinator replies directly, keep task pages stationary while expanded activity follows new output, and avoid turning a single notification timeout into a service-wide interruption.

Breaking changes

• Milestones and their separate board, review and delivery controls are replaced by workspace tasks. Task APIs, MCP tools and CLI commands use workspace identity; older task and milestone routes are removed.
• Older Flowfield databases are no longer migrated. Existing incompatible stores are rejected without automatic deletion. The earlier database backup and restore commands are removed.

Upgrade

Stop all Flowfield services before upgrading. The default data directory is ~/.flowfield on macOS/Linux and %USERPROFILE%\.flowfield on Windows. If you set FLOWFIELD_DATA_DIR or --data-dir, use that directory instead. Preserve the entire directory and relevant repositories, then rename the old directory to an unused backup name such as .flowfield-before-0.6.0. Starting Flowfield again creates a fresh store at the original location; create a workspace and adopt your existing repositories. Alternatively, start with flowfield --data-dir /absolute/path/to/new-flowfield-data serve.

Once you have verified the backup and no longer need the old work history, you can delete that old Flowfield data directory. Keep your project repositories, native harness configuration and credentials. Old state requires its matching Flowfield build for access. See starting fresh.