> ## Documentation Index
> Fetch the complete documentation index at: https://arize-ax.mintlify.site/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent Presets

> Save reusable harness, sandbox, repo, and skill settings, then pick a preset in Agent Studio or attach one to an automation.

<Info>
  Agent Presets is available in closed Enterprise beta. Contact your Arize account team for access.
</Info>

An **agent preset** is a saved setup—harness, sandbox provider, optional GitHub repo, and optional skills—that you reuse across sessions and automations instead of configuring each run from scratch.

Manage presets under **More → Agent Presets** in the space sidebar. You can also create or edit presets inline from [Agent Studio](/ax/agents/agent-studio) or when building an automation.

## What a preset includes

| Field           | Purpose                                                                                                                                                          |
| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Harness**     | Agent runtime inside the sandbox. **Claude Code** is available today; additional harnesses are on the roadmap.                                                   |
| **Sandbox**     | Compute environment. Choose **Arize** (Arize-managed Kubernetes) or a connected **Claude Managed Agent** provider. Daytona and Vercel sandboxes are coming soon. |
| **Skills**      | Optional—[GitHub, Arize, Datadog, custom](/ax/agents/skills-and-permissions)                                                                                     |
| **GitHub repo** | Shown when a GitHub skill is attached                                                                                                                            |

<Note>
  **Automations require a preset.** One-off sessions can use **None** in Agent Studio to configure harness, sandbox, and skills manually for that run only.
</Note>

<Note>
  **Claude Managed Agent** presets support interactive sessions only. Automations must use the **Arize** sandbox provider.
</Note>

## Signal, our built-in agent

**Signal** is a long-running agent that continuously scans a tracing project's traces and surfaces ranked issues. It ships with the platform and runs on a managed preset, so you enable it from the **Signal** tab on a project rather than picking or configuring it in Agent Studio. It runs with trace read access only. By default, Signal writes an investigation for each issue; to have it open a pull request with the proposed fix, use **Attach Repo** on the [Signal](/ax/observe/signal#attach-a-repo-for-fix-prs) settings and add your repository.

When you attach a repo to Signal on a project, Arize may create a **Signal-managed** preset for that flow. These presets stay hidden from the general preset list but remain available to Signal.

## Create a preset

<Frame>
  <video
    src="https://storage.googleapis.com/arize-assets/doc-images/managed%20agents/managed-agents-create-preset.mp4"
    alt="New Agent Preset form showing harness and sandbox selection with optional skills and GitHub repo fields"
    width="100%"
    height="100%"
    style={{
  display: 'block',
  objectFit: 'fill',
  backgroundColor: 'transparent',
}}
    controls
    autoPlay
    muted
    loop
  />
</Frame>

<Steps>
  <Step title="Open Agent Presets">
    Go to **More → Agent Presets** and click **New Preset**, or choose **New Agent Preset** from the preset menu in Agent Studio.
  </Step>

  <Step title="Choose harness and sandbox">
    Select **Claude Code** and either **Arize** or a **Claude Managed Agent** (agent + environment).
  </Step>

  <Step title="Attach skills (optional)">
    Add [skills](/ax/agents/skills-and-permissions) for GitHub, Arize API access beyond trace read, Datadog, or custom install sources.
  </Step>

  <Step title="Set repo (optional)">
    When a GitHub skill is attached, enter the repository the worker should clone.
  </Step>

  <Step title="Save">
    The preset appears in Agent Studio and can be bound to new automations.
  </Step>
</Steps>

## Use a preset

* **Agent Studio** — Pick a preset from the composer, or **None** for a one-off configuration.
* **Automations** — Every automation inherits harness, sandbox, skills, and repo from its preset.
* **Signal with repo** — Attach a repo on the Signal tab; Arize wires the matching preset behind the scenes.

## Related docs

* [Agent Studio](/ax/agents/agent-studio) — Start a session or automation from a preset
* [Skills and permissions](/ax/agents/skills-and-permissions) — Configure integrations and RBAC
* [How agents work](/ax/agents/how-agents-work) — What workers can access in a run