@mastra/mcp-docs-server 1.1.49-alpha.1 → 1.2.0-alpha.0

package/.docs/docs/harness/modes.md

@@ -0,0 +1,124 @@
+# Modes
+
+Modes define the different behaviors a Harness can run. Each mode layers its own instructions and tool overrides on top of a shared backing agent, so the same agent can act as a planner in one mode and an executor in another. The Harness keeps exactly one mode active at a time, carries the thread and state across switches, and handles the transition between them.
+
+Every Harness needs at least one mode — the `modes` array is required, and the Harness throws at construction if it's empty. A single-purpose Harness still defines one mode; multiple modes are how you give a session more than one behavior to switch between.
+
+A mode supplies three things that change how the agent behaves:
+
+- **Instructions**: layered on top of the backing agent's own instructions while the mode is active.
+- **Tools**: either replacing or adding to the backing agent's tools (see [Mode tool overrides](#mode-tool-overrides)).
+- **Model**: an optional `defaultModelId` to bootstrap model selection when the session enters the mode.
+
+Because every mode shares the same backing agent, thread, and state, switching modes changes how the agent behaves without losing conversation context.
+
+## Quickstart
+
+Import the `Harness` class and create a new instance with your agent and modes:
+
+```typescript
+import { Harness } from '@mastra/core/harness'
+import { myAgent } from './agents'
+
+const harness = new Harness({
+  id: 'multi-mode',
+  agent: myAgent,
+  modes: [
+    {
+      id: 'plan',
+      name: 'Plan',
+      metadata: { default: true },
+      instructions: 'Reason about the task before making changes.',
+    },
+    { id: 'build', name: 'Build', instructions: 'Implement the approved plan.' },
+  ],
+})
+
+await harness.init()
+```
+
+## Defining modes
+
+Each mode requires an `id`. When a top-level `agent` is provided, modes layer instructions and tool overrides on the shared agent. Each mode can also specify a `defaultModelId` to bootstrap model selection:
+
+```typescript
+import { Harness } from '@mastra/core/harness'
+
+const harness = new Harness({
+  id: 'multi-mode',
+  agent: myAgent,
+  modes: [
+    {
+      id: 'plan',
+      name: 'Plan',
+      metadata: { default: true },
+      defaultModelId: 'anthropic/claude-sonnet-4-6',
+      instructions: 'Reason about the task before making changes.',
+    },
+    {
+      id: 'build',
+      name: 'Build',
+      defaultModelId: 'anthropic/claude-sonnet-4-6',
+      instructions: 'Implement the approved plan.',
+    },
+  ],
+})
+```
+
+### Mode tool overrides
+
+Modes support two strategies for tool configuration. Use `tools` to replace the backing agent's tools entirely, or `additionalTools` to layer extra tools on top:
+
+```typescript
+// Replace — agent sees only these tools in plan mode
+const planMode = { id: 'plan', tools: { planTool } }
+
+// Augment — agent keeps its own tools plus these
+const buildMode = { id: 'build', additionalTools: { deployTool } }
+```
+
+You can't set both `tools` and `additionalTools` on the same mode.
+
+### Mode transitions
+
+A mode can declare a `transitionsTo` target. When the `submit_plan` built-in tool runs in that mode, the Harness transitions to the target mode on approval:
+
+```typescript
+const planMode = {
+  id: 'plan',
+  name: 'Plan',
+  transitionsTo: 'build',
+  instructions: 'Reason about the task and submit a plan.',
+}
+```
+
+On plan approval, the Harness automatically switches to `build` mode. On rejection, the agent remains in `plan` mode to revise.
+
+## Switching modes
+
+Call `switchMode()` to change the active mode. The Harness aborts any in-progress generation, saves the current model to the outgoing mode, loads the incoming mode's model, and emits `mode_changed` and `model_changed` events:
+
+```typescript
+await harness.switchMode({ modeId: 'build' })
+```
+
+## Querying modes
+
+The Harness exposes the full mode catalog, while the Session tracks which mode is active. Use `harness.listModes()` to read every configured mode, `harness.session.mode.get()` for the active mode ID, and `harness.session.mode.resolve()` for the active mode's full definition:
+
+```typescript
+// List all configured modes
+const modes = harness.listModes()
+
+// Get the current mode ID
+const modeId = harness.session.mode.get()
+
+// Get the full mode object
+const mode = harness.session.mode.resolve()
+```
+
+## Related
+
+- [Harness overview](https://mastra.ai/docs/harness/overview)
+- [Threads and state](https://mastra.ai/docs/harness/threads-and-state)
+- [API reference](https://mastra.ai/reference/harness/harness-class)

package/.docs/docs/harness/overview.md

@@ -0,0 +1,130 @@
+# Harness overview
+
+> **Alpha:** The `Harness` feature is in alpha stage and subject to breaking changes in minor versions until it graduates from its alpha status.
+
+The Harness is a session controller for building interactive agent applications. It handles the runtime concerns that sit between your UI and the agent loop: managing conversation threads, switching between agent modes, persisting state, gating tool execution with approvals, and coordinating subagents. You can focus on what your agent does rather than how to wire it together.
+
+A Harness exposes a [`Session`](https://mastra.ai/docs/harness/session) — the per-conversation runtime state that tracks the active mode, model, thread binding, permission grants, follow-up queue, and token usage. The Harness is the shared host; the Session is the conversation running inside it. In a multi-user host, the same Harness can back many Sessions at once.
+
+[Mastra Code](https://code.mastra.ai/) is the flagship Harness implementation: A terminal-based coding agent with multi-model support, persistent conversations, and plan-then-execute workflows.
+
+## What you can build
+
+The Harness gives you the runtime pieces to ship interactive agent applications. Each outcome below maps to a capability you can use today:
+
+- **Resume a conversation exactly where the user left off.** Persistent [threads and state](https://mastra.ai/docs/harness/threads-and-state) reload the active mode, model, and progress across restarts, so a coding agent or assistant picks up mid-task instead of starting over.
+- **Gate destructive actions behind human approval.** [Tool approvals and permission policies](https://mastra.ai/docs/harness/tool-approvals) let you require confirmation for risky operations like file writes or deployments, while trusted tools run automatically.
+- **Move a task through distinct phases without losing context.** [Modes](https://mastra.ai/docs/harness/modes) switch the agent's instructions, tools, and model on the same thread, so you can build a plan-then-execute coding agent or a research-then-draft assistant.
+- **Let users pick the right model for each step.** Per-mode [model management](https://mastra.ai/reference/harness/harness-class) switches models at runtime and tracks usage, which powers copilot UIs where users trade speed for capability.
+- **Delegate focused work to child agents.** [Subagents](https://mastra.ai/docs/harness/subagents) run subtasks with constrained tools and can fork the parent conversation, so a research mode can spin off web search or code review without polluting the main thread.
+- **Drive a live UI from agent activity.** The [event system](https://mastra.ai/docs/harness/session) emits typed events and coalesced display snapshots, so your TUI or web app reflects message updates, mode changes, and pending approvals in real time.
+- **Run long-lived autonomous agents.** Structured task lists, heartbeat handlers, and observational memory keep background task runners on track and let them learn across threads.
+
+## When to use the Harness
+
+Use the Harness when your application needs:
+
+- Multiple agent modes that share one conversation thread (e.g., plan → build → review)
+- A control layer between your UI and the agent loop (model switching, state persistence, thread management)
+- Tool approval flows and permission policies for human-in-the-loop gating
+- Subagent orchestration to delegate focused subtasks with constrained tools
+- Session continuity with persistent threads, state, and observational memory across restarts
+
+You could assemble all of this yourself on top of the [Agent class](https://mastra.ai/docs/agents/overview), which exposes the full agent loop, tools, and memory. The Harness is an opinionated set of defaults that wires those pieces into one application style: an ongoing session where the agent acts as a collaborator rather than a one-shot endpoint. Reach for the Agent class directly when you want full control or a simple request-response call; reach for the Harness when you want the collaborative-session model without building the runtime around it.
+
+## Key capabilities
+
+- **Session**: Per-conversation state — active thread, mode, model, grants, follow-ups, token usage, and the display snapshot — accessed through `harness.session`. See [Session](https://mastra.ai/docs/harness/session).
+- **Modes**: Define distinct agent personalities (instructions, tools, model) and switch between them without losing conversation context. See [Modes](https://mastra.ai/docs/harness/modes).
+- **Threads and state**: Persist conversations and structured state across sessions, users, and mode switches. See [Threads and state](https://mastra.ai/docs/harness/threads-and-state).
+- **Subagents**: Spawn focused child agents with constrained tools for subtasks, optionally forking the parent conversation. See [Subagents](https://mastra.ai/docs/harness/subagents).
+- **Tool approvals and permissions**: Configure which tools require user confirmation, grant session-wide exceptions, and handle interactive tool suspension. See [Tool approvals](https://mastra.ai/docs/harness/tool-approvals).
+- **Model management**: Switch models per-mode at runtime, track usage, and resolve gateway-backed models through Mastra's [model router](https://mastra.ai/models).
+- **Follow-ups and steering**: Queue messages while the agent is running, or inject mid-stream instructions to redirect the agent. Built on [signals](https://mastra.ai/docs/agents/signals).
+- **Event system**: Subscribe to typed events (message updates, mode changes, tool approvals) or coalesced `HarnessDisplayState` snapshots to drive your UI. See [Events](https://mastra.ai/reference/harness/harness-class).
+- **Observational memory**: Automatic summarization and reflection across threads for long-running agent sessions. See [Observational memory](https://mastra.ai/docs/memory/observational-memory).
+
+## Quickstart
+
+Import the `Harness` class and create a new instance with an agent, storage backend, and modes:
+
+```typescript
+import { Agent } from '@mastra/core/agent'
+import { Harness } from '@mastra/core/harness'
+import { LibSQLStore } from '@mastra/libsql'
+
+const agent = new Agent({
+  name: 'assistant',
+  instructions: 'Help the user plan and complete tasks.',
+  model: 'openai/gpt-5.5',
+})
+
+const harness = new Harness({
+  id: 'my-agent',
+  agent,
+  storage: new LibSQLStore({ url: 'file:./data.db' }),
+  modes: [
+    {
+      id: 'plan',
+      name: 'Plan',
+      metadata: { default: true },
+      instructions: 'Reason about changes before making them.',
+    },
+    { id: 'build', name: 'Build', instructions: 'Implement the approved plan.' },
+  ],
+})
+
+harness.subscribe(event => {
+  if (event.type === 'message_update') {
+    console.log(event.message)
+  }
+})
+
+await harness.init()
+await harness.selectOrCreateThread()
+await harness.sendMessage({ content: 'Hello!' })
+```
+
+> **Note:** Visit the [Harness reference](https://mastra.ai/reference/harness/harness-class) for the full constructor parameters and method signatures.
+
+## Architecture
+
+The Harness sits between your application layer and the underlying agent loop:
+
+```text
+┌──────────────────────────┐
+│   Your App (TUI/Web/API) │
+└────────────┬─────────────┘
+             │ commands (sendMessage, switchMode, approve)
+             │ events (message_update, tool_approval_required)
+┌────────────▼─────────────┐
+│  Harness (shared host)   │
+│  Config · Storage        │
+│  Thread lifecycle        │
+│  Permission policy        │
+│  Subagent spawning        │
+│  Event bus               │
+│  ┌─────────────────────┐ │
+│  │ harness.session      │ │
+│  │ identity · thread    │ │
+│  │ mode · model · run   │ │
+│  │ grants · follow-ups  │ │
+│  │ display state        │ │
+│  └─────────────────────┘ │
+└────────────┬─────────────┘
+             │
+┌────────────▼──────────────┐
+│  Agent + Memory + Tools   │
+└───────────────────────────┘
+```
+
+Your app sends commands (send a message, switch mode, approve a tool call) and receives typed events. The Harness manages the lifecycle internally: persisting threads, routing to the correct mode agent, enforcing permissions, and emitting events as state changes.
+
+## Next steps
+
+- [Session](https://mastra.ai/docs/harness/session): The per-conversation state on a Harness
+- [Modes](https://mastra.ai/docs/harness/modes): Define and switch between agent personalities
+- [Threads and state](https://mastra.ai/docs/harness/threads-and-state): Manage persistent conversations
+- [Subagents](https://mastra.ai/docs/harness/subagents): Delegate focused subtasks
+- [Tool approvals and permissions](https://mastra.ai/docs/harness/tool-approvals): Human-in-the-loop gating
+- [API reference](https://mastra.ai/reference/harness/harness-class): Full constructor and method docs

package/.docs/docs/harness/session.md

@@ -0,0 +1,139 @@
+# Session
+
+A [`Session`](https://mastra.ai/reference/harness/session) holds the live state of a Harness: who the session is for, which thread is active, the selected mode and model, permission grants, queued follow-ups, token usage, application state, and the display snapshot. You reach it through `harness.session`.
+
+## What the Session tracks
+
+The Session is the live state of a single user's interaction with the Harness. It answers "what is true right now": who the session belongs to, which thread is currently bound, which mode and model are selected, what the user has approved, what's queued or running, the application state, and the snapshot to render. A session has one active thread at a time but can list, switch between, and clone many threads over its lifetime. Anything that describes the current state lives here; the Harness owns the shared infrastructure every session runs on.
+
+Because each session has its own identity and state, one Harness can serve many users at once — each backed by its own Session — without one session's mode, grants, or active thread leaking into another.
+
+The rest of this page walks through the Session's state. Each part is a focused sub-object on `harness.session`:
+
+- **Who and where**: [Identity](#identity) sets the resource the session belongs to, and [Thread](#thread) tracks the currently bound thread.
+- **How the agent behaves**: [Mode and model](#mode-and-model) controls which agent profile and model are active, and [Permission grants](#permission-grants) records what the user has approved to run without prompting.
+- **What's happening right now**: [Run state](#run-state) reflects the in-flight generation, and [Follow-ups](#follow-ups) holds messages queued to send when it finishes.
+- **What you store and render**: [State](#state) holds your application's structured data, and [Display state](#display-state) is the single snapshot your UI renders from.
+
+The Harness performs actions that change this state — switching threads, modes, or models — because those operations coordinate shared infrastructure and emit events. The Session is where you read the result. The sections below note this split where it matters.
+
+## Identity
+
+`session.identity` holds the resource ID the conversation belongs to and the currently bound thread ID. Threads are scoped to a resource ID, so this is what groups a conversation's threads together:
+
+```typescript
+const resourceId = harness.session.identity.getResourceId()
+const threadId = harness.session.thread.getId()
+```
+
+The resource ID is set on the Harness constructor and defaults to the harness `id`. See [Resource IDs](https://mastra.ai/docs/harness/threads-and-state) for how it scopes threads.
+
+## Thread
+
+`session.thread` owns the active thread binding and read access to threads and messages. The Harness performs lifecycle transitions; the Session reads the result:
+
+```typescript
+// Lifecycle transitions live on the Harness
+await harness.switchThread({ threadId: 'thread-abc123' })
+
+// Reads live on the Session
+const threads = await harness.session.thread.list()
+const messages = await harness.session.thread.listActiveMessages()
+```
+
+See [Threads and state](https://mastra.ai/docs/harness/threads-and-state) for the full lifecycle.
+
+## Mode and model
+
+The Harness defines the available modes in `config.modes`. The Session tracks which mode and model are _currently_ selected:
+
+```typescript
+// Switch mode (Harness orchestration — aborts the run, emits events)
+await harness.switchMode({ modeId: 'build' })
+
+// Read the current selection (Session state)
+const modeId = harness.session.mode.get()
+const mode = harness.session.mode.resolve()
+const modelId = harness.session.model.get()
+```
+
+See [Modes](https://mastra.ai/docs/harness/modes) for how modes carry their own model.
+
+## Permission grants
+
+The Harness owns permission _policy_ — which categories or tools require approval. The Session owns the _grants_ a user makes during the conversation. A grant lets a tool run for the rest of the session without prompting again:
+
+```typescript
+// Grant a category or tool for the rest of the session
+harness.session.grantCategory('edit')
+harness.session.grantTool('mastra_workspace_execute_command')
+
+// Inspect current grants
+const grants = harness.session.getGrants()
+```
+
+Grants are intentionally in-memory and reset when the session restarts. See [Tool approvals](https://mastra.ai/docs/harness/tool-approvals) for the approval flow.
+
+## Run state
+
+`session.run` tracks the in-flight generation: whether a run is active, its run and trace IDs, and the abort signal. Use it to reflect run status in your UI:
+
+```typescript
+if (harness.session.run.isRunning()) {
+  // show a stop button
+}
+
+// Abort the active run (Harness orchestration clears related state)
+harness.abort()
+```
+
+## Follow-ups
+
+A user may want to add to the conversation while the agent is still working. Instead of dropping or interrupting those messages, the Session queues them on `session.followUps` and sends them when the current run finishes:
+
+```typescript
+const queued = harness.session.followUps.count()
+```
+
+Queue a follow-up with `harness.followUp({ content })`. To redirect the agent mid-run instead of waiting, use `harness.steer({ content })`. Both build on [signals](https://mastra.ai/docs/agents/signals).
+
+## State
+
+`session.state` holds the conversation's application state — structured values that agents and the UI share, such as model preferences, feature flags, or progress. The Harness defines the shape with a `stateSchema`; the Session owns the live snapshot, validates updates against the schema, and emits `state_changed` on every write:
+
+```typescript
+const state = harness.session.state.get()
+await harness.session.state.set({ theme: 'light' })
+```
+
+See [Threads and state](https://mastra.ai/docs/harness/threads-and-state) for defining a schema.
+
+## Display state
+
+A conversation emits many fine-grained events: tokens streaming in, tools starting and finishing, approvals pending, tasks updating, token usage climbing. Subscribing to each event type and reassembling the current picture yourself is tedious and error-prone. `session.displayState` does that work for you.
+
+It's a reducer-maintained snapshot. The Session keeps one `HarnessDisplayState` object and folds every harness event into it as it happens, so the snapshot always reflects the latest state. It captures everything a UI needs to render: whether the agent is running and what it's streaming, which tools and subagents are active, anything waiting on the user such as approvals, the current task list, and running totals like token usage and queued follow-ups.
+
+Because it's a single object, you can drive an entire UI from one place: read the current snapshot with `get()`, and re-render whenever the Harness emits `display_state_changed` (fired after every other event):
+
+```typescript
+const snapshot = harness.session.displayState.get()
+
+// Re-render from the snapshot on every change
+harness.subscribe(event => {
+  if (event.type === 'display_state_changed') {
+    render(harness.session.displayState.get())
+  }
+})
+```
+
+This is the recommended pattern for most UIs. Subscribe to individual typed events only when you need to react to a specific transition rather than re-render the whole view.
+
+> **Note:** Visit the [Session reference](https://mastra.ai/reference/harness/session) for the full list of sub-objects and method signatures.
+
+## Related
+
+- [Harness overview](https://mastra.ai/docs/harness/overview)
+- [Threads and state](https://mastra.ai/docs/harness/threads-and-state)
+- [Tool approvals](https://mastra.ai/docs/harness/tool-approvals)
+- [Session reference](https://mastra.ai/reference/harness/session)

package/.docs/docs/harness/subagents.md

@@ -0,0 +1,104 @@
+# Subagents
+
+Subagents let a parent agent delegate focused tasks to child agents with constrained tools and instructions. The Harness auto-generates a `subagent` built-in tool that the parent model can call to spawn any configured subagent type. Reach for a subagent when a task needs a different toolset or instruction set than the parent agent, when you want to isolate a subtask's messages from the parent thread, or when the parent should delegate to a cheaper or faster model for specific work.
+
+## Quickstart
+
+Define subagent types in the Harness constructor:
+
+```typescript
+import { Agent } from '@mastra/core/agent'
+import { Harness } from '@mastra/core/harness'
+
+const agent = new Agent({
+  name: 'assistant',
+  instructions: 'Use subagents when a focused task needs a narrower toolset.',
+  model: 'openai/gpt-5.5',
+})
+
+const harness = new Harness({
+  id: 'with-subagents',
+  agent,
+  modes: [{ id: 'default', name: 'Default', metadata: { default: true } }],
+  subagents: [
+    {
+      id: 'explore',
+      name: 'Explore',
+      description: 'Reads files and gathers context without making changes.',
+      instructions: 'You are a read-only exploration agent.',
+      allowedWorkspaceTools: ['read_file', 'list_directory', 'grep_search'],
+      defaultModelId: 'anthropic/claude-haiku-4-5',
+      maxSteps: 30,
+    },
+    {
+      id: 'execute',
+      name: 'Execute',
+      description: 'Makes changes to files and runs commands.',
+      instructions: 'You are an execution agent.',
+      allowedWorkspaceTools: ['read_file', 'write_file', 'execute_command'],
+      defaultModelId: 'anthropic/claude-sonnet-4-6',
+    },
+  ],
+})
+```
+
+The parent agent can then call the auto-generated `subagent` tool with a `task` description and optional `agentType`.
+
+When you define a subagent, write its `description` and `instructions` to be clear and narrow. The `description` is what the parent model reads to decide _when_ to delegate, so state the single job the subagent is for and, by implication, what it's not for — "Reads files and gathers context without making changes" tells the parent to reach for it during exploration and to handle edits elsewhere. The `instructions` then keep the child agent inside that job. A subagent scoped to one task with a focused toolset stays predictable and is easier for the parent to route to; a broadly described subagent invites the parent to over-delegate and blurs the boundary between types. Pair the narrow scope with `allowedWorkspaceTools` so the subagent can only do what its description promises.
+
+For the full list of subagent configuration options, see [`Harness` reference](https://mastra.ai/reference/harness/harness-class).
+
+## Forked subagents
+
+A default subagent starts with a fresh context: it can't see the parent conversation, so you pass everything it needs in the `task` description. That's the right model for self-contained work, but it has two costs. The subagent has no access to what's already happened, and it builds a brand-new request prefix — a different system prompt and tool schemas — so it can't reuse the parent's prompt cache.
+
+**Forked subagents** solve both. Instead of a fresh agent, a fork clones the parent thread and runs the parent agent itself, so it sees the full conversation history and keeps the same system prompt and tool schemas as the parent. The identical prefix means the model's prompt cache still hits, which makes context-heavy delegation cheaper and faster.
+
+Use a fork when the subtask depends on the conversation so far — prior messages, earlier tool results, or the parent's tool environment — and you want to run it without paying to rebuild that context. Use a default subagent when the task is self-contained and benefits from a narrower toolset, a tighter system prompt, or a cheaper model.
+
+Enable forked mode per-type:
+
+```typescript
+const collaborator = {
+  id: 'collaborator',
+  name: 'Collaborator',
+  description: 'Continues the conversation in a fork.',
+  forked: true,
+}
+```
+
+Or per-invocation via the `subagent` tool's `forked` input parameter, which overrides the type's default.
+
+### Forked mode semantics
+
+Because a fork reuses the parent agent to keep the prompt prefix stable, the subagent's own definition is mostly set aside:
+
+- Memory must be configured on the Harness, since forking clones the parent thread. Without it, the fork call returns an error.
+- The fork runs with the parent agent's instructions, tools, and model. The subagent definition's own `instructions`, `tools`, and `defaultModelId` are ignored, and a per-invocation `modelId` is ignored too.
+- Only the subagent definition's `description` still matters — it's what the parent model reads to decide when to delegate.
+- Fork threads are tagged with `metadata.forkedSubagent === true` and hidden from `session.thread.list()` by default.
+- Recursive forks are blocked at runtime: the inherited `subagent` tool is disabled inside a fork to prevent infinite nesting.
+
+## Subagent model management
+
+Set a global or per-type subagent model at runtime:
+
+```typescript
+// Global subagent model
+await harness.setSubagentModelId({ modelId: 'anthropic/claude-sonnet-4-6' })
+
+// Per-type override
+await harness.setSubagentModelId({
+  modelId: 'anthropic/claude-haiku-4-5',
+  agentType: 'explore',
+})
+
+// Read current model
+const modelId = harness.getSubagentModelId({ agentType: 'explore' })
+```
+
+## Related
+
+- [Harness overview](https://mastra.ai/docs/harness/overview)
+- [Tool approvals and permissions](https://mastra.ai/docs/harness/tool-approvals)
+- [API reference](https://mastra.ai/reference/harness/harness-class)

package/.docs/docs/harness/threads-and-state.md

@@ -0,0 +1,139 @@
+# Threads and state
+
+Threads and state are how a Harness conversation survives beyond a single exchange. A **thread** is the persistent record of a conversation — its messages and metadata, saved to storage so a user can close the app and resume the same conversation later, or switch between several conversations. **State** is structured data attached to the conversation — values like model preferences, feature flags, or progress — that agents and your UI read and write as the conversation runs.
+
+The two work together: the thread is the message history, and state is the shared scratchpad alongside it. Both persist across mode switches, model changes, and restarts, so nothing is lost when a user switches from plan mode to build mode or reopens the app the next day.
+
+Thread _lifecycle_ transitions — create, switch, clone, delete — live on the Harness because they coordinate the shared thread lock and emit events. The active thread binding and thread/message _reads_ live on the [`Session`](https://mastra.ai/docs/harness/session) as `harness.session.thread`.
+
+## Threads
+
+A thread holds one conversation's full message history. The Harness binds the Session to one active thread at a time; messages you send and the agent's replies are appended to that thread and saved to storage. Threads let users resume a past conversation, keep several conversations side by side, or branch one into alternatives.
+
+### Creating and selecting threads
+
+On startup, call `selectOrCreateThread()` to resume the most recent thread or create a new one:
+
+```typescript
+await harness.init()
+const thread = await harness.selectOrCreateThread()
+```
+
+Create a thread explicitly with a title:
+
+```typescript
+const thread = await harness.createThread({ title: 'New conversation' })
+```
+
+### Switching threads
+
+Switch to an existing thread. The harness aborts any in-progress generation, acquires a lock on the new thread, and emits a `thread_changed` event:
+
+```typescript
+await harness.switchThread({ threadId: 'thread-abc123' })
+```
+
+### Listing threads
+
+List threads for the current resource. Forked subagent threads are hidden by default:
+
+```typescript
+const threads = await harness.session.thread.list()
+
+// Include all resources
+const allThreads = await harness.session.thread.list({ allResources: true })
+```
+
+### Cloning threads
+
+Clone a thread to create a branch of the conversation. The harness copies all messages and switches to the clone:
+
+```typescript
+const cloned = await harness.cloneThread({ title: 'Alternative approach' })
+```
+
+### Thread locking
+
+Pass a `threadLock` to the Harness constructor to prevent concurrent access from multiple processes. The lock is acquired before any thread operation and released on switch or delete:
+
+```typescript
+const harness = new Harness({
+  id: 'my-agent',
+  threadLock: {
+    acquire: async threadId => {
+      /* acquire lock or throw */
+    },
+    release: async threadId => {
+      /* release lock */
+    },
+  },
+})
+```
+
+## State
+
+Where a thread stores the conversation's messages, state stores structured values that describe the conversation but aren't messages — model preferences, feature flags, UI settings, or progress markers. Agents can read and update state during a run, and your UI can react to changes, so state is how the agent and the interface stay in sync on shared facts. You define its shape with a schema, and every update is validated against that schema before it's applied.
+
+### Defining a state schema
+
+Pass a `stateSchema` (Standard JSON Schema) to validate state and extract defaults:
+
+```typescript
+import { Agent } from '@mastra/core/agent'
+import { Harness } from '@mastra/core/harness'
+import { z } from 'zod'
+
+const agent = new Agent({
+  name: 'assistant',
+  instructions: 'Help the user manage a stateful session.',
+  model: 'openai/gpt-5.5',
+})
+
+const harness = new Harness({
+  id: 'stateful-agent',
+  agent,
+  modes: [{ id: 'default', name: 'Default', metadata: { default: true } }],
+  stateSchema: z.object({
+    currentModelId: z.string().optional(),
+    theme: z.enum(['light', 'dark']).default('dark'),
+  }),
+})
+```
+
+### Reading and writing state
+
+State is owned by the [`Session`](https://mastra.ai/docs/harness/session) as `harness.session.state`:
+
+```typescript
+// Read the current state snapshot
+const state = harness.session.state.get()
+
+// Update state — validates against schema and emits state_changed
+await harness.session.state.set({ theme: 'light' })
+```
+
+State changes emit a `state_changed` event with the new state and the set of changed keys.
+
+## Resource IDs
+
+Threads are scoped to a resource ID, which groups a conversation's threads by project, user, or workspace. Set it on the Harness constructor; it defaults to the harness `id` when omitted:
+
+```typescript
+const harness = new Harness({
+  id: 'my-agent',
+  resourceId: 'project-xyz',
+})
+```
+
+The resource ID is part of a conversation's identity, so you read it from the Session:
+
+```typescript
+const resourceId = harness.session.identity.getResourceId()
+```
+
+## Related
+
+- [Harness overview](https://mastra.ai/docs/harness/overview)
+- [Session](https://mastra.ai/docs/harness/session)
+- [Modes](https://mastra.ai/docs/harness/modes)
+- [API reference](https://mastra.ai/reference/harness/harness-class)