Connect Linear to Codex
Give Codex governed access to Linear’s 82 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Linear to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Linear in Runlayer
Add Linear 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, Linear’s 82 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 Linear
Sign in the way Linear requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Linear from Codex
Linear’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
82 Linear tools in Codex
Runlayer policy decides which of these Codex users can call. 17 read data only.
Create attachment
Deprecated fallback for tiny files only.
Create attachment from upload
Link an already-uploaded Linear assetUrl to an existing issue as an attachment.
Create initiative label
Create a new Linear initiative label.
Create issue label
Create a new Linear issue label.
Delete attachment
Delete an attachment by ID
Delete comment
Delete a Linear comment.
Delete customer
Delete a customer in Linear
Delete customer need
Archive a customer need in Linear
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 Linear 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