Set up FeatureFast

Account setup

Six steps to connect a repo and have FeatureFast turn customer requests into pull requests.

The guided way

The in-product onboarding walks you through every step below, detects what's already done, and verifies the whole thing with one real run. These docs mirror it so you know what to expect.
Start onboardingGo to dashboard

1. Name your project

A project is just a label for one app or website in your dashboard. Pick anything — you can rename it later in Settings. Everything else (your public projectId and secret key) is generated for you when the project is created.

2. Connect your GitHub repo

FeatureFast needs access to one repository so it can open pull requests with the changes your customers ask for. Install the FeatureFast GitHub App and pick the repo for this project. You can revoke access at any time from GitHub's own settings.

3. Pick the target branch

Choose the branch pull requests should target. FeatureFast defaults to your repo's default branch (usually main), but you can point it at staging, develop, or any other branch if you'd rather review changes there first.

4. Add your Claude Code token

FeatureFast uses Claude Code to write the changes your customers request — it runs inside your repo on your own Claude subscription, so we never bill you per request. Generate a long-lived token with claude setup-token (it starts with sk-ant-oat01-) and paste it in; we store it as the CLAUDE_CODE_OAUTH_TOKENsecret in your repo for you — you don't need to open GitHub.

This needs a Claude Pro or Max plan. See Claude Code token help if you get stuck. Note: a token starting with sk-ant-api is an API key, not a Claude Code token — those won't work here.

5. Install the workflow

FeatureFast adds one small file to your repo — .github/workflows/featurefast.yml — that runs the AI when a request comes in. We prepare it as a pull request; you just click Merge pull request and then Confirm merge. Nothing else in your repo changes, and FeatureFast detects the merge automatically.

6. Allow third-party Actions & verify

If GitHub blocks the workflow, open your repo's Settings → Actions → General and choose Allow all actions and reusable workflows, plus Read and write permissions under Workflow permissions. Then run the one-time verification — a real check that your token works, GitHub Actions can run, and the AI can reach your repo — before a real customer ever hits it. No code is changed.

Next: drop the widget into your app so customers can actually submit requests. Pick React & Next.js for an authenticated app, or static & marketing sites if there's no login.