# Codex Features and Practical Usage ☁️ Codex fixes repos you haven't even cloned locally, working on them in parallel in the cloud and turning the diffs into PRs. A way of working that never ties up your own machine. 🏷️ Title: Codex Cloud 🔗 URL: 📘 Overview Codex Cloud lets you delegate tasks to the cloud, where Codex works in the background in its own environment. It can run multiple tasks in parallel, and when you delegate work it clones your repository into that cloud environment. When done, it turns the diff into a pull request automatically. ⚙️ How It Works ・Tasks can be delegated from several entry points: the web platform, the IDE extension, and GitHub integrations, all running in parallel inside cloud environments. ・On delegation, the repo is cloned into the cloud environment, giving an isolated setup free of local-machine dependencies. ・You shape the environment with setup scripts (initialization before a task runs), environment configuration (repo selection, tools, dependencies), and internet access controls (whether public networking is allowed). ・Results become PRs automatically, linked to the originating GitHub issue, or you can apply the diff locally through the IDE extension. ・Where the local CLI runs on your machine with direct filesystem access, Cloud offloads execution to managed containers, giving you parallelization, background processing, and lower local resource use. 🛠️ Practical Usage ・Go to and connect your GitHub account to enable repo integration and PR creation. ・For reproducibility, define dependency installs and build prep in the environment's setup script. Enable internet access selectively, only for tasks that truly need external resources. ・Keep prompts clear and constrained with the right level of detail rather than vague. 💡 Use Cases Fire off several independent bugs or small features as concurrent cloud tasks, then review the resulting PRs one by one for parallel development. Even for a repo you've never set up locally, a working setup script lets Codex start immediately. ⚠️ Caveats ・Cloud execution runs in containers with defined resource limits and cannot reach local-only tools or private networks without explicit configuration. ・Always review the diff before merging an auto-generated PR. ・Enable internet access only when needed, in line with your security requirements. #OpenAICodex# #CodexCloud#

# Codex Features and Practical Usage 💬 Just mention `@/Codex` in a bug-report thread. It spins up a cloud task with the whole conversation as context and comes back with a fix PR. 🏷️ Title: Chat / Ticket Integration (Slack / Linear) 🔗 URL: 📘 Overview The Slack integration kicks off a Codex cloud task whenever you mention `@/Codex` in a channel or thread. Thread context is included automatically, so you don't have to restate the earlier discussion. Linear works similarly, launching tasks from a ticket. ⚙️ How It Works ・Mention `@/Codex` with a prompt in a thread and the bot detects it, starting a cloud task. Codex reacts with 👀 and replies with a task link. ・Alongside your message, the preceding thread history is sent, so Codex acts with full awareness of the prior discussion. On completion it posts results or threaded replies depending on workspace settings. ・The environment is chosen automatically: Codex matches accessible environments against your request, falls back to your most recently used environment when ambiguous, and runs against the default branch of the first repository in that environment's config. ・Enterprise admins can disable answer posting in ChatGPT workspace settings, limiting replies to task links only so sensitive environment details don't surface in Slack. 🛠️ Practical Usage ・You'll need a ChatGPT Plus plan or higher, a connected GitHub account, at least one configured cloud environment, and (workspace-dependent) Slack admin approval. ・To target a specific repository, name it in the mention, e.g. `@/Codex fix the above in openai/codex`. ・For complex threads, summarize the key points in your latest message so context isn't lost. 💡 Use Cases When a customer bug report blows up in a thread, ask `@/Codex` to fix it once the conclusion is clear. Without opening the repo locally, the assignee gets a context-aware fix PR. From Linear, the same flow launches a task using the ticket's content as context. ⚠️ Caveats ・If GitHub or Slack connections lapse, you'll get prompts to reconnect. ・When the environment is ambiguous, Codex might run against an unintended repo, so name the target explicitly for important requests. ・For detailed Linear mechanics, consult the Linear-specific documentation rather than this Slack-focused page. #OpenAICodex# #Slack#

# Codex Features and Practical Usage 🔍 Open a PR and get back only the genuinely serious findings, not noise. Codex's GitHub integration posts automated code reviews scoped to high-priority P0/P1 risks. 🏷️ Title: PR Review (@/codex review) 🔗 URL: 📘 Overview Codex's GitHub integration has the AI review a pull request's diff and post high-signal feedback. By design it filters to only P0 and P1 issues, so review comments stay focused on high-priority risks instead of drowning you in nitpicks. ⚙️ How It Works ・For a manual review, comment `@/codex review` on the PR. Codex reacts with 👀 and then posts a GitHub code review. ・Enable Automatic reviews in settings and a review runs the moment a PR is opened, with no mention required. ・Steer the review with a "Review guidelines" section in a top-level `AGENTS.md`. Codex applies the closest `AGENTS.md` to each changed file, so you can nest deeper instructions for package-level scrutiny. ・Mentioning `@/codex` with anything other than `review` kicks off a cloud task using the PR as context, e.g. `@/codex fix the CI failures`. 🛠️ Practical Usage ・First enable the Code review toggle for your repo in the settings (Codex cloud setup is a prerequisite). ・To lock in your review lens, add a "Review guidelines" section to `AGENTS.md` with rules like "Don't log PII" and "Verify authentication middleware wraps every route." ・For a one-off focus, append it inline: `@/codex review for security regressions`. ・To go from review straight to a fix, comment `@/codex fix the P1 issue` and Codex starts a cloud task to address it. 💡 Use Cases On a team where reviewers are stretched thin, let Codex do a first pass to clear P0/P1 issues before human review, cutting down review round-trips. Codify non-negotiable concerns like security and PII handling in `AGENTS.md` so every PR is checked for them automatically. ⚠️ Caveats ・Requires Codex cloud setup on the repo and code review enabled for it. ・The manual trigger must be the exact string `@/codex review`. ・Automatic reviews depend on the toggle being configured correctly, so verify settings during onboarding. #OpenAICodex# #CodeReview#