Skip to main content
Book a demo

Connect Jam to Claude Code

Give Claude Code governed access to Jam’s 15 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude Code setup guide

Set up

Add Jam to Claude Code in four steps

Admins approve the server once. Everyone in Claude Code then gets it through the same governed connection.

  1. 1

    Approve Jam in Runlayer

    Add Jam from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Claude Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Claude Code, and an Anthropic org install also reaches Claude Code. With direct tool listing turned on for your deployment, Jam’s 15 tools show up in Claude Code’s own tool list (supported Claude Code versions).

    Claude Code setup guide
  3. 3

    Sign in to Jam

    Sign in the way Jam requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Jam from Claude Code

    Jam’s approved tools appear in Claude Code. Every call is checked against policy and recorded.

Tools

15 Jam tools in Claude Code

Runlayer policy decides which of these Claude Code users can call. 13 read data only.

  • Get Jam bug report details and metadata

    Retrieve comprehensive metadata and details for a specific Jam bug report.

  • Get network activity and HTTP request logs

    Extract network activity logs captured during the Jam session.

  • Get browser console output and javascript logs

    Retrieve browser console output captured during the Jam session.

  • Get user interaction timeline and events

    Access the complete timeline of user interactions captured in the Jam.

  • Get custom Jam metadata

    Retrieve custom metadata set via the jam.metadata() SDK.

  • Get visual screenshots and image attachments

    Retrieve visual screenshots and image attachments from screenshot-type Jams.

  • Analyze video recording

    Extract user intents from a Jam recording.

  • Get video transcript

    Retrieve the speech transcript (captions) from a video Jam recording in WebVTT format with timestamps.

See all 15 Jam tools

Control

What Runlayer can see and stop in Claude Code

Some controls apply to every client at the gateway. Others depend on what Claude Code exposes to Runlayer.

  • Gateway policy (available)

    Every Jam call from Claude Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Claude Code as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude Code prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • OTLP telemetry (available)

    Claude Code can export OpenTelemetry logs to Runlayer for observe-only session reconstruction.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Claude Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Claude Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in Claude Code and pass the rest through.

In Claude Code

  • When a tool fails, Runlayer records the error but cannot hide it.

Frequently asked questions

Connect more

Find another combination