get-started8.24 KB
View saved version →
---
name: get-started
description: Set up DevKit Code, pair a Mac, check its connection, or guide a first coding task by project name. Use for DevKit onboarding and connection help.
---
# Set up DevKit Code
Help the user reach a connected Mac and a useful first task. Use the DevKit Code tools available in the current chat; do not substitute another repository, account or execution provider.
When the user asks for setup or connection help, read `devkit_status` silently if available. Explain only the next missing setup step. Ignore revoked devices when deciding whether a usable Mac is paired; do not lead with internal QA device names, IDs, status tables or a five-step checklist. An offline or revoked device does not prove that the helper is missing from the current Mac.
## First reply: one useful next step
The verified public guide is **https://devkit.run/docs#local-tools**. The published plugin is **https://chatgpt.com/plugins/plugin_asdk_app_6ad50cf4ff4c8191808e92261b5defc4**. These are actual release URLs, not placeholders. The Mac helper is installed with the Homebrew formula at **https://devkit.run/downloads/devkit.rb**; it is not a graphical installer or an App Store download.
If no usable Mac is connected and installation is unknown, start with: “First, install DevKit’s Mac helper. Open [Install DevKit on your Mac](https://devkit.run/docs#local-tools). On your Mac, press Command + Space, type Terminal, and press Return.” Then give only the install instructions below, with their success check. If the user says it is already installed, skip installation and help connect or start that same Mac. If the Mac is already ready, skip setup and ask what project they want to work on.
Do not say “use the official listing for the installer,” “use the command supplied by the release,” or “I couldn’t verify a public installer link” when these supplied release URLs are available. If a live fetch actually fails, name that specific failure; do not infer that the installer was never published. Do not send someone who already installed and connected the published plugin through manual MCP creation or OAuth scope editing again.
Use one stage at a time: install, pair, prepare Codex, start, then check readiness. State where to act, the exact command or link, and what success looks like. Wait for that stage’s result before supplying the next one. Never ask for the entire diagnostic log; if a step fails, ask only for the non-secret error line. Do not run installation, pairing or permission changes on the user’s behalf merely because they asked for guidance.
## Mac setup
The initial agent supports Apple Silicon macOS (M1 or newer). Homebrew installs Node 24+ as a dependency; do not make users install Node separately. The user needs a normal local Codex ChatGPT login with available included Codex quota. This beta is free from DevKit; no API account or API key is required and checkout is disabled. Never invent a domain, download link, native-client ID or pairing code.
For a first installation on a Mac with Homebrew, give this complete block:
```sh
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
```
Then verify with `devkit --help`. Success is the DevKit command list. If the local tap already exists, skip the first line. If `brew` is missing, direct the user to https://brew.sh/ and continue only after Homebrew is available. If installation fails, stop that stage and help with the actual error. Do not give `devkit setup codex` until the helper is installed.
After installation, pair the Mac using the complete public production command:
```sh
devkit login --backend https://code.devkit.run --auth0-issuer https://dev-3kfazan344cjsvi3.eu.auth0.com/ --client-id h95fohE9xJsjs0nJsT8UkDjt7U5SkfuK
```
The user opens the sign-in URL printed in Terminal, signs in to the same DevKit account connected in ChatGPT, compares the device co
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
