YOUR IDEAS. YOUR APP.
Let’s get you connected.
Sign in with GitHub, set up your company and its token, choose a repository, and get your project ready for critter.
01 / YOUR ACCOUNT
Continue with GitHub
Use GitHub to sign in or create your critter account.
Sign-in identifies your GitHub account and email. Repository access is a separate step for one private repository you own; no organization access is requested.
Signed in with GitHub
Account details
Sign-in identifies your GitHub account and email. Repository access is a separate step for one private repository you own; no organization access is requested.
Loading sign-in…
02 / YOUR COMPANY
Invites
Other companies invited your GitHub email. Connect account hands that company’s token to the critter extension.
Members and details
critter is used per company. The company token is what the critter extension asks for before its GitHub sign-in; share it with your team. Connect account hands it to the critter extension when its side panel is open in this browser. An invite emails the token and the setup steps to a teammate. The free plan covers two active people: the earliest to join who are still active hold the seats, and anyone else from the company is paused in the extension until critter Pro. The owner can remove a member here; a member can leave from the extension. Either frees the seat right away.
Members
03 / YOUR REPOSITORYChoose one repository (optional)
You can skip this step. GitHub’s standard sign-in cannot grant access to a single repository: its only repository permission covers every repository on your account, so critter does not ask for it. Sign-in gives critter your identity and email, nothing more. Repository access is a separate choice you make for one repository — with a fine-grained token here, or in the extension.
Coming next: signing in through the critter GitHub App, where GitHub itself asks which repositories it may see (“Only select repositories”) and you choose from that list.
When you install the critter GitHub App, GitHub asks which repositories it may see — choose Only select repositories. critter never lists or reads the rest.
Sign in again to list the repositories you gave the critter GitHub App; GitHub shows what it may see and you pick one.
Check one repository with a fine-grained token
Use a private repository owned by your personal account. Create a fine-grained token on GitHub ↗. Choose your personal account as Resource owner, then Only select repositories and select this one repository. Leave account permissions unset. Metadata read access is enough for this setup check. For the extension’s edits and draft PRs, also allow Contents and Pull requests: read and write, plus Checks and Commit statuses: read.
04 / PROJECT SETUP
- Use the matching extension and runner from the local setup page.
- Start the app and runner in a dedicated local checkout.
- Pair the extension using the runner’s private address and token.
This early version runs locally. Shared team runtimes and automatic repository connection are still being built.