Hermes on Cua Spaces

What Hermes on Cua Spaces does

With the plugin enabled, each command, file read, file write and code run lands in a Cua Space instead of on your computer. A Space can be a Linux, macOS or Windows machine on your own hardware or in your own cloud account. Because the Space is the sandbox, Hermes skips its risky-command prompts for Spaces the plugin creates, and keeps asking for a Space you named yourself.

By default each Hermes run creates its own Space and deletes it on exit, so concurrent runs never share files. Settings such as space, on, image, delete_on_exit and create_timeout live under plugins.entries.cua-spaces.settings in config.yaml, or can be overridden per shell with HERMES_CUA_SPACE, HERMES_CUA_ON and HERMES_CUA_IMAGE.

The plugin stores no token or key; it uses the sign-in saved by cua auth login.

Key features

• Terminal, file and code tools run in an isolated Space
• Linux, macOS or Windows Spaces
• Per-run Spaces deleted on exit, or one reused Space
• Existing Spaces can be named and are never deleted
• Settings stored in Hermes config.yaml
• No tokens stored by the plugin

When to use it

• Letting Hermes run risky commands without touching your own machine
• Watching an agent's terminal work live in a Space
• Testing on a Windows Space from Hermes

Who it is for: Hermes Agent users who want agent commands sandboxed in a disposable, watchable machine.

How it fits with Hermes Agent

It is a Hermes Agent plugin that sets terminal.backend to cua.

How to install Hermes on Cua Spaces

These commands are copied from the project's README. Check the repository for the latest steps before you run them.

curl -fsSL https://cua.ai/install.sh | sh
cua auth login
hermes plugins install https://github.com/trycua/hermes-cua-spaces
hermes config set terminal.backend cua

Requirements: Hermes Agent, the Cua CLI and its cua Python package; a cua.ai sign-in for cloud Spaces

Note: Spaces on a cua.ai account require signing in, while a local Space needs no sign-in.

FAQ