Skip to navigation
Agentic Orchestrator

Memory

What the Agentic Orchestrator keeps in context during a conversation, how sessions resume, and how long state is kept.
View as Markdown
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 works from one conversation at a time. What the model sees depends on the layer: some context is sent on every call, some is refreshed each turn, and the rest is fetched only when the model asks.

LayerWhat the model sees
AlwaysThe Orchestrator’s base prompt; your instructions; each Skill’s name and description; the user’s profile (name, email, role, department, timezone, and similar); tool names, with full schemas for built-in tools only
Every turnCurrent date and time in the user’s timezone; the active plan’s status and goal; session variable names and descriptions; a digest of plan changes the model already made
HistoryEarlier messages, tool calls, tool results, and plan step results in this conversation
On demandSkill bodies, deferred tool schemas, variable values, file contents, images

How It Works

  • Suspend and resume. When the session waits on the user, for example for plan review or a confirmation, it saves its state and stops. The next message resumes it with the full history and any active plan.
  • Trimming. As history nears the model’s context budget, the oldest tool calls and their results are dropped first. Your instructions and the newest user message are never trimmed.
  • Session variables. Large tool results are stored as session variables instead of being placed in the prompt. The model sees each variable’s name and description, reads the value only when it needs it, and can save its own values for later steps.
  • Cost of the always layer. That layer is sent on every model call. Keep instructions short and move long procedures into Skills, which load on demand.
  • No long-term memory. A new conversation starts empty. Nothing carries over between sessions.

Limits

ItemValue
Session state, plans, and variablesKept for 30 days
One run, from a message until the session finishes or waitsUp to 1 hour
  • Planning: execution tiers, plan review, and waiting.
  • Skills: move long procedures out of the always layer.