---
title: "Platform engineering · Ataris"
description: "Teams trace their agents with one CLI wherever they run them: laptops, CI, VMs, or the sandboxes they already use. Every run lands on the same timeline, so a failed run is debugged from one place."
canonical: "https://ataris.dev/solutions/platform-engineering"
last-updated: 2026-10-10
---
# Give every team one traced way to run agents.

Teams trace their agents with one CLI wherever they run them: laptops, CI, VMs, or the sandboxes they already use. Every run lands on the same timeline, so a failed run is debugged from one place.

## How teams roll it out

1. **Trace runs from a laptop or CI.** Teams put ataris in front of the agent command, in a terminal, a CI step, or a scheduled job. It needs no root, so it runs on locked-down runners too.
2. **Share guardrails.** Target a workspace policy at sessions by tag, such as team:infra, so the same rules apply to every agent that carries it.
3. **Debug from the timeline.** When a run fails, its session shows the state it ended in, the reason, and the context, decision, and command that broke it.

## What platform teams get

- **No tracing code to maintain.** Agents run unchanged through the CLI. There is no instrumentation to add and no agent to register.
- **Clear session states.** Each session runs until the agent exits, then ends as succeeded, failed, or stopped, with a reason when it fails.
- **Nothing new to host.** The CLI runs on the machines you already have, so there are no runners, images, or capacity limits to manage. Each run is billed as one traced session.
- **Runs grouped by tag.** Tag each job, such as name:test-fixer or team:infra, and filter and compare its runs over time in the dashboard. Repo and branch are tagged automatically.

## Trace a CI step

Install the CLI in the job and put ataris in front of the agent command. The run shows up tagged with its agent name.

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

# ATARIS_API_KEY comes from your CI secrets
ataris --agent test-fixer claude -p "Fix the failing test"
```

## Common questions

### Do teams have to change their agents?

No. Put ataris in front of the command they already run.

### Does it need root?

No. The CLI runs as an ordinary user on macOS and Linux.

### Can we pipe events into our own tools?

Yes. Stream a session's events live with the SDK, resume after a disconnect, or page through stored events with the REST API.

## Standardize how your agents run.

Book a demo and we'll map Ataris onto the agents your teams already run.

[Book a demo](https://ataris.dev/contact) · [Read the docs](https://ataris.dev/docs/quickstart.md)