Skip to main content

Connect Omni to Zed

Give Zed governed access to Omni’s 25 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Omni to Zed in four steps

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

  1. 1

    Add Omni to Runlayer

    Omni isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Zed to Runlayer

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

    Zed setup guide
  3. 3

    Sign in to Omni

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

  4. 4

    Use Omni from Zed

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

Tools

25 Omni tools in Zed

Runlayer policy decides which of these Zed users can call.

  • Ask Omni

    Starts the full Omni AI agent on an open-ended or multi-step analytical question and returns immediately with a 'jobId' — it does NOT wait for or return the answer, which is retrieved separately once…

  • Cancel job

    Stops a job started by askOmni.

  • Check dashboard download

    Polls a dashboard download started by startDashboardDownload.

  • Check status

    Checks on a job started by askOmni and returns quickly.

  • Fetch dashboard download

    Returns the png a completed dashboard download produced — the job from startDashboardDownload once checkDashboardDownload reports it "complete" — as an image you can look at, after a text block with…

  • Get app

    Alpha — the app content shape may change without a deprecation cycle.

  • Get app draft

    Alpha — the app content shape may change without a deprecation cycle.

  • Get data

    Gets data by generating and executing a query from natural language.

See all 25 Omni tools

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 Omni 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