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

# Manage the AI ROI Agent

> Choose which organizations and tools the agent records, turn prompt labels on or off, and revoke machines.

Admins manage the agent in **Settings → Integrations → AI ROI Agent**. The card shows how many machines are signed in.

> [!NOTE]
>
> Managing the agent needs nOps administrator access and the **Inform + Operate** plan, like [OpenTelemetry](https://help.nops.io/telemetry/opentelemetry.md).

The card has four tabs:

| Tab | Use it to |
| - | - |
| [Install](#install) | Copy the install command to share with developers. |
| [Machines](#machines) | See every signed-in machine and revoke one. |
| [Policy](#policy) | Choose where and what the agent records. |
| [What's collected](#whats-collected) | See exactly what the agent sends, as developers see it. |

## Roll out in four steps

**1. Set the policy**

Add your GitHub organizations, GitLab groups and Bitbucket workspaces on the **Policy** tab. Until you do, the agent installs but records nothing.

**2. Share the install command**

Send developers `npx @nops-io/clara` and a link to [Install the AI ROI Agent](https://help.nops.io/ai-roi/agent/install.md).

**3. Watch machines sign in**

Each machine appears on the **Machines** tab as soon as it is approved. The AI ROI [Setup](https://help.nops.io/ai-roi/setup.md) tab counts them too.

**4. Check the numbers**

Within a day, AI cost per PR on the AI ROI page turns from estimates (`~$42`) into exact figures for developers with the agent.

## Install

Shows the install command each developer runs:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
npx @nops-io/clara
```

A browser opens, the developer signs in with their nOps login and approves the machine. Each machine gets its own key. There is no shared key to distribute or rotate.

## Machines

One row per machine: the developer's email, the machine's name, and when it was last seen.

**To revoke a machine**, click **Revoke** on its row and confirm. The machine stops sending data within a minute and can no longer fetch policy. To use the agent on that machine again, the developer runs the install command and approves it again.

Machines also stop working on their own when the developer leaves your organization in nOps, even if nobody revokes them.

When a developer runs `clara uninstall`, their machine is revoked automatically and shows as **Revoked**.

## Policy

The policy applies to every machine in your organization. Machines pick up changes within five minutes. Click **Save policy** after any change.

### Allowed organizations

The agent records work only in repositories that belong to these. **Nothing is recorded until you add one.**

Separate entries with commas:

| Host | Entry | Example |
| - | - | - |
| GitHub | The organization name | `acme` |
| GitLab | `gitlab.com/` and the top-level group | `gitlab.com/acme` |
| Bitbucket Cloud | `bitbucket.org/` and the workspace | `bitbucket.org/acme` |

### AI tools

Sessions in the tools turned on here are recorded: **Claude Code**, **Cursor**, **Codex**, **GitHub Copilot**.

### Other activity

Work around the AI tools that ties sessions to what shipped:

| Toggle | Records |
| - | - |
| **Git commits** | Repository, branch, commit ID, lines changed and AI-written lines for each commit. Needed to link sessions to PRs. |
| **Shell commands** | The command name and first subcommand (`npm test`), duration and exit code. Never arguments. |
| **Editor activity** | File kinds, languages and line counts of edits. Never file names or contents. |

> [!WARNING]
>
> Turning **Git commits** off stops sessions from linking to PRs, so AI cost per PR falls back to estimates.

### Prompt labels

**Label prompts on each machine**: a small model on the machine sorts each prompt into a work type, like Build or Fix. Only the label is sent, never the prompt.

Turn it off and no model is downloaded or run, and AI spend that never reached a merged PR stays **Not categorized**.

## What's collected

The full list of what the agent sends and what stays on the machine, the same list developers see before they approve a machine and in `clara status`. See [What the agent sends and keeps](https://help.nops.io/ai-roi/agent/privacy.md).

## Deploying at scale

Every developer needs to sign in once with their nOps login, so each machine gets its own key and each developer gives their own consent. There is no organization-wide key. If you install the agent with device management software, developers still run `npx @nops-io/clara` once to sign in.

To keep the agent from updating itself on a machine, run `clara update --auto off` on it, or set `CLARA_AUTO_UPDATE=0` in the environment of the agent's service. See [Updates](https://help.nops.io/ai-roi/agent/commands.md#updates).

## Related

* [Install the AI ROI Agent](https://help.nops.io/ai-roi/agent/install.md)
* [Who sees what](https://help.nops.io/ai-roi/access.md)


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