Connect DeepWiki to Codex
Give Codex governed access to DeepWiki’s 4 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add DeepWiki to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve DeepWiki in Runlayer
Add DeepWiki from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Codex to Runlayer
Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, DeepWiki’s 4 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).
Codex setup guide - 3
Sign in to DeepWiki
Sign in the way DeepWiki requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use DeepWiki from Codex
DeepWiki’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
4 DeepWiki tools in Codex
Runlayer policy decides which of these Codex users can call.
Ask question
Ask any question about a GitHub repository and get an AI-powered, context-grounded response.
Ask wiki question
Ask any question about a GitHub repository's codebase and get an AI-powered answer grounded in its DeepWiki.
Read wiki contents
View documentation about a GitHub repository.
Read wiki structure
Get a list of documentation topics for a GitHub repository.
Control
What Runlayer can see and stop in Codex
Some controls apply to every client at the gateway. Others depend on what Codex exposes to Runlayer.
Gateway policy (available)
Every DeepWiki call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Codex 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 or permission request before Codex runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Codex’s model sees it.
Redact output in place (not available)
Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
Frequently asked questions
Connect more