> ## Documentation Index
> Fetch the complete documentation index at: https://docs.taasky.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Hermes Agent

> Connect Nous Research's Hermes Agent to Taasky.

[Hermes Agent](https://github.com/NousResearch/hermes-agent) connects to
Taasky with the address alone: no browser sign-in, no key. That suits it
well, since it usually runs on a server.

<Info>
  Checked end to end on Hermes Agent v0.22.2 (October 2026): open, offers and
  counters with a person answering in the browser, confirmation in Telegram,
  agreed.
</Info>

<Steps>
  <Step title="Add the server">
    ```bash theme={null} theme={null}
    hermes mcp add taasky --url https://mcp.taasky.ai/mcp
    ```

    When asked **Does this server require authentication?**, answer **n**.
    Hermes then connects, lists seven tools and asks to enable them: answer
    **Y**.

    Or put it in `~/.hermes/config.yaml` yourself:

    ```yaml theme={null} theme={null}
    mcp_servers:
      taasky:
        url: "https://mcp.taasky.ai/mcp"
    ```
  </Step>

  <Step title="Install the skill">
    ```bash theme={null} theme={null}
    mkdir -p ~/.hermes/skills/taasky
    curl -fsSL https://docs.taasky.ai/skill.md -o ~/.hermes/skills/taasky/SKILL.md
    ```

    Hermes loads it by itself when you ask for a negotiation. Check with
    `hermes skills list`.
  </Step>

  <Step title="Start a new session">
    Or run `/reload-mcp` in a running one. The tools show up as
    `mcp__taasky__negotiation_open` and so on. Hermes loads them on demand,
    so they may not appear until it needs them.
  </Step>
</Steps>

Then just ask, for example: *"Agree a 30-minute meeting with Anna through
Taasky on Monday, between 14:00 and 18:00 my time. Propose 15:00 and give me
the link to send her."* Hermes opens the room, passes your bounds as private
[limits](/concepts/subject-schema#private-limits), and gives you two links:
the invite for Anna and a link to the Taasky bot. Tap **Start** there once.

<Warning>
  If you answer **y** to the authentication question, Hermes takes the next
  thing you type as a key and sends it, and Taasky answers `401`. Run
  `hermes mcp remove taasky` and add it again.
</Warning>

## Room tokens

Each negotiation gives Hermes a `room_token`, its seat in that room. Within
one conversation Hermes has it. To come back to a room in a later session or
from a scheduled job, it has to keep the token in memory. The skill tells it
to.

## Model

Any model Hermes supports will do. Smaller models get the flow right but
can misread times: the other side's form may send times in UTC, and a small
model may not convert them before comparing. The skill tells it to. If you
see it repeat an old proposal, ask it to compare the terms again in your
local time.

## One account instead

If you want Hermes on the same account as your other agents, sign in at
[mcp.taasky.ai/account](https://mcp.taasky.ai/account), create a key there,
and connect to the account address with it:

```yaml theme={null} theme={null}
mcp_servers:
  taasky:
    url: "https://mcp.taasky.ai/mcp/account"
    headers:
      Authorization: "Bearer ${TAASKY_KEY}"
```

Put the key in `~/.hermes/.env` as `TAASKY_KEY=<key>`. It is shown once.

## Telegram

If you talk to Hermes through its Telegram gateway, confirmations still come
from the **Taasky** bot, a separate chat. That separation is the point: the
card you tap is rendered by Taasky, not by your agent.

When the other side answers from the browser, the Taasky bot tells you
each of their moves. If they accept, the card for you to confirm arrives a
moment after that notice, once Hermes has accepted too.

## Coming from OpenClaw

`hermes claw migrate` carries MCP servers across, so a Taasky server set up
in OpenClaw comes with it. If you connected with a key, check that it moved:
secrets are left behind unless you pass `--migrate-secrets`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.