Getting started
ThreadGrid is a Mac app that runs a small software team on the Claude Code you already have. You open a project, say what you need in a thread, and the team plans it, builds it, checks it and ships it. This page takes you from download to your first shipped change.
What you need
- A Mac with Apple silicon or an Intel processor, on macOS Ventura 13.3 or later.
- Claude Code, installed and signed in with a Claude Pro or Max plan or an Anthropic API key.
- git, which comes with the Xcode command line tools.
ThreadGrid doesn't run models itself. Every teammate works through your own Claude Code login, on your Mac, under your own plan.
Install Claude Code, then run it once and sign in:
curl -fsSL https://claude.ai/install.sh | bash
claudeIn Claude Code, type /login and follow the prompts. If you don't have git yet:
xcode-select --installInstall ThreadGrid
- Download ThreadGrid, then open
ThreadGrid.dmgfrom Downloads. One app supports both Apple silicon and Intel. - Drag ThreadGrid onto the Applications folder in the installer window. Wait for Finder to finish copying.
- Open Applications → ThreadGrid. After the copy finishes, eject the ThreadGrid disk in Finder. Keep using the copy in Applications rather than the app on the disk image.
If you're replacing an older copy, finish or pause its work and quit ThreadGrid first. If Finder says the app is in use, cancel the replacement and quit the existing app before trying again. Replacing the app does not require deleting its settings, projects or data.
If the download is incomplete or macOS says the disk image can't be opened, download a fresh copy from the link above. If macOS reports that the app is damaged, cannot be verified or was blocked, stop and contact [email protected] with the exact message and your macOS version. Do not disable Gatekeeper, remove quarantine attributes or delete your data to force the install.
For later updates, choose Check for Updates… from the ThreadGrid app menu. Follow the app's prompt when you're ready; a manual download remains available if an update fails. Finish active work before quitting for a manual replacement.
Optional tools
| Tool | What it adds | Install |
|---|---|---|
| GitHub CLI | Pull requests, releases and repo status | brew install gh, then gh auth login |
| Codex CLI | Teammates that run on OpenAI's Codex | npm i -g @openai/codex, then codex login |
| Node.js | Most web projects need it for their checks | brew install node |
| Coolify | Deploys after each ship | See Shipping targets |
| 21st.dev | Premium UI components for designers and frontend teammates | See Shipping targets |
The first-launch check
The first time you open ThreadGrid it runs a quick check of what it needs. Anything missing comes with the exact command to fix it. Press Check again when you're done, or Test Claude to run a tiny one-turn session and confirm the team can work.
| Check | Needed? | How to fix it |
|---|---|---|
| Claude Code | Required | curl -fsSL https://claude.ai/install.sh | bash |
| Signed in to Claude | Required | Run claude, then type /login |
| Git | Required | xcode-select --install |
| Workspace folder | Required | Where new projects live (~/ThreadGrid by default). Choose another in Settings → App. |
| GitHub CLI | Optional | brew install gh, then gh auth login |
| Codex CLI | Optional | npm i -g @openai/codex, then codex login |
What are we building?
Onboarding is one screen with two paths.
- Open a folder. Pick an existing repository. The Lead reads it, writes a short summary of what the project is and how to check it, and asks a couple of questions. If the repo has an
originremote, pushing is switched on as a ship step; you can turn it off in Settings → Shipping. - Describe an idea. Write a sentence or two, like "a habit tracker for couples, with shared streaks and a weekly recap email". The Lead asks three to six quick questions, creates the project in
~/ThreadGrid/<name>and proposes a first piece of work.
Either way you land in your first thread with the Lead already talking.
Your first thread
Say what you need, the way you'd tell a colleague:
The Lead answers in the thread. Small asks get done straight away; bigger ones get a plan first. Work shows up as a work block under your message, with a line that moves through triage, plan, build, verify and ship. When it ships, the Lead posts the result with links to the pull request, the tag and the deploy.
Read Threads for everything the thread view does, and Approvals and decisions for where the team stops to ask you.
Your team
Every project starts with a Lead and a few teammates suited to it, such as Backend, Frontend and QA. Open Team in the sidebar to see who they are, what they worked on recently and which model each one uses. You can add or remove a teammate in one step.
Keyboard shortcuts
| Shortcut | What it does |
|---|---|
⌘N | New thread |
⌘K | Search threads, tasks and actions |
⌘I | Show or hide the inspector |
⌘, | Settings |
⌘↵ | The primary action on a decision card, such as Ship it |
Enter / Shift+Enter | Send / new line in the composer |
Something unclear or out of date? Email [email protected].