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

# Claude Code and Cowork Agents

> How the people who use Claude Code and Cowork appear in Agent Inventory, and what Opal shows for each.

> [!NOTE]
>
> Agent Inventory is currently in limited beta. Contact Opal support to enable it for your organization.

Opal keeps a Claude agent for each person who uses Claude, and shows Claude Code and Cowork activity on that agent. This page explains how a person's Claude agent reaches [Agent Inventory](https://docs.opal.dev/docs/agent-inventory.md), what Opal reads to fill it in, and what you see.

## Requirements

Before you begin, you must:

* Be an Opal Admin.
* Connect your Anthropic organization, set up Claude Code or Cowork, or both. See [How a Claude agent reaches the inventory](#how-a-claude-agent-reaches-the-inventory).

## How a Claude agent reaches the inventory

| Route | What it creates | Where to set it up |
| - | - | - |
| Anthropic connection | An agent for everyone with Claude usage when **Sync agents daily** is on for the connection, or for each person you select from your Anthropic usage data. Also an agent for each API key and service account you import. | [Anthropic Setup](https://docs.opal.dev/docs/anthropic-agent-setup.md) |
| Claude Code or Cowork activity | A person's Claude agent, from their first call, when your organization has that turned on. Contact Opal support to turn it on. | [Claude Code Setup](https://docs.opal.dev/docs/tool-call-governance-claude-code.md) and [Cowork Setup](https://docs.opal.dev/docs/tool-call-governance-cowork.md) |

Both routes make the same kind of agent for a person. Its name is the person's name followed by **'s Claude**. Opal aims for one agent for each person:

* If a person already has a Claude agent, Opal uses it and doesn't make another.
* If activity made the agent first, a later sync takes it over. If the person already has another Claude agent, the sync keeps that one, retires the activity-made one, and moves its calls to the kept agent.
* Opal makes an agent from activity only for an active user in Opal, and it doesn't make one again after an admin deletes it.
* Opal makes a few agents for each batch of activity it receives, so a large rollout can take several batches before every person has one.

## What you see

Go to **Inventory** > **Agents** and select a person's Claude agent. The agent has these fields:

| Field | What it shows |
| - | - |
| Source | **Anthropic** |
| Owning Group | The person's own owner, which the agents list shows as **Owner**. If the person already belongs to an owner in Opal, Opal uses the first of those by name, which can be a shared group. |
| Tier | **Supervised** when Opal creates the agent. You can change it. API keys and service accounts you import start as **Unknown**. |
| Harness | **Claude Code** for an agent that Opal creates from activity. For an agent from a sync, the harness is the Claude product where Opal saw the person use connectors, such as **Claude Cowork**. If Opal saw several products, or none, the harness is **Claude**. A sync can change the harness when it takes over or replaces an activity-made agent. |

The agent's page also has:

* **A Claude Code activity tab.** It lists the person's calls from every runtime that reported, Cowork included. In the default **All** view, it also lists every call in your organization that Opal couldn't match to an agent. Choose **This agent** to see only the person's calls. See [Claude Code Setup](https://docs.opal.dev/docs/tool-call-governance-claude-code.md#what-opal-records) and [Cowork Setup](https://docs.opal.dev/docs/tool-call-governance-cowork.md#what-opal-records) for what each call holds.
* **An Effective access tab**, on a person's own Claude agent. It lists the MCP servers, plugins, skills, subagents, and permission rules in that person's Claude Code configuration, under **Can reach**, next to what the person **Has used** in the last 7 days. Opal gets the configuration from the Opal hook kit, so the **Can reach** side fills in for computers that run it.

## What Opal reads

| Source | What Opal reads |
| - | - |
| Anthropic connection | Your Anthropic users, workspaces, API keys, and service accounts, and the usage that shows which people use Claude and where they use connectors. What Opal can read depends on the keys you add. See [Anthropic Setup](https://docs.opal.dev/docs/anthropic-agent-setup.md). |
| Claude Code | Each tool call and who made it, and with the kit, the computer's Claude Code configuration. |
| Cowork | Each prompt, reply, and tool call, from Cowork's telemetry. |

## Limits

* Opal takes the person on a call from the email the computer reports, except for a call sent with the person's own sign-in token. Treat the person as reported, not proven.
* If a person has more than one Claude agent, Opal doesn't guess which one a call belongs to. The call shows under the email the computer reported, with an **unknown** tag, or as **Unknown agent**, in **Activity**.
* Opal can't make an agent for an email that doesn't belong to an active user in Opal.


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