Connect Jam to Goose
Give Goose governed access to Jam’s 15 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Jam to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Approve Jam in Runlayer
Add Jam from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Goose to Runlayer
Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches Jam’s 15 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 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
Use Jam from Goose
Jam’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
15 Jam tools in Goose
Runlayer policy decides which of these Goose 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.
Control
What Runlayer can see and stop in Goose
Some controls apply to every client at the gateway. Others depend on what Goose exposes to Runlayer.
Gateway policy (available)
Every Jam call from Goose passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Goose 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 Goose runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Goose’s model sees it.
Redact output in place (not available)
Goose cannot apply masking, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.
Frequently asked questions
Connect more