> ## 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. # Signal > Enable Signal on a project, browse and inspect Signal issues, and trigger a sweep from the terminal with the ag CLI [Signal](/docs/ax/observe/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](/docs/api-clients/ag/automations). `ag signal` and `ag signals` are the same command. `project` and `projects`, and `issue` and `issues`, are also interchangeable. Two IDs appear throughout: * `` is the project's relay ID, from `ag signal project list` or the project URL. * `` 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. ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} ag signal [--space ] ``` ## `ag signal project list` List projects in a space with their Signal state. By default only projects with Signal enabled are shown. ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} ag signal project list [--space ] [--search ] [--all] [--limit ] [--columns ] [--output ] ``` | Option | Description | | - | - | | `--space` | Space ID (falls back to the saved context) | | `--search` | Filter projects by name, server-side | | `--all` | Include projects where Signal is paused or not yet configured | | `--limit` | Maximum projects to return (default and server cap: 50) | | `--columns` | Comma-separated columns for text output (default: `signal,name,id`). Available: `signal`, `#`, `name`, `id` | **Examples:** ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} ag signal project list ag signal project list --all ag signal project list --search checkout --columns signal,name,id ``` ## `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. ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} ag signal project show [--since ] [--start ] [--end ] [--output ] ``` | Option | Description | | - | - | | `--since` | Look-back window for the issues-by-entity breakdown, such as `24h`, `7d`, or `30d` (default: `30d`). Ignored when `--start` is set. | | `--start` | Inclusive lower bound of the window (RFC 3339). Overrides `--since`. | | `--end` | Exclusive upper bound of the window (RFC 3339). Defaults to now. | **Examples:** ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} ag signal project show ag signal project show --since 7d ``` ## `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`. ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} ag signal project create [--yes] ``` | Option | Description | | - | - | | `--yes`, `-y` | Skip the confirmation prompt | > [!NOTE] > > 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:** ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} ag signal project create ag signal project create -y # in scripts ``` ## `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. ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} ag signal project delete [--yes] ``` | Option | Description | | - | - | | `--yes`, `-y` | Skip the confirmation prompt | ## `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. ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} ag signal issue list [--since ] [--start ] [--end ] [--status ] [--severity ] [--limit ] [--columns ] [--output ] ``` | Option | Description | | - | - | | `--since` | Look-back window on last-seen time, such as `24h`, `7d`, or `30d` (default: `30d`). Ignored when `--start` is set. | | `--start` | Inclusive lower bound on last-seen time (RFC 3339). Overrides `--since`. | | `--end` | Exclusive upper bound on last-seen time (RFC 3339). Defaults to now. | | `--status` | Filter by status: `open`, `resolved`, or `ignored`. Applied after the fetch. | | `--severity` | Filter by severity: `low`, `medium`, `high`, or `critical`. Applied after the fetch. | | `--limit` | Maximum issues to return (default: 100, server cap: 500) | | `--columns` | Comma-separated columns for text output (default: `id,severity,status,last_seen,title`). Available: `id`, `#`, `issue_key`, `severity`, `status`, `entity`, `title`, `tags`, `matches`, `first_seen`, `last_seen` | JSON output includes the Markdown investigation body and the matching trace IDs for every issue. **Examples:** ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} ag signal issue list ag signal issue list --since 7d --status open --severity high ag signal issue list --start 2026-06-01T00:00:00Z --end 2026-06-29T00:00:00Z ag signal issue list --columns id,severity,status,last_seen,matches,title ag signal issue list --output json ``` ## `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. ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} ag signal issue show [--output ] ``` **Examples:** ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} ag signal issue show ag signal issue show --output json ``` ## Recipes ### Enable Signal on a project and read what it found ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} ag context show ag signal project list --all --search ag signal project create ag signal project show ag signal issue list --status open --since 7d ag signal issue show ``` ### Run a sweep without waiting for the schedule ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} ag automation list # the Signal sweep has signal = yes ag automation trigger ag session events --follow ``` ## Related docs * [Signal](/docs/ax/observe/signal) — What Signal is, plan limits, and configuring it in the UI * [Enable Signal](/docs/ax/get-started/get-started-managed-agent) — Get Started walkthrough * [Managed agents and Signal via GraphQL](/docs/ax/graphql-reference/guides/managed-agents-and-signal) — The same operations from your own code