use-cases/slack-coding-tasks.md

name: Kick off coding tasks from Slack tagline: Delegate repository work from Slack threads. summary: Mention @ChatGPT in Slack to request repository work in an eligible workspace-shared Codex Cloud environment, then review the result in the thread. bestFor:

Async handoffs with enough context in the Slack thread to act on
Teams handling issue triage, bug fixes, or scoped implementation work from Slack starterPrompt: title: Start the task from a thread body: >- @ChatGPT investigate the issue described in this thread for [repository].

Use the workspace-shared Cloud environment for [project or environment].

Make the smallest useful fix, run the relevant checks, and report the result here. suggestedModel: cloud relatedLinks:
label: Use ChatGPT in Slack url: /codex/third-party/slack
label: Codex Cloud environments url: /codex/environments/cloud-environments

For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to the page URL.

How to use

Have your workspace admin enable the ChatGPT app in Slack using the Slack setup guide.
For repository work, confirm that Cloud delegation is enabled and an eligible workspace-shared environment has a published version. For an Enterprise workspace, follow the environment sharing guidance.
Copy the starter prompt into an enabled Slack channel or thread. Include the repository, relevant context, constraints, and the result you want.
Complete any connection or approval prompts, then review the result and reported checks. When available, use Follow along to inspect the coding task.
Mention @ChatGPT in the same thread for related work. Follow-ups that use the same account to run the task can continue it; another execution account may start a separate task. Start a new conversation to use a different Cloud environment.

Tips

Summarize the issue and expected behavior if the thread doesn't already provide enough context.
Name the repository or intended workspace-shared environment. Personal Cloud environments aren't included in this Slack flow.
Check that the account running the task has the required environment, repository, and service access. A Slack reply doesn't give everyone access to the coding task.
Keep the request scoped and name relevant files or folders in a large codebase.
Before merging, review proposed changes and check that the reported tests cover the requested behavior.

use-cases/slack-coding-tasks.md +43 −22

1---1---

2name: Kick off coding tasks from Slack2name: Kick off coding tasks from Slack

~~3tagline: Turn Slack threads into scoped cloud chats.~~3tagline: Delegate repository work from Slack threads.

~~4summary: Mention `@Codex` in Slack to start a chat tied to the right repo and~~4summary: Mention `@ChatGPT` in Slack to request repository work in an eligible

~~5 environment, then review the result back in the thread or in Codex cloud.~~5 workspace-shared Codex Cloud environment, then review the result in the

6 thread.

6bestFor:7bestFor:

~~7 - Async handoffs that start in a Slack thread and already have enough context~~8 - Async handoffs with enough context in the Slack thread to act on

~~8 to act on~~9 - Teams handling issue triage, bug fixes, or scoped implementation work from

~~9 - Teams that want quick issue triage, bug fixes, or scoped implementation work~~10 Slack

~~10 without context switching~~

11starterPrompt:11starterPrompt:

~~12 title: Kick Off the Task From a Thread~~12 title: Start the task from a thread

~~13 body: "@Codex analyze the issue mentioned in this thread and implement a fix in~~13 body: >-

~~14 <name of your environment>."~~14 @ChatGPT investigate the issue described in this thread for [repository].

16 Use the workspace-shared Cloud environment for [project or environment].

18 Make the smallest useful fix, run the relevant checks, and report the result

19 here.

15 suggestedModel: cloud20 suggestedModel: cloud

16relatedLinks:21relatedLinks:

~~17 - label: Use Codex in Slack~~22 - label: Use ChatGPT in Slack

18 url: /codex/third-party/slack23 url: /codex/third-party/slack

~~19 - label: Codex cloud environments~~24 - label: Codex Cloud environments

~~20 url: /codex/environments/cloud-environment~~25 url: /codex/environments/cloud-environments

21---26---

22 27

23> For the complete documentation index, see [llms.txt](/llms.txt). Markdown versions of documentation pages are available by appending `.md` to the page URL.28> For the complete documentation index, see [llms.txt](/llms.txt). Markdown versions of documentation pages are available by appending `.md` to the page URL.

24 29

25## How to use30## How to use

26 31

~~271. Install the Slack app, connect the right repositories and environments, and add `@Codex` to the channel.~~321. Have your workspace admin enable the ChatGPT app in Slack using the [Slack

~~282. Mention `@Codex` in a thread with a clear request, constraints, and the outcome you want.~~33 setup guide](https://developers.openai.com/codex/third-party/slack).

~~293. Open the chat link, review the result, and continue the follow-up in Slack if the task needs another pass.~~342. For repository work, confirm that Cloud delegation is enabled and an eligible

30 35 workspace-shared environment has a published version. For an Enterprise

~~31You can learn more about how to use Codex in Slack in the [dedicated guide](https://developers.openai.com/codex/third-party/slack).~~36 workspace, follow the [environment sharing

37 guidance](https://developers.openai.com/codex/environments/cloud-environments#share-within-an-enterprise-workspace).

383. Copy the starter prompt into an enabled Slack channel or thread. Include the

39 repository, relevant context, constraints, and the result you want.

404. Complete any connection or approval prompts, then review the result and

41 reported checks. When available, use **Follow along** to inspect the coding

42 task.

435. Mention `@ChatGPT` in the same thread for related work. Follow-ups that use

44 the same account to run the task can continue it; another execution account

45 may start a separate task. Start a new conversation to use a different Cloud

46 environment.

32 47

33## Tips48## Tips

34 49

~~35- If the thread does not already include enough context or suggested fix, include in your prompt some guidance~~50- Summarize the issue and expected behavior if the thread doesn't already provide

~~36- Make sure the repo and environment mapping are correct by mentioning the name of the project or environment in your prompt~~51 enough context.

~~37- Scope the request so Codex can finish it without a second planning loop~~52- Name the repository or intended workspace-shared environment. Personal Cloud

~~38- If your project is a large codebase, guide Codex by mentioning which files or folders are relevant to the task~~53 environments aren't included in this Slack flow.

54- Check that the account running the task has the required environment,

55 repository, and service access. A Slack reply doesn't give everyone access

56 to the coding task.

57- Keep the request scoped and name relevant files or folders in a large codebase.

58- Before merging, review proposed changes and check that the reported tests cover

59 the requested behavior.

use-cases/slack-coding-tasks.md 2026-09-28 23:02 UTC to 2026-09-29 22:59 UTC

How to use

Tips