Connect Pigment to Claude Cowork
Give Claude Cowork governed access to Pigment’s 101 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Pigment to Claude Cowork in four steps
Admins approve the server once. Everyone in Claude Cowork then gets it through the same governed connection.
- 1
Approve Pigment in Runlayer
Add Pigment from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Claude Cowork to Runlayer
Claude Cowork gets connector tools through the Runlayer Plugin. With direct tool listing turned on for your deployment, Pigment’s 101 tools show up in Claude Cowork’s own tool list.
Claude Cowork setup guide - 3
Sign in to Pigment
Sign in the way Pigment requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Pigment from Claude Cowork
Pigment’s approved tools appear in Claude Cowork. Every call is checked against policy and recorded.
Tools
101 Pigment tools in Claude Cowork
Runlayer policy decides which of these Claude Cowork users can call.
Add list items
Add one or more new items (rows) to a dimension/list with their property values in a single operation.
Batch share blocks
Share multiple lists and metrics in a single operation, making them visible and usable across applications within the organization.
Calendar add time dimension
Add a new time dimension to existing Application calendar.
Create calendar
Creates a new gregorian calendar in the Pigment application.
Calendar expand
Expands or shrinks a calendar's date range.
Get calendar
Retrieves detailed configuration of a specific calendar.
Calendar remove time dimension
Remove a time dimension from the Application's calendar.
Clear widget preview
Removes the Draft View preview from a single Board widget for the current user, so the widget shows its saved View again.
Control
What Runlayer can see and stop in Claude Cowork
Some controls apply to every client at the gateway. Others depend on what Claude Cowork exposes to Runlayer.
Gateway policy (available)
Every Pigment call from Claude Cowork passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude Cowork as the client, the tool, and the policy and scanner decisions.
Anthropic inference hooks (available)
Anthropic Inference hooks let Runlayer check Claude Cowork prompts before inference.
OTLP telemetry (available)
Claude Cowork can send supported OpenTelemetry events to Runlayer for observe-only session visibility.
Stop a call before it runs (available)
Runlayer can reject a Claude Cowork prompt before Anthropic runs it, which stops the whole request rather than one tool call.
Block output after it runs (available)
Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.
Redact output in place (not available)
Runlayer cannot mask content in Claude Cowork. The gateway still applies policy to the call.
In Claude Cowork
- Cowork session data sent over OpenTelemetry is for monitoring only and cannot stop anything.
Frequently asked questions
Connect more