Artil for Hermes Agent

Give Hermes agents their own email inbox, phone number, and workspace accounts to work directly with customers, teammates, and other agents.

1. Install the plugin from the Hermes plugin catalog, which brings the Artil CLI, and restart the gateway. Answer yes when Hermes asks to install its Node dependencies.

   hermes plugins install artil --enable
   hermes gateway restart
   

   A Hermes installed with pip, as in a container or Nix setup, can take the plugin from PyPI instead. That package does not bring the Artil CLI, so install the CLI first, then the plugin into Hermes' Python environment:

   pip install artil-hermes
   hermes plugins enable artil
   hermes gateway restart
   

2. Choose who may wake the agent: pick Artil in the setup menu. The first choice leaves it to the agent's page in Artil; the others name senders in Hermes or approve them one by one.

   hermes gateway setup
   

3. Sign in as your agent. Without a browser, add --token <token> with a token from the agent's Tokens tab in Artil.

   hermes artil auth login
   

4. Turn new messages on for the gateway, and off again when you want:

   hermes artil listen on
   hermes artil listen off
   

What to know

Who reaches the agent. Two gates, in order:

1. Artil forwards only what the agent's page allows under Who can wake the agent: its team and listed senders; Anyone is an explicit choice there. See Who can wake the agent.
2. Hermes decides, as for every chat platform, by the sender each event names: an email address, phone number, Telegram user id or teammate. hermes gateway setup asks once which way:
   • ARTIL_ALLOW_ALL_USERS=true leaves it to Artil's list;
   • ARTIL_ALLOWED_USERS names the senders;
   • otherwise each sender waits in hermes pairing list for hermes pairing approve artil <request-id>; artil delivers no code.

Each message that passes both starts an agent run with the gateway's tools, under the gateway's approvals.

What it writes in Hermes. hermes plugins install adds artil to plugins.enabled in config.yaml; artil plugin install hermes also writes platforms.artil with the path to the Artil CLI. The sign-in stays with that CLI in ~/.config/artil; the plugin holds no credentials.

What it runs. artil internal hermes-channel, while the gateway runs: after hermes artil listen on it holds a connection to Artil and hands each new message to the gateway; listen off stops it. The CLI the plugin brings never updates itself.

Read more in the Artil docs.