Documentation Index

Fetch the complete documentation index at: https://agentclientprotocol.com/llms.txt Use this file to discover all available pages before exploring further.

Agent Plan

How Agents communicate their execution plans

Plans are execution strategies for complex tasks that require multiple steps.

Agents may share plans with Clients through session/update notifications, providing real-time visibility into their thinking and progress.

plan_update carries a plan object with a type discriminator and a required planId so Clients can track multiple plans independently.

The plan content type is items. Additional plan operations remain unstable while the Plan Operations RFD is in progress.

Creating Plans

When the language model creates an execution plan, the Agent SHOULD report it to the Client with plan_update.

Item-Based Plans

{
  "jsonrpc": "2.0",
  "method": "session/update",
  "params": {
    "sessionId": "sess_abc123def456",
    "update": {
      "sessionUpdate": "plan_update",
      "plan": {
        "type": "items",
        "planId": "plan-1",
        "entries": [
          {
            "content": "Analyze the existing codebase structure",
            "priority": "high",
            "status": "pending"
          },
          {
            "content": "Identify components that need refactoring",
            "priority": "high",
            "status": "pending"
          },
          {
            "content": "Create unit tests for critical functions",
            "priority": "medium",
            "status": "pending"
          }
        ]
      }
    }
  }
}

Extensibility

plan.type values can be custom or future variants when Clients can preserve or display them generically. Custom plan content types MUST begin with _; unknown non-underscore plan content types are reserved for future ACP variants.

Every plan content variant, including custom or future variants, MUST carry a planId.

Plan Entries

Each plan entry represents a specific task or goal within the overall execution strategy: