A terminal-style Codex panel triggered from Slack, alongside an autonomous assistant agent acting on messages on its own

How to Connect Codex to Slack (and What It Can't Do)

Yes — OpenAI Codex has an official Slack integration, but it does a specific thing: it lets developers kick off coding tasks from a Slack channel. You mention @Codex with a prompt, it spins up a cloud task against your connected GitHub repo, and replies with a link to the result. It’s genuinely useful — for engineering teams. What it is not is an assistant that manages Slack for you: it doesn’t triage messages, route requests, or follow up on threads as part of your day-to-day ops. And like every Codex integration, standing it up is a developer setup, not a toggle a non-technical person flips.

Here’s what the Codex Slack integration does, how to turn it on, where the limits are, and what to use if you want Slack work handled by an assistant instead of a coding agent.


What the Codex Slack integration does

Codex in Slack is part of OpenAI’s push to make its coding agent reachable from where developers already work. Mention @Codex in a channel or thread and it will:

  • Gather context from the thread — it reads the surrounding messages, so you often don’t have to restate the problem.
  • Kick off a cloud coding task — it picks the right environment and runs the task in Codex Cloud.
  • Reply with a link to the result — where you can merge its changes, keep iterating, or pull the task down to your machine.

The intended job is clear from the OpenAI docs: triage a bug from a channel, start a fix, and get a PR — without leaving Slack. For a dev team, that removes real friction.


How to set it up

Setup is a developer task with prerequisites:

  1. A Plus, Pro, Business, Edu, or Enterprise plan.
  2. A connected GitHub account and at least one configured environment.
  3. Install the Codex Slack app for your workspace from Codex settings — a Slack admin may need to approve it.
  4. Mention @Codex in a channel with your prompt.

If you don’t have a repo and an environment, there’s nothing for it to do — the integration assumes you’re driving software work.


The limits that actually matter

The Slack integration is built for one persona and one job. Three limits define it:

  • It’s a coding-task launcher, not a Slack manager. It exists to start Codex tasks against your codebase. It won’t watch #support for customer questions, route a request to the right person, or send a follow-up — those aren’t things it does.
  • It assumes a developer setup. GitHub repo, environments, plan tiers, admin-approved app install. This is plumbing for engineers, not a five-minute connect for an exec or EA.
  • Codex is a coding agent at its core. Even with computer-use and 90+ plugins, its native surface is code, PRs, terminals, and environments. Pointing it at general inbox-and-calendar ops is using a build tool for a job it wasn’t shaped for.

So Codex-in-Slack is great for “start a fix from this bug thread” and not built for “watch our channels and handle what comes in.”


If you want Slack work handled by an assistant: Carly

The moment you want Slack handled — messages flagged and acted on the instant they arrive, requests routed, follow-ups sent — without writing config files or managing environments, you’ve crossed past what Codex is for.

That’s where Carly fits. Carly is an AI executive assistant built to act on triggers across your whole stack, set up by conversation instead of code:

  • No-code setup. Tell Carly “flag urgent Slack messages and follow up” in plain English; it interviews you and builds the workflow. No config.toml, no MCP server to run, no GitHub required.
  • Fires on events, 24/7, in the cloud — when a message lands, Carly acts; nothing to keep running on your machine.
  • Connects Slack to the rest of your work — route and post messages as part of a workflow that also touches email, calendar, CRM, and tasks.
  • Actually sends and updates — drafts and sends email (Gmail and Outlook), files and labels, manages tasks, updates your CRM, records meetings.

AI agents start at $35/month, and workflow steps that don’t use AI run free and unlimited. Carly connects to 200+ tools across 40+ categories — see integrations. By the way, Carly also integrates with Slack.


Codex’s Slack integration vs Carly

Codex (Slack integration)Carly
PurposeLaunch coding tasks from SlackHandle Slack + ops work
SetupGitHub, environments, configDescribe it in plain English
Reads channels & threadsYes (for task context)Yes
Routes / follows up on messagesNoYes
Acts on triggers / eventsTask-launch onlyYes, on any event
Runs without your machineCloud tasks (dev)Yes (cloud, 24/7)
Sends email as part of the flowNoYes (Gmail + Outlook)
Built forDevelopersExecs, EAs, operators
PricingPaid ChatGPT planAI agents from $35/mo

Codex-in-Slack is a coding agent you summon from a channel. Carly is an assistant that works your Slack and the rest of your day.


Frequently Asked Questions

Does OpenAI Codex integrate with Slack?

Yes. Codex has an official Slack app that lets you mention @Codex in a channel or thread to kick off a cloud coding task against your connected GitHub repo. It reads thread context and replies with a link to the result. It requires a paid ChatGPT plan, a connected GitHub account, and a configured environment.

Can Codex manage my Slack messages or route requests?

No. The Slack integration is designed to launch coding tasks, not to triage messages, route requests, or follow up on threads. For an assistant that handles Slack as part of your workflow, you need an agent platform like Carly.

How do I connect Codex to Slack?

Install the Codex Slack app from Codex settings (an admin may need to approve it), make sure you have a connected GitHub account and at least one environment, then mention @Codex in a channel with your prompt. It’s a developer setup, not a one-click connect.

Is Codex the right tool for non-technical Slack automation?

Not really. Codex is a coding agent, and its integrations assume repos, environments, and config files. If you’re not shipping code and just want Slack and your inbox handled, a no-code assistant like Carly is a better fit — set up by describing it, running 24/7 in the cloud.


More: Codex + Gmail · Codex + Outlook · Codex + Google Calendar · Codex + Outlook Calendar · Best AI personal assistants

Ready to automate your busywork?

Carly schedules, researches, and briefs you—so you can focus on what matters.

See what people say

"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.

Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.

On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."

Gus Ibrahim, Founder & Director, IHR