Skip to main content
subagent CX Codex

task_decided — Claude Code subagent: what it does, how to install

The task_decided Claude Code subagent records an owner's answer to a pending task decision. It captures the choice when the owner gives it in the conversation.

MIT ★ 395 updated 2026-11-16

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/task_decided.md
Open on GitHub

What task_decided does

task_decided saves the owner's answer to a task decision that is waiting in its to-do list. It accepts only the owner's words from the main conversation or the task's supervisor. An agent's own judgement does not count as the owner's decision.

The record needs the task ID, the exact label of the chosen option, and the owner's words. If the answer matches no option, the subagent asks for clarification or for the decision to be revised with task_review. With told_agent: false, the hub sends the selected option to the task agent and records it; if that agent cannot be reached, the record is refused. With told_agent: true, the answer has already been sent through agent_send, so the subagent only records it. The decision then leaves the pending list.

What it helps with

  • record an owner's answer to a pending task decision
  • save the owner's wording alongside the selected option
  • close a pending decision after its answer was sent with agent_send

Example prompts for the agent

  • Record my answer, “choose the first option,” for task decision todo_123.
  • I choose “Defer.” Save my answer to this task decision.
  • I already sent the answer with agent_send; record it for todo_123.

How to install task_decided

Manually: put the files in place

.claude/agents/task_decided.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about task_decided

How do I install task_decided in Claude Code?

Add .claude/agents/task_decided.md to the project.

What does task_decided do?

It records the owner's words and chosen option for a pending task decision. If the answer was already sent to the task agent with agent_send, it only saves the record.

What information does task_decided need to record an answer?

It needs the task ID, the exact label of the chosen option, and the owner's words. If the answer matches none of the options, it asks for clarification or for the decision to be revised with task_review.

Source text

task_decided.md · MIT
Record the owner's answer to a task's waiting decision (a needs_user decision on its to-do) when they gave it to you in this conversation, in their own words, instead of on the decision's card or row. Only from the main conversation or the task's supervisor, and only what the owner said: never your own call (a decision that is yours is no decision: send the agent on, or review the task). option is the label of one of the decision's options, the one their words choose; when their words fit none of them, don't record it: ask them, or restate the decision with task_review. With told_agent false the hub takes the option as the card does: it goes to the task's agent and is recorded (refused, and nothing recorded, while the agent cannot be reached). With told_agent true you already passed their answer to the agent with agent_send, and it is only recorded. Either way the decision ends as if they had answered it on its card: it leaves their Needs you, is not raised again, the to-do lists it among its decisions with their words, and the task is supervised as before. So when the owner answers a task's open decision in the chat, record it here; relaying it with agent_send alone leaves the decision waiting.

```json
{
  "type": "object",
  "required": ["todo_id", "option", "said"],
  "properties": {
    "todo_id": {
      "type": "string",
      "description": "the task's todo id (todo_…)"
    },
    "option": {
      "type": "string",
      "description": "the label of the option the owner chose, exactly as the decision lists it"
    },
    "said": {
      "type": "string",
      "description": "what the owner said, quoted (one or two sentences)"
    },
    "told_agent": {
      "type": "boolean",
      "description": "true when you already sent their answer to the task's agent (agent_send): it is only recorded; default false: the hub sends the option to the agent as the card does"
    }
  }
}
```

© nwverse · MIT · nwverse/persona

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

From the same set61

The whole set →
interaction_answer The interaction_answer Claude Code subagent answers another agent’s question on the user’s behalf when the user has chosen an answer or delegated the choice. It picks from the offered options and leaves personal decisions to the user. CX Codex ★ 395repo stars agent_autoname_receipt The agent_autoname_receipt Claude Code subagent reads existing name-confirmation cards and one coding agent’s current naming snapshot. It helps inspect the available evidence about a rename. CX Codex ★ 395repo stars ask_escalate The ask_escalate Claude Code subagent routes decisions that task agents cannot make to the user. It groups unanswered task questions into one reminder. CX Codex ★ 395repo stars agent_supervise The agent_supervise Claude Code subagent takes over an agent that was started without a task and tracks its work as a task in the current conversation. It routes progress messages to a supervisor and closes the task with task_review. CX Codex ★ 395repo stars agents_list agents_list — a subagent for Claude Code and Codex monitoring running herdr sessions across user machines. Displays active jobs, pending approvals, and subscription limits. CX Codex ★ 395repo stars task_scope task_scope — a subagent for Claude Code revises a supervised task after it starts. It updates the completion criteria and time estimate, with the change shown to the owner in their next digest. CX Codex ★ 395repo stars agent_archive Subagent for Claude Code moves a coding agent session from the active list to the archive. It triggers when cleaning up or archiving agent sessions. CX Codex ★ 395repo stars agent_switch This subagent for Claude Code moves a running agent to another launcher on the same computer. It switches sessions only when the user asks. CX Codex ★ 395repo stars

Project sponsors

Companies that keep this analytics open