Skip to main content
Book a demo

Connect Slack to Codex

Give Codex governed access to Slack’s 37 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Codex setup guide

Set up

Add Slack to Codex in four steps

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

  1. 1

    Approve Slack in Runlayer

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

  2. 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, Slack’s 37 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).

    Codex setup guide
  3. 3

    Sign in to Slack

    Each user signs in to Slack with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Slack from Codex

    Slack’s approved tools appear in Codex. Every call is checked against policy and recorded.

Tools

37 Slack tools in Codex

Runlayer policy decides which of these Codex users can call. 5 read data only.

  • Add list record

    Adds a new record (row) to a Slack list.

  • Add reaction

    Adds a reaction (emoji) to a Slack message.

  • Complete file upload

    Finalizes a file upload started with slack_get_file_upload_url, using the file_id from that call.

  • Create canvas

    Creates a Slack Canvas document from Canvas-flavored Markdown content.

  • Create conversation

    Create a channel, DM, or group DM.

  • Create list

    Creates a new Slack List with optional columns and a description.

  • Get file upload URL

    Generates a signed upload URL for a file, plus a file ID.

  • Get reactions

    Retrieves all reactions (emoji) on a specific Slack message.

See all 37 Slack tools

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

Find another combination