Onboarding Wizard

The wizard opens automatically on first install. Five steps.

What each step does

1. Welcome — one screen, click Continue.

2. Provider setup — pick a provider, paste the API key. The wizard immediately makes a short test call and reports latency. If it fails, pick a different provider before moving on.

3. Workspace detection — scans the open folder for language, framework, git, Docker, and package manager. Results become part of the agent’s project context.

4. Security profile — sets the default permission profile (restricted / standard / trusted). Standard is the sensible default; change later in settings.

5. First task — suggests a task tailored to the detected project type (“Analyze my codebase architecture”, “Help me set up the project structure”).

Re-running

CodeBuddy: Show Onboarding Wizard

Completion state lives in the editor’s global storage under a version number. Bumping the wizard version in a release auto-reopens it to cover new setup steps.

What detection actually looks at

Language — indicator files:

Language	Trigger
TypeScript	tsconfig.json, .ts
JavaScript	package.json, .js, .mjs
Python	requirements.txt, pyproject.toml, setup.py, .py
Java	pom.xml, build.gradle, .java
Go	go.mod, .go
Rust	Cargo.toml, .rs
PHP	composer.json, .php
Ruby	Gemfile, .rb
C#	.csproj, .sln, .cs
Swift	Package.swift, .swift

Framework — top-level dependency in package.json (React, Next.js, Vue, Angular, Express, NestJS) or requirements.txt (FastAPI, Django, Flask).

Rest — presence of .git/, Dockerfile / docker-compose.yml, and lockfile shape (npm / yarn / pnpm / pip / poetry).

If detection guesses wrong, you can correct the context via CodeBuddy: Reset Workspace Analysis and re-run.