Getting started

Set up DevKit on your Mac

1. Install DevKit on your Mac

DevKit needs a small helper on your Mac to work on local projects. Install it once, then return to this chat. Requires an Apple Silicon Mac (M1 or newer).

Open Terminal: press Command + Space, type Terminal, then press Return.

If you already have Homebrew, paste these three lines into Terminal:

brew tap-new devkit/local
curl -fL https://devkit.run/downloads/devkit.rb -o "$(brew --repository devkit/local)/Formula/devkit.rb"
brew install devkit/local/devkit

Homebrew installs the required Node.js runtime too. When installation finishes, run:

devkit --help

Done when: Terminal prints the DevKit commands. Already installed? Run this help check and continue to step 2. If Terminal says brew: command not found, install Homebrew from its official website, then return here. If the local tap already exists, skip the first line. If installation fails, stop and use the error to troubleshoot; do not continue with commands for an uninstalled helper.

2. Connect this Mac to your DevKit account

In Terminal, run this complete command:

devkit login --backend https://code.devkit.run --auth0-issuer https://dev-3kfazan344cjsvi3.eu.auth0.com/ --client-id h95fohE9xJsjs0nJsT8UkDjt7U5SkfuK

Open the sign-in URL printed by Terminal, sign in with the same DevKit account you connected in ChatGPT, compare the device code and approve pairing. Done when: Terminal says the Mac is paired. Already paired? Keep that pairing; do not log out or create a replacement.

Run:

devkit setup codex
devkit model login

This prepares Codex and reuses its existing ChatGPT login on this macOS user. If Codex needs sign-in, it opens the official login flow. No API key is needed. Done when: the command reports it is configured.

4. Start the Mac helper

While the helper is stopped, enable access to the project folders you name, then start it:

devkit folders enable
devkit run

Done when: the helper reports it is running. Keep this Terminal open and your Mac awake and online. Return to ChatGPT and say “Check my connection.” The local check is devkit doctor.

Optional background startup

After stopping the foreground helper, run devkit service install only if you want background startup. This is optional, not a requirement for your first task.

5. Return to ChatGPT

Already using DevKit Code in this chat? Stay here; no custom server or OAuth scope editing is needed. Say “Check my connection.” ChatGPT checks the Mac and guides only the next missing step.

First time connecting in ChatGPT? Open DevKit Code in ChatGPT, choose Install plugin, and connect the same DevKit account you used in step 2. Review the sharing consent. Then select DevKit in a new Chat conversation.

Choose GPT-6 with Extra High reasoning for coding. Keep the conversation active while the task runs. The task card shows progress and local permission waits automatically. It offers View changes and Cancel; the saved final answer appears in the conversation. In a text-only client, no embedded card is required. Work is optional for longer tasks and uses your ChatGPT account's Work allowance; choose Cloud if the desktop app asks where to run it.

Manual MCP connection (advanced)

Use this only if you deliberately need a custom connection instead of the published plugin. Choose Add custom MCP server and use https://code.devkit.run/mcp/code with OAuth authentication. Leave the discovered client method and default scopes unchanged. Set Base scopes to the following, one per line:

openid
email
offline_access
devkit:read
devkit:execute
devkit:manage

No Codex credential belongs in this form; its login stays on the Mac. Review the actual connection consent. ChatGPT connection guide.

Background service installation is explicit. Describe the change and name your project. It finds the folder automatically; no project registration or picker is required. Source checkout files stay intact while Git jobs use isolated worktrees.

Use your local Codex login

DevKit uses Codex signed in with ChatGPT on this Mac. If you already use Codex here, that login is reused. Run devkit model login only when Codex needs sign-in; Codex opens its official ChatGPT login. DevKit does not read, copy or upload its login credentials.

For an older API-key installation, stop the agent and run devkit model setup to switch this profile to local Codex. It no longer asks for an API key. Use devkit model status to check the sign-in. Your Codex subscription limits apply. DevKit stops when subscription quota is unavailable or exhausted and never falls back to API-key billing or purchases credits.

Work on your project

In ChatGPT, say “Fix the checkout total in Demo Shop and run its tests.” DevKit finds the named folder. ChatGPT reports meaningful progress and the saved final answer automatically; you do not need to refresh or ask it to check again. If the task needs a local permission decision, choose Approve or Deny in the Mac window while ChatGPT waits.

Say “Show me the changes” to review the saved patch in the conversation, reply with a follow-up to continue the same working copy, or say “Cancel that task” to stop unfinished work. Cancellation does not undo earlier changes. You can also use View changes and Cancel on the task card. Closing an old conversation does not create background push notifications.

Local approval decisions

When Codex needs permission, a DevKit Code approval window opens on your Mac. Read the command or proposed changes, then click Approve or Deny. Closing the window denies the request. No terminal is needed. ChatGPT shows the waiting state and cannot make this decision for you.

Operator fallback

devkit approvals
devkit approve APPROVAL_ID --decision accept
# Or use decline / cancel

Connections

Separate DevKit integrations are not part of the Code-only release. Choose a provider, preserve its identity and credential references, and use devkit recipe / devkit connection locally. Kubernetes, MySQL, Blender and iOS setup checks show missing runtimes, credentials and hardware.