Quick Start
FlightDesk adds the team workflow around Claude Code: shared task visibility, preview environments, and QA handoff. This guide gets you from zero to your first task.
What You'll Need
- A GitHub account with at least one repository
- Claude Code installed and working on your machine
- Node.js 18+ (for the CLI)
Step 1: Create Your Account
Go to flightdesk.dev/register and sign up with your email or GitHub account. Email verification is required before you can log in.
Once verified, you'll land inside your organization dashboard.
Step 2: Connect GitHub
FlightDesk uses a GitHub App for secure, short-lived access to your repositories.
- Go to Settings → Organization → Integrations
- Click Connect GitHub
- Authorize the FlightDesk app on GitHub
- Select which repositories to grant access to
FlightDesk will immediately start receiving PR webhooks from those repositories. No manual webhook setup required.
Step 3: Create a Project
Projects link a GitHub repository to FlightDesk.
- Go to Projects → New Project
- Select your connected GitHub repository
- Give the project a name
- Save
Optionally configure preview environments at this step — you can always do it later in project settings.
Step 4: Install the CLI
The CLI connects your local development context to FlightDesk. Install it globally:
npm install -g @flightdesk/cli
Then authenticate:
flightdesk login
This opens a browser window to complete OAuth. Your credentials are stored in ~/.flightdeskrc.
Step 5: Create and Dispatch a Task
- Go to Tasks → New Task
- Select your project
- Write a title and description of what you want Claude Code to build
- Click Create
Then on the task detail page, click Dispatch. This marks the task as in-progress and generates a prompt you can paste into Claude Code.
Step 6: Work in Claude Code
Start your Claude Code session and paste the dispatch prompt. FlightDesk keeps the task, branch, PR, checks, preview link, and QA context together:
- Work starts → task moves through the workflow
- Branch created → branch name is synced
- PR opened → task moves to PR Open
- Preview ready → the live URL appears on the task
- QA ready → generate a test plan and assign review
What Happens Next
From here the task moves through preview, review, QA, and merge. See Task Workflow for a full explanation of every status and what triggers each transition.
Next Steps
- Set up Preview Environments for live PR previews
- Built-in Prompts to create QA test plans and handoff notes
- Connect SonarQube for supporting code quality feedback