Skip to main content
The GrowthBook Wizard signs you in and sets up an SDK Connection in your existing project. Your coding agent finishes the SDK integration, adds targeting attributes, and helps you create your first Feature Flag. You don’t need to copy keys.
GrowthBook currently shows this setup flow only for organizations whose creator selected Engineering as their role during signup. Organizations managed through Vercel use their own setup flow.

​
Prerequisites

  • A GrowthBook Cloud account or a self-hosted instance. You’ll sign in during setup.
  • Node.js 22.20.0 or newer (24 LTS recommended). Check with node -v.
  • Claude Code, Cursor, Codex, opencode, Gemini CLI, or Antigravity.
  • Your project’s repository. Run the wizard from its root directory.

​
Run the wizard

In GrowthBook, go to Get Started → Connect Your SDK, select your SDK language, then choose your Coding agent on the AI-assisted tab. Copy the command and run it in your project directory:
To let the wizard detect your project and agent, omit those options:
After the wizard finishes, continue in your coding agent:
  • Claude Code, Codex, opencode, or Cursor CLI (cursor-agent): The agent opens with the setup instructions ready. Continue there.
  • Cursor or Antigravity desktop app: Select it with --cursor or --antigravity. If the wizard opens the app, paste the instructions from your clipboard into its agent chat.
  • Gemini CLI: Copy the instructions printed in your terminal and paste them into Gemini.
If your agent doesn’t open or the clipboard is empty, copy the printed instructions into your agent manually.
For manual setup, use the Manual setup tab or SDK docs. No-code platforms (including Webflow, WordPress, and Shopify), Roku, and generic script tags only offer this option.

​
What happens

1

Sign in

Approve access in your browser and choose an organization if you belong to several. The helper scripts handle your sign-in token without passing it to your coding agent.
2

Detect your project

The wizard identifies your language, framework, and package manager. --language skips language detection.
3

Create an SDK Connection

Choose a name and environment (dev by default). The wizard reuses connections with the same name, language, environment, and project, and creates missing environments.
4

Install the SDK

The wizard installs the package or gives your agent a dependency snippet to add. Where supported, it writes the public client key to .env or .env.local with your framework’s prefix and adds the file to .gitignore. Other platforms use their own configuration. Browser apps include this key in their bundle.
5

Install the skills

The wizard installs the setup skill and GrowthBook Agent Skills for ongoing work with flags and experiments. Newly installed skills load in your next agent session.
6

Complete the integration

Your agent:
  • Asks you to approve a plan before editing your app.
  • Connects the SDK and checks that the project builds.
  • Finds targeting attributes such as user ID or plan, then adds the ones you select to GrowthBook and your SDK.
  • Helps you flag a behavior you choose, run an A/B test, or finish without a flag.
  • Runs setup checks and opens the report in GrowthBook.
A/B tests need metrics and a data source, which setup doesn’t create. Restart your agent if the experiments skill hasn’t loaded yet.

​
Review the setup report

The report shows:
  • Created During Setup: your SDK Connection, Feature Flag, and other created items. Open each to review its settings.
  • Configured by Your Agent: targeting attributes and other settings.
  • Any failed required checks for SDK installation, imports, configuration, or flag usage.
These checks inspect your code. The SDK Connection shows as connected once your app requests features from GrowthBook. Get Started links to your latest report and warns about failed required checks. You can dismiss the notice once they all pass.

​
Resume or start over

Your agent records progress in GROWTHBOOK_SETUP.md in your repository root. After an interruption or teammate handoff, rerun the wizard or ask your agent to continue from that file. Use --fresh to sign out and start a new report. The wizard still reuses an SDK Connection with matching settings.

​
Options

​
Self-hosted GrowthBook

Pass your API host to use a self-hosted instance:
Add --app-origin if the app URL differs from the one your API reports. Commands copied from a self-hosted Connect Your SDK page already include --api-host. Your instance must support browser sign-in; otherwise, follow the manual SDK setup. The wizard is open source: npm package · source code.

​
Next steps