Connect Pendo to VS Code
Give VS Code governed access to Pendo’s 54 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Pendo to VS Code in four steps
Admins approve the server once. Everyone in VS Code then gets it through the same governed connection.
- 1
Approve Pendo in Runlayer
Add Pendo from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect VS Code to Runlayer
Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Pendo’s 54 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).
VS Code setup guide - 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
Use Pendo from VS Code
Pendo’s approved tools appear in VS Code. Every call is checked against policy and recorded.
Tools
54 Pendo tools in VS Code
Runlayer policy decides which of these VS Code 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.
Control
What Runlayer can see and stop in VS Code
Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.
Gateway policy (available)
Every Pendo call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, VS 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.
Stop a call before it runs (available)
Runlayer can deny a tool call before VS Code runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before VS Code’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.
Frequently asked questions
Connect more