Skip to content
Catalyst Cloud

Search is only available in production builds. Try building and previewing the site to test it out locally.

Quick start

Catalyst Cloud is invitation-only while it is in staging. Accept the invitation email before anything else. Signing in without one creates a user with no account, and every later step fails with GET /me failed (403): jwt-org-unmapped.

You need one coding agent installed: Claude Code, Codex, OpenCode or Cursor. The installer checks for one and tells you if it finds none. It checks for Node and Git the same way and says exactly what to install.

1. Paste one command

Section titled “1. Paste one command”
Terminal window
curl -fsSL https://staging.catalystcloud.dev/install.sh | sh

It shows its plan and asks before it continues. It installs the Catalyst command-line tool and the Catalyst skills into your coding agent, then signs you in: it prints a short code and a sign-in URL on a *.authkit.app address (WorkOS, Catalyst’s sign-in provider). Open the URL yourself, type the code and approve; the browser does not open on its own, and the code expires after five minutes. If it expires, run the same command again.

It ends with READY: this machine is set up.

2. Open your coding agent and type /catalyst-onboard

Section titled “2. Open your coding agent and type /catalyst-onboard”

The onboarding agent checks where you are and does the rest, one step at a time. It does what it can from the terminal and, when a step needs your browser, hands you one link and one action, then checks that it landed before moving on.

  • Linear. It sends you to Settings → Connections; Linear asks you to authorise Catalyst in your browser and returns you.
  • Your team’s stages. It sends you to Settings → Linear teams to pick one team and map its stages, or to adopt Catalyst’s stages in one click. Start with the team you care least about breaking.
  • GitHub. It sends you to the same Connections page to install the Catalyst Cloud Connector GitHub App and grant it the repository you want worked, then to Settings → Repositories to register that repository against the team.
  • A coding account. It tells you when no usable account exists and sends you to Settings → AI accounts to add Claude or Codex.
  • The settings file. It reads what your repository needs and proposes the .catalyst/catalyst.toml declaration for you; see The settings file if you want to know what is in it.

When it says the team is ready, move a ticket to that team’s start stage, usually Todo. An agent picks it up and comments on the ticket when its first stage completes. Watch on the ticket page, its Agent work tab, and Cloud Activity; anything that needs you appears in Waiting on me.

If something does not work

Section titled “If something does not work”
What you see What to do
GET /me failed (403): jwt-org-unmapped Accept the invitation email, then sign in again.
the login code expired after 5 minutes Run the install command again and approve within five minutes.
FAILED step: install the CLI and the log shows EACCES Your Node came from the nodejs.org installer and its global folder is root-owned. Install Node with Homebrew, or run npm config set prefix ~/.npm-global and add its bin directory to your PATH.
A ticket sits in its start stage and nothing happens Ask the onboarding agent: /catalyst-onboard reads your account and names the failing check. The usual causes are an unmapped stage, a paused repository, or a team already at its limit of 12 tickets in progress.