Skip to main content

Connect pg-aiguide to Zed

Give Zed governed access to pg-aiguide through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add pg-aiguide to Zed in four steps

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

  1. 1

    Approve pg-aiguide in Runlayer

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

  2. 2

    Connect Zed to Runlayer

    Users add the Runlayer Plugin to Zed by following Runlayer’s setup guide. Zed reaches pg-aiguide’s tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Zed setup guide
  3. 3

    Sign in to pg-aiguide

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

  4. 4

    Use pg-aiguide from Zed

    pg-aiguide’s approved tools appear in Zed. Every call is checked against policy and recorded.

Tools

pg-aiguide tools in Zed

pg-aiguide reports its tools when your organization connects it, so the list depends on your deployment.

Control

What Runlayer can see and stop in Zed

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

  • Gateway policy (available)

    Every pg-aiguide call from Zed passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Zed as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for Zed yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination