Skip to main content

nut task

Manage tasks (change proposals) in your Coconut instance.
Aliases: task, proposal

Overview

Tasks (also known as change proposals) are the core unit of work in Coconut. They represent features, bugs, refactors, or any change you want to implement in your codebase. The nut task command provides comprehensive management of tasks throughout their lifecycle.
nut task manages tasks in the current local workspace. To list, create, or update tasks on a remote peer Coconut through the Coconut Dashboard, use nut coconut task.

nut task list

List all tasks in your repository.
Options:
  • --status <status> - Filter by status (draft, backlog, ready, queued, active, blocked, review, done, canceled, duplicate)
  • --search <query> - Search tasks by text
  • --json - Output as JSON
Examples:

nut task get

Get detailed information about a specific task.
Arguments:
  • id - The task ID (e.g., cp-1234567890)
Options:
  • --json - Output as JSON
Examples:

nut task create

Create a new task.
Arguments:
  • title - Title or description of the task
Options:
  • -p, --priority <level> - Set priority (low, medium, high, critical)
  • -t, --tags <tags> - Comma-separated tags
  • -s, --status <status> - Initial status (draft, backlog, ready, queued, active, blocked, review, done, canceled, duplicate)
  • --author <name> - Author name
  • --email <email> - Author email
  • --type <type> - Author type (human or agent, default: human)
  • -c, --content <text> - Detailed description or content for the task
  • -f, --file <path> - Read content from a file
  • -r, --readiness <score> - Readiness score (0–100)
  • --spec <ref> - Product specification reference
  • --json - Output as JSON
  • -y, --yes - Skip confirmation prompts
Examples:
Clear, descriptive intents help AI skills better understand and implement tasks. Use -c or -f to provide additional context that helps agents plan implementation.

nut task update

Update an existing task’s properties.
Arguments:
  • id - The task ID to update
Options:
  • -t, -i, --title, --intent <text> - Update title (aliases: -i, —intent)
  • -c, --content <text> - Update content
  • -f, --file <path> - Read new content from a file
  • -s, --status <status> - Update status (draft, backlog, ready, queued, active, blocked, review, done, canceled, duplicate)
  • -p, --priority <level> - Update priority (low, medium, high, critical)
  • --tags <tags> - Update tags (comma-separated)
  • --spec <ref> - Update product specification reference
  • --json - Output as JSON
Examples:

nut task step

Add a plan step to a task.
Arguments:
  • id - The task ID
  • description - Description of the step
Options:
  • --command <cmd> - Optional command to execute for this step
Examples:
Plan steps help break down complex tasks into manageable pieces and provide structure for implementation.

nut task comment

Add a comment to a task.
Arguments:
  • id - The task ID
  • content - Comment text
Options:
  • --author <email> - Comment author (defaults to current user)
Examples:

nut task delete

Delete a task.
Arguments:
  • id - The task ID to delete
Examples:
Deleting a task is permanent. Make sure you want to remove it before confirming.

Complete Workflow Example

Here’s a complete workflow using task commands:
1

Create a task

Returns: Created task cp-1234567890
2

Add plan steps

3

Start implementation

4

Update status

5

Add review comments

6

Mark complete

Finding Task IDs

If you need to find a task ID:
  1. Use nut task list to see all tasks
  2. Use nut task list --search "keyword" to search
  3. Task IDs follow the format cp-XXXXXXXXXX