Tasks and approvals

Use a task when work needs state

Chat is useful for quick requests. Create a task when the work needs an owner, status, due date, review, or durable result.

Define the outcome before starting: a cited comparison, an inspectable CSV, a tested change, or a draft ready for review. “The agent finished talking” is not the same as “the work is accepted.”

A task can be assigned to a person or an agent. An assigned agent can claim the task through CrewX and report progress while it works.

Task status

Tasks move through these states:

Status	Meaning
Backlog	Captured but not ready to start
To do	Ready for the assignee
In progress	The assignee is working
Review	Output is ready for a person to inspect
Done	Work is accepted
Cancelled	Work will not continue

The activity history records assignment changes, status changes, comments, results, and review decisions.

Why a task may need approval

Human approval is optional and configured per task. When Require approval is enabled, an agent cannot make the task accepted simply by marking its work complete.

Instead, the task moves to Review and a workspace reviewer can:

• Approve the result
• Request changes with a note

Approval is for the work product. Runtime file edits and shell commands are governed separately by the agent permission preset and the local runtime.

Run an agent task

Create the task, select a project channel, assign an eligible agent, and choose Run task. The project supplies shared context. For a connected agent, choose an appropriate approved checkout; a path on your laptop is not a path on a cloud agent’s computer.

If Run task is unavailable, check that:

• The task has an agent assignee
• The agent is not chat-only
• The agent can access the project on the machine where it runs
• The agent is online
• The runtime and computer have available capacity

Record the result

Agents can update their assigned tasks and attach a written result. A person can add comments, change the status, or request another revision without losing the earlier activity history.

Recurring requests are not schedules

General routines are not yet a released self-service feature. Where the gated implementation is enabled, an agent can turn “check this every day” into an inactive proposal. A person must review and activate it before CrewX schedules work. Without an activated routine, a chat request alone does not establish a durable schedule. See recurring responsibilities.

For requests such as “improve SEO, create PRs, merge and deploy,” separate data access, proposed changes, test results, merge authority, and deployment authority. Do not treat a green CI run or an agent’s completion message as approval for every downstream action.