> This page is for Harness.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.moveworks.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.moveworks.com/_mcp/server.

# Planning

> **Controlled Availability**
>
> The Agentic Orchestrator is in Controlled Availability and comes to your Enterprise Assistant in Q1 2027. Capabilities, limits, and interface labels described here may change before general availability. To request access, contact your Moveworks account team.

The Agentic Orchestrator handles each request at the lowest execution tier that fully covers it. Most requests never need a plan, since each plan costs the user a review before work starts.

```mermaid
flowchart LR
    R["Request"] --> Q1{"Answerable<br />from context?"}
    Q1 -->|Yes| A["Answer directly"]
    Q1 -->|No| Q2{"More than 3 steps,<br />or plan requested?"}
    Q2 -->|No| T["Ad hoc tool calls"]
    Q2 -->|Yes| P["Plan: user reviews,<br />then it runs"]
```

## How It Works

* **Choosing a tier.** Anything answerable from the conversation gets a direct answer. Three or fewer steps run as ad hoc tool calls. Longer work gets a plan, especially when results feed later calls or the user should approve the approach first.
* **Plan review.** The user sees a short task list and replies to approve, request changes, or cancel. Changes come back as a revised plan. An ambiguous "no" doesn't cancel; the Orchestrator asks.
* **Sign-off.** Destructive, irreversible, or broad-reach actions need explicit sign-off first: plan review for planned work, a direct confirmation for ad hoc calls, unless the user just asked for exactly that action.
* **Concurrency.** Independent ad hoc calls in one response run concurrently as a batch. In a plan, phases and batches run in order, and the steps within a batch run concurrently.
* **Waiting.** The active plan's status and goal stay in context every turn. When the session needs the user, it suspends instead of holding a request open and resumes on the next message. Asynchronous results from external systems fold back in when they arrive.

## Configure

* Instructions can't turn off plan review or the sign-off rule.
* To show the user exact values before a specific action runs, set the action activity's **Confirmation Policy** in the plugin's [Conversation Process](/tool-studio/conversation-process/activities#activity-confirmation-policies).

## Related

* [Memory](/harness/agentic-orchestrator/memory): context, session state, and retention.
* [Tool Orchestration](/harness/agentic-orchestrator/tool-orchestration): how tools are called.