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

# AppSignal CLI

> Query your AppSignal data from the terminal with CLI: Tail logs as they arrive, search incidents and close them out, and manage anomaly detection triggers, all without opening the web UI. It's a single binary built in Rust, so there's nothing else to install.

AppSignal CLI is built for two kinds of users: people and AI agents. By default every command prints human-readable output; pass `--output json` and it returns machine-readable JSON instead. In other words, the same tool you reach for during an incident can also feed structured data to a coding agent. It even bundles an [AppSignal agent skill](/cli/skill): a set of instructions that teaches an agent like Claude or Codex how to use the CLI. Install it with `appsignal-cli skill install`.

<Note>
  The CLI talks to the same AppSignal data as the app UI and [AppSignal MCP](/mcp-server). It's a gateway to data AppSignal already has. If your app isn't sending logs, `logs tail` won't show any.
</Note>

<h2 id="what-you-can-do">
  What you can do
</h2>

* **Logs:** tail log lines as they arrive, or search across a time range with AppSignal's [query syntax](/logging/query-syntax). Filter by severity or source, apply saved log views, and list an app's views and sources. Create and manage log-derived metrics and log-based triggers from your log data.
* **Incidents:** list exception, performance, and anomaly incidents, and search the exception and performance ones; open an incident's details; update its state, severity, notification frequency, or assignees; and add, edit, or delete its notes.
* **Traces:** list the performance samples and error traces behind an action or an incident, filter them by tag or deploy revision, and open one to read its [span tree](/cli/traces) down to a single span.
* **Triggers:** list, create, update, and archive anomaly detection triggers.
* **Dashboards:** list, create, and update your app's [dashboards](/cli/dashboards).
* **Apps:** list your applications, find an app by name, and inspect its users, notifiers, namespaces, dashboards, and deploy markers.
* **Project configuration:** create a [project-local config](/cli/configuration) so commands run in a repository default to the right organization.
* **Agent skill:** install the bundled AppSignal skill into your AI agent, update it, and check whether it's current.
* **Feedback:** [report](/cli/feedback) a missing command, a broken behavior, or a feature you need, without leaving the terminal.

<h2 id="quick-reference">
  Quick reference
</h2>

A few commands to get you started. For the full cheat sheet of every command and its arguments, see the [command reference](/cli/commands).

| Command | What it does |
| - | - |
| `appsignal-cli auth login` | Authenticate with AppSignal via OAuth |
| `appsignal-cli apps list` | List your applications |
| `appsignal-cli logs tail --app <APP>` | Tail log lines in real time |
| `appsignal-cli logs search --app <APP>` | Search log lines with a one-shot query |
| `appsignal-cli incidents list --app <APP>` | List an app's incidents |
| `appsignal-cli incidents show --number <NUMBER> --app <APP>` | Open one incident's details |
| `appsignal-cli triggers list --app <APP>` | List anomaly detection triggers |
| `appsignal-cli skill install` | Install the bundled AppSignal agent skill |

<h2 id="global-flags">
  Global flags
</h2>

These flags work on every command:

| Flag | Description |
| - | - |
| `--output <value>` (`-o`) | Render results as `human` (the default) or `json`. `--format` is a synonym. |
| `--help` (`-h`) | Show usage, subcommands, and options for any command (for example, `appsignal-cli logs tail --help`). |

You can pass `--output` (or `--format`) before or after the subcommand. Command results go to standard output in the format you choose; status messages always go to standard error, so a `--output json` stream stays valid JSON that you can pipe into another tool.

<h2 id="next-steps">
  Next steps
</h2>

To get started, [install the CLI and sign in](/cli/authentication). The CLI can't reach your data until it's connected to your AppSignal account.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.