Skip to main content
Agent Presets is available in closed Enterprise beta. Contact your Arize account team for access.
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 or when building an automation.

What a preset includes

Automations require a preset. One-off sessions can use None in Agent Studio to configure harness, sandbox, and skills manually for that run only.
Claude Managed Agent presets support interactive sessions only. Automations must use the Arize sandbox provider.

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 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

1

Open Agent Presets

Go to More → Agent Presets and click New Preset, or choose New Agent Preset from the preset menu in Agent Studio.
2

Choose harness and sandbox

Select Claude Code and either Arize or a Claude Managed Agent (agent + environment).
3

Attach skills (optional)

Add skills for GitHub, Arize API access beyond trace read, Datadog, or custom install sources.
4

Set repo (optional)

When a GitHub skill is attached, enter the repository the worker should clone.
5

Save

The preset appears in Agent Studio and can be bound to new automations.

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.