How do I link GitHub with Ergod?
Linking GitHub is a Personal Access Token, validated against GitHub before it is stored and encrypted at rest; from then on Ergod can commit, push and open PRs on your behalf. /secrets stores other provider tokens the same way, each exposed to the bash tool as $<PROVIDER>_TOKEN for the turn, owner-scoped so collaborators and room members do not inherit them. Signing in with GitHub on the dashboard is a different thing: that is identity, this is a token.
6 commands in 2 groups; all of them are Discord-only today, because they act on a server. Most days you will not type any of them: @Ergod and plain English is the normal way in.
Link a GitHub account so Ergod can commit, push, and open PRs on your behalf.
Once, before the first task that touches a repo: /github link with a personal access token, validated against GitHub and encrypted at rest. After that git and gh run inside your sandbox as you; there is no separate GitHub tool. /github whoami checks the link, /github unlink deletes the token immediately. Example: /github link token: ghp_…
Connect a GitHub account with a Personal Access Token. Validated against GitHub before storing, then encrypted at rest.
Disconnect your GitHub account. The stored token is deleted immediately.
Check your linked GitHub account.
Store provider tokens (npm, PyPI, DockerHub, Hugging Face, custom) that Ergod's bash tool can read as $<PROVIDER>_TOKEN. Same encryption + scope as GitHub.
When a build needs to publish somewhere that wants a token: npm, PyPI, Docker Hub, Hugging Face or a custom name. /secrets link stores it, encrypted, and the agent's shell reads it as an environment variable; /secrets list shows what is stored without showing values; /secrets unlink removes one. Example: /secrets link provider: npm token: npm_… label: ci-publish.
Store a token for any provider — npm, PyPI, DockerHub, Hugging Face, or any custom name. Exposed to your bash tool as $<PROVIDER>_TOKEN per turn. Encrypted at rest with the same Fernet key used for GitHub tokens. Owner-scoped — collaborators and channel-session participants do not inherit.
Remove a linked secret. Token is deleted immediately.
Show your linked secrets — provider, label, when added. Token values are NEVER shown.