Slack and Linear Workflow Integration

Your designer posts a screenshot of a broken layout in the #bugs Slack channel. Instead of filing a ticket, assigning it, waiting for a dev to pick it up, and then waiting for them to find the right file — someone types @Codex fix the header alignment issue shown above in the frontend repo. Within minutes, Codex posts a link to a PR with the fix. This is the Slack integration at its best: turning conversations directly into code changes.

What You’ll Walk Away With

• Complete setup guides for both the Slack and Linear integrations
• Workflow patterns that turn Slack messages and Linear issues into Codex cloud tasks
• Strategies for managing environment selection, thread context, and enterprise data controls
• The Linear MCP server configuration for local Codex access to issue data

Codex in Slack

Setup

1. Set up Codex cloud tasks by connecting GitHub and creating at least one environment.
2. Go to Codex settings > Connectors and install the Slack app for your workspace.
3. Add @Codex to the channels where you want it available. Slack prompts you to add it when you first mention it.

Starting Tasks

Mention @Codex with your prompt in any channel or thread:

@Codex fix the N+1 query in the orders listing endpoint.
The slow query is in src/services/orders.ts

Codex reacts with an eyes emoji, creates a cloud task, and replies with a link. When the task finishes, Codex posts the result in the thread (if your admin allows it).

Prompt: Context-aware Slack task

In a thread where someone pasted an error traceback:

“@Codex fix the above error in openai/codex. The stack trace suggests a null pointer in the session handler. Add a regression test.”

Codex reads the entire thread history, so you do not need to re-paste the error.

Environment Selection

Codex automatically selects the environment that best matches your request:

• If you specify a repo, Codex uses the environment containing that repo
• If ambiguous, it falls back to the environment you used most recently
• If no suitable environment exists, Codex replies with instructions to fix the issue

To override: reply in the thread with Please run this in openai/openai (applied) and mention @Codex again.

Enterprise Data Controls

Enterprise admins can disable answer posting via Allow Codex Slack app to post answers on task completion in workspace settings. When disabled, Codex posts only a link to the task, preventing code snippets from appearing in Slack channels.

Codex in Linear

Setup

1. Set up Codex cloud tasks with a connected GitHub account and at least one environment.
2. Go to Codex settings > Connectors and install Codex for Linear.
3. Link your Linear account by mentioning @Codex in a comment on any Linear issue.

Delegating Work

Assign issues directly: After setup, assign issues to Codex the same way you assign them to teammates. Codex starts work and posts updates to the issue.

Mention in comments: Use @Codex in comment threads for ad-hoc tasks or questions. Follow up in the thread to continue the same session.

@Codex fix this bug in openai/codex. The error occurs when
the session ID is null. Add proper null checking and a unit test.

Automatic Triage with Linear Rules

Set up triage rules so new issues automatically go to Codex:

1. In Linear, go to Settings > Your teams > [team name].
2. Open Triage and turn it on.
3. In Triage rules, create a rule: Delegate > Codex (plus any labels or properties you want).
4. New issues entering triage are automatically assigned to Codex.

When using triage rules, Codex runs tasks using the account of the issue creator.

Prompt: Linear issue with specific repo context

In a Linear issue comment:

“@Codex fix this in openai/codex-frontend. The bug is in the session management module. The user reports that logging out does not clear the session cookie. Add an integration test that verifies cookie cleanup on logout.”

Linear MCP Server for Local Access

For local Codex sessions (App, CLI, or IDE Extension), connect to Linear via MCP:

# Recommended: use the CLI
codex mcp add linear --url https://mcp.linear.app/mcp

Or configure manually in ~/.codex/config.toml:

[mcp_servers.linear]
url = "https://mcp.linear.app/mcp"

Then authenticate: codex mcp login linear

This gives local Codex sessions read access to your Linear issues, enabling prompts like “Look at Linear issue FE-234 and fix the reported bug.”

When This Breaks

• Missing connections: Codex replies with a link to reconnect if your Slack or GitHub connection is not confirmed.
• Unexpected environment choice: Be explicit about the repository in your prompt, or reply in the thread with the correct environment and re-mention @Codex.
• Long threads: Summarize key details in your latest message. Context buried in a 50-message thread may get lost.
• Workspace posting restrictions: Enterprise workspaces may restrict answer posting. Open the task link to view progress and results.
• Linear triage not triggering: Verify the triage rule is enabled and that the issue enters triage status. Check that the Codex integration has the necessary permissions.

What’s Next

• Cloud Environments — Both integrations run cloud tasks; optimize your environment setup
• Enterprise Governance — Admin controls for Slack and Linear data exposure
• Cost Management — Each cloud task from Slack or Linear consumes credits