Tenuo for Hermes Agent
Let Hermes work. Decide what it can do.
Give your Hermes agent signed, expiring permissions with Tenuo warrants: which tools it may call, which arguments it may use, and for how long. With Hands, connect your remote Hermes to a project on your Mac or Linux laptop while its memory and skills stay on the server.
| What do you want Hermes to do? | Start here |
|---|---|
| Run a task with clear limits on tools, files and duration | Try Tenuo warrants |
| Work in a local project from your existing remote chat | Try Hands |
| Wrap MCP servers you already use and trace scoped calls | Verify delegated MCP calls |
Use either feature on its own, or both together.
Try Tenuo warrants
Give a nightly report job access to its reports folder, let a researcher search without writing files, or give a delegated agent fewer permissions than its parent. The limits are checked before the tool handler runs.
A warrant is a signed permission slip with an expiry. Here is a shortened example from the runnable demo:
ALLOW read_file path=/data/reports/q3.csv
DENY read_file path=/opt/private/payroll.csv
DENY terminal command=ls
After expiry: DENY read_file path=/data/reports/q3.csv
See the checks run locally—no Hermes process or model API key needed:
uvx --refresh hermes-tenuo demo
Apply it to your Hermes: install and configure Tenuo,
mint a warrant for the task, and run hermes-tenuo doctor to check the configuration.
For example, this grants only web_search for one hour:
uvx hermes-tenuo mint --ttl 1h --allow web_search
The command prints the configuration and signing-key instructions. Apply them in the Hermes profile serving the task, check the configuration, and restart that profile. Installing the plugin alone does not activate tool authorization.
See a real-model prompt-injection walkthrough or explore argument constraints and delegation. Tool-call authorization checks the calls and arguments it covers; Hands adds an OS sandbox for work on the connected device.
Give your remote Hermes hands
Your Hermes lives on a server. Your project is on your laptop.
Open the Hermes chat you already use, connect a folder, and ask it to get to work. You keep the same agent, memory and skills. Hands needs no manually minted warrant.
From your chat to your local files
Ask Hermes:
Run the tests in this folder. Fix the invoice calculation without changing the tests, then rerun them.
The practice project gives you a small, visible result:
On your laptop In your existing Hermes chat
─────────────────────────────────── ─────────────────────────────
invoice.py + two failing tests ← Run the tests and inspect the code
invoice.py updated ← Fix the calculation
Two tests pass ← Run the tests again
def total_after_discount(subtotal, discount):
- return subtotal * discount
+ return subtotal * (1 - discount)
The edited file is on your laptop, ready for you to inspect. Your Hermes keeps its existing memory and skills. Then try your own project: investigate a test failure, review local changes, or write a script for files in the shared folder.
You choose the folder and how long to share it. Internet access is off by default. Press Ctrl-C on your laptop to end access. Commands and results are sent to your remote Hermes and its model; keep private files out with personal exclusions.
Try Hands
You'll need a running Hermes with terminal-provider and tool-middleware support, and a Mac or Linux laptop with Python 3. macOS uses its built-in sandbox; Linux needs bubblewrap. Hands supports terminal and file work, not GUI or browser control.
1. Server — install and connect once.
hermes plugins install tenuo-ai/hermes-tenuo
hermes plugins enable hermes-tenuo
Leave the optional credential prompts empty. Enable installs the dependencies. Follow the Tailscale connection setup to connect the server and laptop, then restart the Hermes gateway/profile serving your chat. An existing HTTPS endpoint works too; the guide covers both.
2. Laptop — create a practice folder.
Install uv if needed:
uvx --refresh hermes-tenuo --version
uvx hermes-tenuo hands demo
Check that the version is 0.4.0 or newer. Follow the printed cd command.
The demo creates a new temporary project; it does not change your existing files.
3. Hermes chat — connect this folder.
Run /hands setup edit. Copy the command it prints into your laptop terminal
inside the practice folder. This shares the project for one hour, with internet off.
Keep that terminal open, then run /hands verify in the same chat.
4. Hermes chat — ask for the fix.
Run
python3 -m unittest -vin the shared folder. Fix the invoice calculation in invoice.py without changing the tests, then rerun the tests.
Inspect the local change. When you're done, press Ctrl-C in the laptop's
sharing terminal, then /hands off in chat to return tools to the server.
/hands off alone changes routing; it does not end the laptop grant.
Troubleshooting and the full walkthrough →
Keep using the Hermes you know
Hands adds a local workspace to your existing remote Hermes. Your laptop connects outward, so it needs no incoming port or SSH server. You approve the connection locally and can switch the conversation back to server tools when you're done.
Hermes also supports SSH terminal backends. Hands is useful when you want to connect a laptop temporarily, choose the folder locally, and attach it to one conversation. Browser and MCP tools stay on the server.
For read-only work, use /hands setup read. If a task needs network access,
choose /hands setup online explicitly. Linux online shares also require
Landlock ABI 6. Secret redaction is best effort; exclude files that must not be
sent to Hermes or its model.
More
- Hands settings, platform requirements and troubleshooting
- Warrants, tool authorization, delegation and advanced configuration
- Changelog
Hands ships in hermes-tenuo, the Tenuo plugin for Hermes Agent. Apache-2.0 license.
Metadata
Release files for hermes-tenuo 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| hermes_tenuo-0.4.0.tar.gz | 411.8 kB | With provenance | Details for hermes_tenuo-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hermes_tenuo-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for hermes_tenuo-0.4.0-py3-none-any.whl |
Total release size: 582.5 kB
Release files / hermes_tenuo-0.4.0.tar.gz
| Download URL | hermes_tenuo-0.4.0.tar.gz |
|---|---|
| Size | 411.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e3b32b45cb2b04ef54736e74d0053d29fca1e69f9141be7d04cf9527a37e6a99
|
|
BLAKE2b-256 checksum How to use checksums |
f9b4130a2928e76e03385942a2644f394d4d050201a34ea6479bb64b4136d674
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / hermes_tenuo-0.4.0-py3-none-any.whl
| Download URL | hermes_tenuo-0.4.0-py3-none-any.whl |
|---|---|
| Size | 170.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6f2115c1f83fbf5c397d8124f0772255980a05cc8c7027b3882317ee6ad95736
|
|
BLAKE2b-256 checksum How to use checksums |
af64b06b5bb92ea5cdbe9d0c6ba02f32cb5eb7ab73386661539cc225ead6ac64
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logSecurity for hermes-tenuo 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for hermes_tenuo-0.4.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.