Skip to main content
Signal is the scheduled investigation agent on a tracing project. It reviews recent traces, groups recurring failures into ranked issues, and writes an investigation for each. The ag signal commands enable or pause Signal on a project, show its status, and list or read its issues. To run a sweep immediately, see Automations. ag signal and ag signals are the same command. project and projects, and issue and issues, are also interchangeable. Two IDs appear throughout:
  • <project-id> is the project’s relay ID, from ag signal project list or the project URL.
  • <issue-id> is the issue’s relay ID, from the id column of ag signal issue list.

ag signal

With no further arguments, ag signal opens the interactive project picker. In the list, press / to search, r to refresh, enter to open a project’s issues, and d to enable or pause Signal after a confirmation.

ag signal project list

List projects in a space with their Signal state. By default only projects with Signal enabled are shown.
Examples:

ag signal project show

Print a status card for one project: Signal state, preset, cadence, last and next run, extra context, issue counts by entity, and the activity window.
Examples:

ag signal project create

Enable Signal on a project. Arize provisions the built-in Signal preset and a scoped service key for the project. The command prints the consent text and asks for confirmation unless you pass --yes.
Enabling Signal means an automated agent runs on a schedule to review the project’s traces, surface ranked issues, and link evidence. Runs use Claude Code, and trace data and investigation output may be processed by Anthropic as part of each sweep.
Examples:

ag signal project delete

Pause Signal on a project. Scheduled runs stop and the automation’s service key is revoked, but the automation and its issues are kept. Run ag signal project create again to re-enable it.

ag signal issue list

List the issues Signal has found on a project. The default look-back is 30 days. Issues are deduplicated across runs, so one row can span many sweeps.
JSON output includes the Markdown investigation body and the matching trace IDs for every issue. Examples:

ag signal issue show

Print one issue: its header (ID, key, status, severity, entity, tags, match count, first and last seen, trace IDs) followed by the full Markdown investigation. No time window is needed.
Examples:

Recipes

Enable Signal on a project and read what it found

Run a sweep without waiting for the schedule