Use a GitHub App bot identity
Instead of an agent acting on GitHub as a connected human, it can act as a machine identity (agentvalet[bot]) that gets a fresh, narrowly scoped token for every call. For the reasoning, see GitHub App bot identity.
This is an early capability. Completing the bot install currently involves AgentValet, and today only your organisation’s primary owner sees the bot as an “Acts as” option. If it is not yet enabled for you, contact AgentValet.
Install the bot
On the Platforms page, find GitHub. Alongside the usual Connect button, GitHub shows a Connect as Bot (GitHub App) action. Clicking it opens the Install GitHub App dialog, which lists the permissions the install will grant:
- Contents: read and write
- Pull requests: read and write
- Metadata: read
The dialog explains the key guarantee: the install grant is the ceiling, and each agent call gets a one-hour token scoped to one repository and one permission, so no single request can exceed what you approved.
Click Install on GitHub. You are handed to GitHub, where you choose which repositories the bot may access. On return, a successful install shows “GitHub bot installed. Your agent can now authenticate as agentvalet[bot].”
If your account is not permitted to complete the install, the request is refused. This is the current preview limitation: reach out to AgentValet to have the bot installed for your organisation.
Point an agent at the bot
Open the agent’s detail page. On its GitHub permission row you will see an Acts as selector. The options are:
Owner default- Any connected GitHub account, shown by its label
agentvalet[bot](shown only when the bot is installed for your org)
Pick agentvalet[bot]. The change saves as soon as you select it (there is no separate save button), and you will see “GitHub identity updated”. The agent now carries an agentvalet[bot] badge, and its GitHub calls run as the bot.
Changing the identity does not change the scopes the agent holds. It only changes which credential its calls use. Only an admin can change it.
Manage or remove the bot connection
The bot connection appears on the Platforms page as a distinct Bot identity row showing the account and repository selection, with Refresh and Disconnect actions. Use Refresh if the installation changes on GitHub’s side; if it reports the installation was not found, reinstall to restore bot access.