Claiming Workflow

A detailed walkthrough of the project claiming and provisioning process.

When you claim a project, several automated processes run to set up your development environment. This page walks through each step and explains what happens behind the scenes.

Multiple Workers Can Claim

Unlike some platforms, multiple workers can claim the same project. The client (or system) will choose which worker's work gets promoted to production.

From the Marketplace, click View on a project row to see the project details page. Review the Overview tab to understand what the project needs.

Click the Claim button. A Claim Quiz Modal appears asking you to confirm you understand the commitment. This ensures you're ready to work on the project.

After passing the quiz, the system checks if you have a GitHub account linked:

  • If linked – Proceeds to provisioning immediately
  • If not linked – A modal prompts you to link your GitHub account first

The system automatically provisions your development environment:

  1. GitHub Collaborator

    You're added as a collaborator to the repository.

  2. Branch Creation

    A branch named worker-[your-pseudonym] is created. If the build hasn't succeeded yet, branch creation may be deferred.

  3. GCP Provisioning

    You're added to the GCP project with editor permissions.

You'll see toast notifications indicating success or any issues. Common messages include:

  • "Branch will be created once the build succeeds" – Deferred branch creation
  • "Branch already exists - using existing branch" – You may have claimed before
  • "GCP provisioning failed" – Can be retried from the project page

After claiming, you have access to these resources:

ResourceDetailsWhere to Find It
Git Branchworker-[pseudonym]GitHub repo (link in project Quick Actions)
GCP AccessEditor roleconsole.cloud.google.com
Firebase AccessVia GCP permissionsconsole.firebase.google.com
Preview DeploymentsAuto-deploy on push"View Preview" button on project page
Full Project TabsPlan, PRD, Chat, etc.Project details page

If you need to stop working on a project, you can unclaim it:

  1. Go to the project page

    Navigate to the project from My Projects or the Marketplace.

  2. Click "Unclaim"

    In the hero section, click the Unclaim button.

  3. Confirm

    Confirm the unclaim in the dialog. You'll be removed as a GitHub collaborator.

Avoid Frequent Unclaiming

Only unclaim if absolutely necessary. Frequent unclaiming may affect your standing on the platform.

Common issues and solutions:

  • GitHub not linked – Link your GitHub account in Account Settings before claiming.
  • Branch not created – If the build hasn't succeeded, branch creation is deferred. Use the "Create Branch" button in the Workers section once the build succeeds.
  • GCP provisioning failed – Click "Provision GCP" in the Workers section to retry.
  • Repository access denied – Ensure your linked GitHub username matches your actual account exactly (case-sensitive).
Next Steps

Once claiming is complete, you're ready to start development! Learn about the development workflow to understand how to build and deploy your changes.