Skip to main content

​
nut task

Manage tasks (change proposals) in your Coconut instance. 
nut task [command]
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 list

List all tasks in your repository. 
nut task list [options]
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: 
# List all tasks
nut task list

# Filter by status
nut task list --status draft
nut task list --status active

# Search for specific tasks
nut task list --search "authentication"

​
nut task get

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

​
nut task create

Create a new task. 
nut task create <title> [options]
Arguments:
  • title - Title or description of the task
Options:
  • --priority <level> - Set priority (low, medium, high, critical)
  • --tags <tags> - Comma-separated tags
  • --status <status> - Initial status (draft, backlog, ready, queued, active, blocked, review, done, canceled, duplicate)
Examples: 
# Create a simple task
nut task create "Add user authentication"

# Create with priority and tags
nut task create "Fix bug in payment processing" --priority high --tags "bug,urgent"

# Create with specific status
nut task create "Refactor database layer" --priority medium --tags "refactor"
Clear, descriptive intents help AI skills better understand and implement tasks.

​
nut task update

Update an existing task’s properties. 
nut task update <id> [options]
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: 
# Update task status
nut task update cp-1234567890 --status review

# Change priority
nut task update cp-1234567890 --priority critical

# Update title
nut task update cp-1234567890 --title "New task title"

# Update content from file
nut task update cp-1234567890 --file path/to/content.md

# Update multiple properties
nut task update cp-1234567890 --status done --priority low --tags "completed,deployed"

​
nut task step

Add a plan step to a task. 
nut task step <id> <description> [options]
Arguments:
  • id - The task ID
  • description - Description of the step
Options:
  • --command <cmd> - Optional command to execute for this step
Examples: 
# Add a simple plan step
nut task step cp-1234567890 "Implement user authentication"

# Add step with command
nut task step cp-1234567890 "Run tests" --command "npm test"

# Add multiple steps
nut task step cp-1234567890 "Create database schema"
nut task step cp-1234567890 "Implement API endpoints"
nut task step cp-1234567890 "Add frontend components"
Plan steps help break down complex tasks into manageable pieces and provide structure for implementation.

​
nut task comment

Add a comment to a task. 
nut task comment <id> <content> [options]
Arguments:
  • id - The task ID
  • content - Comment text
Options:
  • --author <email> - Comment author (defaults to current user)
Examples: 
# Add a comment
nut task comment cp-1234567890 "Looks good, approved!"

# Add comment with specific author
nut task comment cp-1234567890 "Please review" --author "reviewer@example.com"

# Add detailed feedback
nut task comment cp-1234567890 "Great work! Just need to update the tests before merging."

​
nut task delete

Delete a task. 
nut task delete <id>
Arguments:
  • id - The task ID to delete
Examples: 
nut task delete cp-1234567890
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

nut task create "Add dark mode support" --priority high --tags "feature,ui"
Returns: Created task cp-1234567890
2

Add plan steps

nut task step cp-1234567890 "Add theme toggle component"
nut task step cp-1234567890 "Update CSS variables for dark mode"
nut task step cp-1234567890 "Add user preference persistence"
nut task step cp-1234567890 "Test in all browsers" --command "npm run test:e2e"
3

Start implementation

nut code cp-1234567890
4

Update status

nut task update cp-1234567890 --status review
5

Add review comments

nut task comment cp-1234567890 "Implementation complete, ready for review"
6

Mark complete

nut task update cp-1234567890 --status done

​
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