Skip to main content
Book a demo

Connect Pendo to Cline CLI

Give Cline CLI governed access to Pendo’s 54 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cline CLI setup guide

Set up

Add Pendo to Cline CLI in four steps

Admins approve the server once. Everyone in Cline CLI then gets it through the same governed connection.

  1. 1

    Approve Pendo in Runlayer

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

  2. 2

    Connect Cline CLI to Runlayer

    Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches Pendo’s 54 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI setup guide
  3. 3

    Sign in to Pendo

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

  4. 4

    Use Pendo from Cline CLI

    Pendo’s approved tools appear in Cline CLI. Every call is checked against policy and recorded.

Tools

54 Pendo tools in Cline CLI

Runlayer policy decides which of these Cline CLI users can call.

  • Account metadata schema

    Return the set of metadata fields available for accounts.

  • Acquisition trend

    Count new visitors or accounts per period - users whose first-ever interaction with the app (scope='app'), a specific page or feature (scope='page' or 'feature'), or a track event…

  • Agent analytics conversation analysis

    Lists and ranks individual AI agent conversations with per-conversation metrics.

  • Agent analytics issue analysis

    Returns issue diagnoses, flagged response tool/model usage, and user prompt content for the events of a specific detected issue cluster in AI Agent Analytics.

  • Agent analytics key metrics

    Returns key aggregate metrics for AI agent conversations with period-over-period comparison.

  • Agent analytics tracked issue analysis

    Deep-dives into a single tracked issue in AI Agent Analytics for a specific AI agent, surfacing the visitors and accounts, sampled issue explanations from detected issue clusters, the tools and…

  • Agent analytics tracked use case analysis

    Deep-dives into a single tracked use case in AI Agent Analytics for a specific AI agent, surfacing the visitors and accounts, the tools and models the agent invoked, sampled explanations, and a…

  • Aggregate entity usage

    Rank pages, features, or track events by aggregate usage over a date range, or measure a named set of them as one population.

See all 54 Pendo tools

Control

What Runlayer can see and stop in Cline CLI

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

  • Gateway policy (available)

    Every Pendo call from Cline CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cline CLI 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.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Cline CLI runs it.

  • Block output after it runs (not available)

    Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination