Tasks
Tasks separates the record of work from the Agent execution that may act on it. A Task remains the workspace-visible plan and result; each start creates a distinct Task Run with its own snapshot and lifecycle.
You need Manage tasks permission to open the Tasks app or change its data.
Create a board and Task
- Open Tasks in the app switcher.
- Create or select a board.
- Add a Task with a title and description.
- Optionally set priority, due date, labels, dependencies, a checklist, attachments, and a report Channel.
- Assign an active Agent.
Assignment does not start execution. This lets a member prepare, review, and sequence work before consuming Agent resources.
Statuses
| Status | Meaning |
|---|---|
| Backlog | Recorded but not ready to start. |
| Ready | Prepared for work. |
| Running | Owned by one active Workflow-backed run. |
| Review | The run completed and its result needs human review. |
| Done | The work has been accepted as complete by the team. |
| Failed | The latest run failed and may need correction or another run. |
Members can move Tasks between non-running columns. Only the execution lifecycle enters or leaves Running.
Start and follow a run
Select Run on a Task that has an active Agent and no incomplete dependency. Discoflare atomically claims the Task, snapshots the Task and Agent configuration, and starts one Cloudflare Workflow.
While it runs, the board and Task detail show progress. The run uses an isolated Agent reasoning context and the Agent's checkpointed Sandbox computer. If a report Channel is configured, the Agent can publish the result back into Chat.
Cancel or recover
- Cancel terminates the active Workflow and restores the Task status it had before the run.
- Check run reconciles the Task and run records with the Workflow when a request or client update was interrupted.
- A failed run keeps its error and history; correcting the Task does not erase the earlier attempt.
Only one run can own a Task at a time. Starting twice, starting an archived Task, using a paused Agent, or starting before dependencies are complete is rejected.
Review the result
Open the Task detail to inspect its current summary, details, attachments, checklist, and Run history. The durable Run proves that execution reached an outcome; it does not prove that a human accepted the work, a pull request merged, or a production deployment succeeded.
Move the Task to Done only after applying the evidence appropriate to the work. For software work, that may include tests, a diff or pull request, a preview, and a separate production check.
The Agents roadmap describes planned work around stronger evidence and GitHub-backed delivery.