Connect Guru to Warp
Give Warp governed access to Guru’s 6 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Guru to Warp in four steps
Admins approve the server once. Everyone in Warp then gets it through the same governed connection.
- 1
Approve Guru in Runlayer
Add Guru from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Warp to Runlayer
Users add the Runlayer Plugin to Warp by following Runlayer’s setup guide. Warp reaches Guru’s 6 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Warp setup guide - 3
Sign in to Guru
Each user signs in to Guru with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Guru from Warp
Guru’s approved tools appear in Warp. Every call is checked against policy and recorded.
Tools
6 Guru tools in Warp
Runlayer policy decides which of these Warp users can call. 4 read data only and 1 can change or delete data.
Ask knowledge agent
Generate direct answers to questions using the knowledge base.
Create a draft of content
Create a Draft of a Card in Guru.
Search documents
Find and retrieve specific documents, sources or cards.
Update card content
Update the content of an existing card.
List knowledge agents
Get available knowledge agents and their IDs.
Get Card content by ID
Get full card content in original HTML format by card ID
Control
What Runlayer can see and stop in Warp
Some controls apply to every client at the gateway. Others depend on what Warp exposes to Runlayer.
Gateway policy (available)
Every Guru call from Warp passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Warp as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Warp yet, so control happens at the gateway.
Frequently asked questions
Connect more