GitHub Repository Access
Get your app's code onto your machine and give people access to its GitHub repository.
Every Stardeck app is backed by a private GitHub repository in the stardeck-customer-apps
organization.
Get the code locally
- New app:
npx @stardeckai/cli@latest newcreates the app and clones it for you. See Create an App. - Existing app:
npx @stardeckai/cli@latest clone <app-slug>clones it and runs setup. See Run Your App Locally. - Existing app, through your agent: with the org MCP server
connected, ask it to clone the app. It calls
get_repo_accessfor a clone URL with a token. See Work Across Every App. - Your own GitHub account: add yourself as a collaborator (below), then clone as usual.
What the clone token can do
The token your agent receives is for one repository and carries only repository contents access (plus read-only metadata). It lasts about an hour; when git answers 401/403 afterwards, your agent asks for a new one and you confirm again. It is meant to be used for a single push, not stored.
It can push only to branches named agent/... or starcat/.... GitHub rejects the default branch
and every other name, so code reaches the default branch through a pull request that a person
merges. If the platform's push credential is not set up, the token is read-only and your agent is
told so. Production deploys also need your confirmation.
Use your own GitHub account (optional)
If you want to push with your own GitHub login instead of a token, your agent can run
gh api user --jq '.login' to read your GitHub username, show it to you, and, only after you
confirm, invite that account with Write access. Accept the invitation on GitHub. Stardeck
removes this access (and cancels a pending invitation) when you leave the organization or lose
write access to the app. Access your account already had is never touched. Your account can push
any branch, but the default branch changes only through a pull request. If Stardeck cannot confirm
that protection, it does not send the invitation.
Add a collaborator
- Open the app and go to Settings → Repository → Repository access.
- Click Add GitHub User and enter the exact GitHub username.
- Pick a permission and click Add Collaborator.
| Permission | Can |
|---|---|
| Read | View and clone |
| Write | View, clone and push |
| Admin | Everything, including repository settings and managing access |
GitHub emails an invitation. The row reads Pending invitation acceptance until the user accepts
it at github.com/stardeck-customer-apps/<repo>.
Manage collaborators
- Refresh (refresh icon) pulls the current list from GitHub, including invitations accepted and people added on GitHub directly.
- Remove (trash icon) revokes access, or cancels a pending invitation, immediately. You can re-invite later.
- Rename the repository inline in the GitHub repository section on the same page.
If a collaborator can't see the repository, the invitation is usually unaccepted, expired (remove and re-invite), or sent to a different GitHub account.
Next
Run Your App Locally
Pull the app's environment and start it on your machine