- name
- ghapp
- description
- Give your AI agents and automations their own GitHub (App) identity. Authenticate using GitHub Apps so every commit, PR, and action is attributed to the bot — not your personal account.
- homepage
- https://github.com/operator-kit/ghapp-cli
- metadata
- {"clawdbot":{"emoji":"🔑","requires":{"bins":["ghapp"]},"install":[{"id":"brew","kind":"brew","formula":"operator-kit/tap/ghapp","bins":["ghapp"],"label":"Install ghapp (brew)"}]}}
ghapp
Use ghapp to authenticate as a GitHub App so git and gh commands use installation tokens. Requires a GitHub App with App ID, Installation ID, and a private key (.pem).
Setup
ghapp setup— interactive wizard: enter App ID, Installation ID, key path, then configure authghapp auth configure— configure git + gh authentication (if skipped during setup)ghapp auth status— show current auth config and diagnostics
Commands
ghapp --help— list all commands and flagsghapp token— print an installation token (cached;--no-cachefor fresh)ghapp auth configure [--gh-auth shell-function|path-shim|none]— configure how git/gh authenticateghapp auth status— check auth healthghapp auth reset [--remove-key]— undo all auth configghapp config set,ghapp config get [key],ghapp config path— manage configghapp update— self-update to latest releaseghapp version— print version
gh auth modes (passed to auth configure)
shell-function— auto-authenticates gh commands via shell integration (recommended)path-shim— wrapper binary for CI/containersnone— static token in hosts.yml
Notes
- After setup,
git clone/push/pullandghwork without manual tokens. - Commits are attributed to the app's bot account (e.g.,
myapp[bot]). - Tokens are cached locally and auto-refreshed.
- Config stored at
~/.config/ghapp/config.yaml.