ChatGPT Dots with GitHub: connect it and get pull requests

Connect the GitHub plugin and your dot can read your repositories. To change code, your dot starts a Work or Codex task, on your computer or in a Codex cloud environment, and brings you a pull request to review.

#How a request becomes a pull request

Your dot doesn't write the code in the chat. It hands the job to a task that runs in one of two places, then checks the result and reports back.

Your connected computer has to stay on, with the ChatGPT app open. A Codex cloud environment keeps going with your laptop closed, once you've created it in Codex.

#Which setup does your job use?

With the two places in mind, pick the job you have. The answer tells you what to have ready and which usage it spends.

#Connect GitHub

Whichever setup you use, your dot needs the GitHub plugin to read your repositories. If you already connected GitHub to ChatGPT, Work or Codex, your dot has it and you can skip this.

1. Open Plugins from the @ icon at the far left of ChatGPT and click + on the GitHub row.
2. On GitHub, install and authorize the ChatGPT app.
3. Select the repositories it can read. Pick specific ones, not all of them.
4. Wait about five minutes, then ask your dot: "Which repositories can you read?"

The + sits at the end of the GitHub row.

Your dot looks through connected repositories without being asked, so choose them on purpose. You can change the list later in the app's settings on GitHub.

#Three recipes that end in a pull request

Each recipe says where the work runs. Swap in the parts in [BRACKETS], and keep the last line: it leaves the merge with you.

Use my [ENVIRONMENT NAME] Codex cloud environment. Investigate issue #[NUMBER] in [OWNER/REPO], reproduce it, and prepare a fix with tests. Open a draft pull request and send me the link, with a summary of what you changed and what you couldn't verify. Don't merge anything.

This is what done looks like. The pull requests are opened under the dot's own name, and each one waits for a person.

Marker 1Marker 2

1. 1Opened by the dot, here named alfred, and tagged Bot.
2. 2Review required: the merge is yours.

For code that only lives on your machine, have your dot find the problems first and fix them after you've read the list.

Open [THE APP: a folder or a local address] on my computer and test it. Check the layout at different screen sizes and the main flows. Bring me a prioritized list of bugs with what you'd change. Don't change any code until I say so.

Once your dot is in Slack, it can pick up bug reports where your team posts them.

Watch #[CHANNEL] in Slack for bug reports about [OWNER/REPO]. When one comes in, investigate it, prepare a fix with tests in my [ENVIRONMENT NAME] Codex cloud environment, and reply in the thread with a summary and the pull request link. Don't merge anything. Confirm what you've set up.

#What your dot can and can't do with GitHub

The table below sorts the jobs by what does them.

#Fixes

If something's off, find what you see in the left column.

#Check you've got it

One question before you go.

1. 6 October 2026
   Rebuilt as a recipe page with a drawing of the two setups, a chooser and three recipes.
2. 5 October 2026
   First published.