Connect Omni to VS Code
Give VS Code governed access to Omni’s 25 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Omni to VS Code in four steps
Admins approve the server once. Everyone in VS Code then gets it through the same governed connection.
- 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
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, Omni’s 25 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).
VS Code setup guide - 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
Use Omni from VS Code
Omni’s approved tools appear in VS Code. Every call is checked against policy and recorded.
Tools
25 Omni tools in VS Code
Runlayer policy decides which of these VS Code 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.
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 Omni 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