Collection · 4 use cases

For developers

Feedback in, reviewed fixes out: bug reports, pull requests and issues, with Codex doing the heavy lifting and you merging.

The 4 prompts in this collection

What your dot can own

OpenAI’s developer example is the clearest picture of what a dot can own: it watches feedback, scopes fixes, builds and tests them, and brings you pull requests to review. These prompts set that up step by step. For cloud coding work, create the Codex cloud environment first.

Suggested order

Start with the pull request digest and issue triage, which only read GitHub and report to you. Once those summaries are useful, add Slack bug-report monitoring, then let your dot prepare fixes for review.

Keep humans on the merge

Fixes arrive as draft pull requests, which are visible to everyone with access to the repository. Review each one like any contributor’s change, and keep merging, deploying and closing issues with you. Connecting Slack alone doesn’t start monitoring: ask your dot to confirm which events it can follow.

For developers: FAQ

Will my dot merge code?

No. Fixes arrive as draft pull requests for you to review. Merging, deploying and closing issues stay with you.

What do I need to set up first?

Connect GitHub, and for cloud coding work create a Codex cloud environment before asking your dot to use it.

Does adding my dot to Slack start bug monitoring?

No. Connecting Slack alone doesn't start monitoring. Ask your dot to watch a specific channel and confirm what it's following.