Hermes Agent's pair mechanism is to give unfamiliar users an entrance to "apply first and then release". The default scenario is usually: the other party first privately sends a private message to the bot, and the bot returns a one-time matching code, and then you manually approve it on the server.
Basic process
- Users who are not in the allowlist DM bot.
- Hermes returns a string of pairing code.
- You perform
hermes pairing approve <platform> CODEon the machine. - The user can then continue the conversation with Hermes.
Common commands
hermes pairing approve telegram XKGH5N7P\nhermes pairing list\nhermes pairing revoke telegram 123456789When is pair appropriate?
Ideal for personal assistants, small team testing, and when you don't want to go to the background of each platform to find the user ID first. It is not suitable to use it as a "public registration portal", because the bot itself has tool permissions, and after pairing, it is a real access authorization.
The official documentation also states that the pairing code has an expiration time, will be frequency limited, and is disposable. This means that it can replace "write allowlist in advance", but not "approve the action itself".
In a word: the value of pair is to lower the threshold for first authorization, not to open Hermes Agent directly to anyone to self-register.
Official open source address: https://github.com/NousResearch/hermes-agent; Official document entry: https://hermes-agent.nousresearch.com/.
