---
title: "Quickstart · Ataris docs"
description: "Install the ataris CLI, trace an agent run where it already runs, and open its timeline. Every plan."
canonical: "https://ataris.dev/docs/quickstart"
last-updated: 2026-10-12
---
# Quickstart

Install the ataris CLI, trace an agent run where it already runs, and open its timeline. Every plan.

This guide installs the `ataris` CLI and traces an agent run where it already runs. You need an Ataris workspace; the CLI works on every plan.

## 1. Create an API key

In the Ataris dashboard, open **Settings → API keys** and create a key. Workspace keys start with `atk_`.

```bash
export ATARIS_API_KEY=atk_...
```

The CLI reads `ATARIS_API_KEY` from the environment.

## 2. Install the CLI

```bash title="macOS / Linux"
curl -fsSL https://ataris.dev/install | sh
export PATH="$HOME/.local/bin:$PATH"
```

```powershell title="Windows"
irm https://ataris.dev/install.ps1 | iex
```

The script installs the `ataris` binary to `~/.local/bin` (on Windows, to your user `Programs` folder and your `PATH`). Set `ATARIS_VERSION` to install a specific release. Check it with:

```bash
ataris --help
```

## 3. Trace an agent

Put `ataris` in front of the agent command you already run. It works with Claude Code, Codex, and Grok:

```bash
ataris claude -p "Fix the failing tests"
```

The CLI starts a session, runs the agent, and records what it does: each tool call and its result, the skills it loads, and the MCP calls it makes, plus every process, file, and network connection underneath, without root. It runs on macOS and Linux.

## 4. Open the timeline

In the dashboard, open **Sessions**. The run is there, tagged `source:cli`, as one ordered timeline.

## Next steps

- [Trace an agent CLI](/docs/guides/cli): options, tags, and how to run it in CI or your own sandbox.
- [Trace events](/docs/concepts/trace-events): the events on a timeline and how they're linked.
- [Policies](/docs/concepts/policies): on Pro and above, block tool calls and alert on credential reads.