A/B — monitoring & governance

Monitor Claude Cowork Activity: Session Visibility for Admins

As Claude Cowork rolls out across a team, the first question most admins and team leads ask is simple: what is everyone actually doing with it? Not to surveil people — but to understand adoption, catch risky patterns, support new users, and be able to answer questions when they come up.

The honest answer in 2026 is that the official tooling gives you usage visibility but not session visibility. This page lays out exactly what you can see today, where the limits are, and how to get the full picture if you need it.

What you can see with native tools

Admin dashboard (Team & Enterprise). Anthropic's admin console shows Cowork adoption: how many sessions, daily/weekly/monthly active users, who has it enabled. This is the right tool for answering "is Cowork being adopted?" and "who's using it?" — but it stops at the metadata. It does not show the contents of sessions.

OpenTelemetry. Claude's Agent SDK emits OTel events you can route to your own collector (SigNoz, Grafana, Datadog, etc.): token usage, estimated cost, tool activity, errors, broken down by user, model, and skill. This is genuinely useful for cost governance and spotting anomalies. Its limit: it's aggregate telemetry, not a reviewable transcript. You can see that a session cost $0.40 and used four tools — not what it actually did.

Local files. Each Cowork (and Claude Code) session is stored locally on the user's machine. That means the detail exists, but it's scattered across endpoints, not centralized, and not something you can query across the team.

Where the native tools fall short

Put together, the native stack tells you Cowork is being used, by whom, and what it costs. What it can't tell you:

• What happened inside a session — the prompts, responses, tool and MCP calls, and which skills ran.
• Whether the output was any good — there's no review or QA layer.
• A centralized, queryable record across everyone, retained on your terms.

For a lot of teams, usage metrics are enough. But if you're a forward-deployed engineer or agency shipping Cowork implementations to clients, or an admin with governance responsibilities, you usually need to see the work itself — to debug a bad result, prove a deliverable, onboard someone by example, or review quality.

Full session visibility with Argus

Argus adds the layer the native tools don't: session-level visibility you control. A lightweight plugin instruments your Cowork environment and captures each session as a structured, replayable record — every turn, every tool and MCP call, every skill invocation — into your own workspace, where you can:

• Replay any session step by step, instead of guessing from cost metrics.
• Review and rate the quality of what skills and connectors produced.
• Search and filter across sessions, projects, and people.
• Keep it private and governed — encrypted, workspace-scoped, visible only to invited members, with automatic redaction and per-session opt-out so sensitive work stays out.

It's the difference between "Cowork was used 142 times this week" and "here's exactly what each of those sessions did, and how good it was."

FAQ

Can I see what my team is doing inside Claude Cowork without an audit log?

The admin dashboard shows usage metrics — session counts, active users — but not what happened inside any session. For real visibility you need either OpenTelemetry (cost/latency, no content) or a capture plugin that records the session itself.

What's the difference between OpenTelemetry and a session capture?

OpenTelemetry gives you cost, latency, and counts: the quantities of what happened. A session capture gives you prompts, tool calls, assistant responses, and version hashes: the qualities. You need both to actually understand a Claude Cowork rollout.

Is monitoring Claude Cowork sessions a privacy violation?

It depends on how you set it up and how you tell your users. Argus defaults to per-workspace storage, supports redaction, and gives users a /private slash command that opts a session out and deletes anything already shipped. Tell your team what's captured — the disclosure is on you.

How quickly does a captured Cowork session appear in a dashboard?

With Argus, within seconds of session end. The plugin streams events as hooks fire, and the dashboard reads from a single Supabase backend — no batching, no delayed pipeline.

Can I monitor Claude Cowork without installing anything on user machines?

You can monitor cost server-side via OTel routed to your collector. You cannot monitor content without an in-VM capture, because the VM is the only place where sessions exist.