Sweep 22 Sep 2026 · 15:52Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Reading a new release v2.1.280 Building the pages · 4/6 1043 findings $36.88 so far
Tool description

TaskCreate, as sent

CLI Claude Code, interactive mode, v2.1.269. 12 model strings share this prompt, byte for byte.

Lines402,146 characters
Moved+0−0 against v2.1.268
Reach12model strings receive this description
Copies1distinct descriptions under this name
Parameters42 of them required Tools in captureall of themevery description on this arm
Plain text · sha256 995575dbea8f

The description, rendered

This renders the markdown inside the description, so it isn’t quite the description itself.

The raw view and the plain text are the bytes as they were sent.

Use this tool to create a structured task list for your current coding session. This helps you track progress, organize complex tasks, and demonstrate thoroughness to the user. It also helps the user understand the progress of the task and overall progress of their requests.

When to Use This Tool

Use this tool proactively in these scenarios:

  • Complex multi-step tasks - When a task requires 3 or more distinct steps or actions
  • Non-trivial and complex tasks - Tasks that require careful planning or multiple operations
  • Plan mode - When using plan mode, create a task list to track the work
  • User explicitly requests todo list - When the user directly asks you to use the todo list
  • User provides multiple tasks - When users provide a list of things to be done (numbered or comma-separated)
  • After receiving new instructions - Immediately capture user requirements as tasks
  • When you start working on a task - Mark it as in_progress BEFORE beginning work
  • After completing a task - Mark it as completed and add any new follow-up tasks discovered during implementation

When NOT to Use This Tool

Skip using this tool when:

  • There is only a single, straightforward task
  • The task is trivial and tracking it provides no organizational benefit
  • The task can be completed in less than 3 trivial steps
  • The task is purely conversational or informational

NOTE that you should not use this tool if there is only one trivial task to do. In this case you are better off just doing the task directly.

Task Fields

  • subject: A brief, actionable title in imperative form (e.g., "Fix authentication bug in login flow")
  • description: What needs to be done
  • activeForm (optional): Present continuous form shown in the spinner when the task is in_progress (e.g., "Fixing authentication bug"). If omitted, the spinner shows the subject instead.

All tasks are created with status pending.

Tips

  • Create tasks with clear, specific subjects that describe the outcome
  • After creating tasks, use TaskUpdate to set up dependencies (blocks/blockedBy) if needed
  • Check TaskList first to avoid creating duplicate tasks

What it accepts

4 parameters The JSON parameter schema sent beside this description, 687 characters of it. Name, type, then whether the client marked it required.
activeForm string optional Present continuous form shown in spinner when in_progress (e.g., "Running tests")
description string required What needs to be done
metadata object optional Arbitrary metadata to attach to the task
subject string required A brief title for the task

sha256 f08c2d6156af · the schema as the client sent it:

{ "$schema": "https://json-schema.org/draft/2020-12/schema", "additionalProperties": false, "properties": { "activeForm": { "description": "Present continuous form shown in spinner when in_progress (e.g., \"Running tests\")", "type": "string" }, "description": { "description": "What needs to be done", "type": "string" }, "metadata": { "additionalProperties": {}, "description": "Arbitrary metadata to attach to the task", "propertyNames": { "type": "string" }, "type": "object" }, "subject": { "description": "A brief title for the task", "type": "string" } }, "required": [ "subject", "description" ], "type": "object" }