Skip to main content
Book a demo

Connect Lattice to Claude Code

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

Book a demo Claude Code setup guide

Set up

Add Lattice 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 Lattice in Runlayer

    Add Lattice 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, Lattice’s 22 tools show up in Claude Code’s own tool list (supported Claude Code versions).

    Claude Code setup guide
  3. 3

    Sign in to Lattice

    Each user signs in to Lattice with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Lattice from Claude Code

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

Tools

22 Lattice tools in Claude Code

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

  • Find ancestors

    Find ancestors.

  • Find employees

    Searches for employees in the user's company by name, work email, and/or department.

  • Find feedback

    Retrieves feedback items the user has visibility into.

  • Find one on ones

    Find one on ones.

  • Find reports

    Find reports.

  • Find reviews

    Retrieves reviews the user is permitted to see, filterable by who the review is about, who wrote it, the cycle, direction, submission/sharing status, and date range.

  • Get current update draft

    Returns the user's current-period update draft, with the questions on the form, any answers already saved, the period bounds, and the cadence.

  • Get draft reviews

    Retrieves the open performance review drafts the user is currently authoring.

See all 22 Lattice 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 Lattice 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