Skip to main content
Managed agents are available on Enterprise. Signal and managed agents are currently included at no additional charge for Enterprise. See Pricing and usage.
Every managed agent starts the same way: Signal & Agents → + New Agent. From there you either pick a ready-made agent and adjust it, or start from scratch and write the task yourself.

​
Start from a ready-made agent

The gallery groups agents by what they are for. Picking one pre-fills its task prompt and tells you which controls still need setting. Every setting a ready-made agent pre-fills remains editable before launch.
A Security agent covering PII, secrets, and prompt-injection review is built but not yet in the gallery, along with Prompt Optimization and Eval / Quality agents. They appear once their access roles land.

​
Or start from scratch

Start from Scratch opens Agent Studio — the composer — with nothing pre-filled. You choose the harness, sandbox, project, skills, and task prompt yourself, then Run session or Setup as automation. Use it when none of the ready-made agents match the job. Every run is configured in Agent Studio. A ready-made agent fills it in through the guided setup below; Start from Scratch opens it empty.

​
Guided setup

Choosing a ready-made agent walks you through up to three steps instead of dropping you straight into Agent Studio. Steps you do not need are skipped — an agent that reads only Arize traces has nothing to connect, so it drops the first step entirely.
1

Connect

Connect the outside systems this agent needs — GitHub to clone a repo and open PRs, Dynatrace to pull metrics and logs. When a GitHub skill is connected, you set the repository here too, since a repo does nothing without it. Arize trace access is provisioned automatically and never appears here.
2

Configure

Bind the tracing project the agent reads, and choose whether it runs as a one-off session or a recurring automation. For an automation, name it and set the trigger.
3

Review & launch

Edit the task prompt, confirm the setup, and start it.
On the first run you may need to acknowledge that the harness can process project traces, your instructions, and connected repo or tool data.

​
Session or automation

Some agents support only one mode. Fix a bug in your repo is session-only, since it acts on a bug you describe. Triage a monitor alert and Recurring health check are automation-only, since each is defined by its trigger. Signal uses the same automation model, enabled per tracing project.

​
What you can customize

​
Save it as an agent config

An agent config is a saved bundle of harness, sandbox, optional AI provider, optional skills, and optional repo, so you configure it once instead of per run. Manage agent configs under More → Agent Configs, or create one inline while setting up an agent.
Two things to know about agent configs:
  • Automations require one. A one-off session can configure everything ad hoc; a recurring automation inherits its whole setup from an agent config.
  • Some are managed for you. Attaching a repo in Configure Signal creates a Signal-managed agent config behind the scenes. Those stay out of the general list.
You pick the project each time you launch, not on the agent config, so one config serves many projects and setting it up for a different project does not duplicate it.

​
Track what is running

Sessions and automations both land in Signal & Agents. Select Agents, then choose a view:
  • Grid view shows recent runs grouped by agent config and colored by status. Click a run to open it.
  • List view shows sessions and automations in a searchable table. On an automation row, select View automation details to inspect its configuration and manage future runs.
From a run you can read the live transcript, send follow-ups, jump to a PR the agent opened, view the agent’s own traces, reprovision a finished session to continue it, or archive it. Multiple sessions run in parallel. Opening an automation shows its trigger, prompt, agent config, recent runs, and any PRs it produced. Pause, resume, or delete it from there.

​
Edit a custom automation’s prompt

Edit prompt is available for custom automations when you have permission to manage them. It is not available for Signal or other issue-producing agents, whose prompts are managed by the platform.
  1. Open Signal & Agents, select Agents, and switch to List view.
  2. Find your custom automation and select View automation details on its row.
  3. In the automation panel, open the More actions menu (three dots) at the top right, next to the close button. Choose Edit prompt. Use the automation’s menu, not the separate menu inside an individual run.
  4. Update the Prompt field and select Save. The prompt cannot be empty.
Future runs use the updated instructions. Runs already in progress keep the prompt they started with.

​
Outputs

Code changes arrive as a pull request for you to review and merge. A managed agent does not deploy to your production environment, and is not a runtime for your customer-facing app.
  • Cost agent — The ready-made agent for spend
  • Signal — Ranked issues on a tracing project
  • Connect your harness — Credentials, skills, permissions, and boundaries
  • Arize Skills — A different thing: skills in your own local coding agent