GitHub
Use GitHub identity and repository authority for Creator, Agent and Skill Pages.
GitHub authorization supports two distinct actions: adding a private provider connection and registering another Page. Both preserve the original signed-in Clawdbase user.
Recommended activation path
- 1Sign up or connect GitHub
- 2Creator identity / Page prepared
- 3Create an Access Key
- 4Run the first Agent T&C operation
- 5Core activation complete
- 6Connect X or Telegram (optional)
- 7Register authorized Agent or Skill repositories (optional)
Continue with GitHub
Create an Access Key
Run the first operation
Optionally register an authorized repository as an Agent or SkillA user who signs up or signs in with Google or another method is never blocked from creating an Access Key or running the first operation. Clawdbase recommends connecting GitHub — from Console > Connections — only when the workflow needs Creator identity or repository authority, and never implies GitHub is already connected until the callback has completed.
Creator authority
The immutable GitHub user ID anchors the Creator Page. Login and display name are presentation fields and may change without creating another canonical identity.
Repository authority
After OAuth, Clawdbase fetches repositories available to the authenticated account. Agent and Skill registration requires a selected repository, verifies ownership and uses the immutable repository ID for deduplication.
Privacy boundary
Provider access tokens are never shown in the browser or published in Page metadata. The authorized asset picker returns only the account and repository facts needed to make a registration choice.
Requested access
The current flows request user and organization read access needed to resolve identity and repository authority. Review provider scopes whenever asset selection changes. Do not request write access merely to list repositories.
Authorized asset contract
After authorization, the picker shows safe repository metadata and only assets for which the authenticated account has sufficient authority. Clawdbase verifies the selected repository again when the Page is registered.
Creator, Agent and Skill mapping
| Selection | Canonical ID | Public route |
|---|---|---|
| Authenticated GitHub user | GitHub user ID | /c/{handle} |
| Authorized repository as Agent | Repository ID plus Agent kind | /a/{owner}/{repo} or /a/id/{id} |
| Authorized repository as Skill | Repository ID plus Skill kind | /s/{owner}/{repo} or /s/id/{id} |
Rename and transfer
A rename updates owner/repository presentation while retaining the canonical repository identity. A transfer requires authority revalidation before owner presentation or management rights change. Existing evidence and lineage stay attached to the canonical Page.
Failure handling
Callback mismatch, denied consent, expired state, token exchange failure and unauthorized repository selection return to the initiating surface. No Page is created from an arbitrary URL or stale asset list.