Get up and running with Confidence in minutes. One command sets up authentication, installs the right SDK, connects MCP servers, and onboards your AI assistant — so you can start managing feature flags and experiments without leaving your editor.
- Zero-to-flags in one command — run
npx @spotify-confidence/quickstartand the interactive wizard handles the rest - Auto-detects your stack — React, Next.js, Node, Python, Swift, Kotlin, Java, and Go; installs the matching Confidence SDK
- Connects your AI assistant — configures MCP servers and IDE plugins for Claude Code, Cursor, or Codex so your agent can manage flags inline
- Guided onboarding — generates project context files that teach your AI assistant how your Confidence setup works
- Migrating from another platform? Pair with Confidence AI Plugins for one-command migrations from PostHog, Eppo, Statsig, or Optimizely
npx @spotify-confidence/quickstartRequires Node.js 24+.
Prefer to manage the integration yourself? confidence-ai-plugins provides standalone plugins that give AI agents the ability to manage feature flags, work with documentation, run migrations, and more — without the guided wizard flow.
Found a bug or have a feature request? Open an issue.
confidence-quickstart [command] [options]
| Command | Description |
|---|---|
| (default) | Launch the interactive setup wizard |
start |
Alias for the default command |
help |
Show the help message |
| Option | Description |
|---|---|
--dir <path> |
Project directory to run the wizard in |
--dry-run |
Run without making real API calls |
--debug |
Enable debug output and preserve terminal history |
--no-telemetry |
Disable anonymous usage telemetry |
During the project onboarding step, the wizard spawns your chosen AI agent to integrate the Confidence SDK into your project. You will be prompted to confirm before this step begins. Each agent runs with different permissions:
- Claude Code — Spawned in non-interactive (
--print) mode using its standard permission model. It can read files and execute tools within your project directory as allowed by your existing Claude Code settings. No elevated trust flags are applied. - Cursor — Spawned in agent mode with
--trust, which grants full read/write access to files in your project directory and allows it to run shell commands (e.g.npm install) without individual approval prompts. MCP server connections are also auto-approved (--approve-mcps). - Codex — Spawned in
execmode with--sandbox danger-full-access, which grants unrestricted filesystem and network access. It can read and write any file, run shell commands, and make network requests without sandboxing restrictions. Full access is required because the onboarding agent needs to install npm packages, modify project configuration files, and download SDK dependencies — operations that Codex's default sandbox would block.
All agents are scoped to your project directory and run with a timeout. The wizard installs a Confidence skill/plugin and connects MCP servers before spawning the agent, so configuration files may already be written to your project at that point.
The wizard collects anonymous usage data (e.g. which steps you complete) to help improve the experience. No personal or project data is collected.
To opt out:
npx @spotify-confidence/quickstart --no-telemetryOr set the environment variable:
CONFIDENCE_TELEMETRY=false npx @spotify-confidence/quickstartTelemetry is automatically disabled in CI environments and during development.
pnpm install
pnpm try # Run the wizard locally via tsx
pnpm test # Run vitest
pnpm lint # ESLint + Prettier check
pnpm typecheck # TypeScript type checking
pnpm qa # Run all checks (typecheck + lint + test)
pnpm build # Build for distributionE2E tests use node-pty to drive the TUI in a real terminal. This native module requires platform-specific build tools. If pnpm install fails on node-pty, install the prerequisites listed at https://github.com/microsoft/node-pty#dependencies.
The stable node-pty release (v1.1.0) doesn't ship prebuilt binaries for Node.js v26+. The project uses node-pty@1.2.0-beta.14 which includes updated Node-API bindings for newer Node versions. If you hit this error on a newer Node version, ensure the beta is installed. On CI with Node 24, the stable release works fine.