All plugins

tinfoil-sandbox

A tinfoil terminal backend: Hermes' terminal, file and code tools run inside your own Tinfoil Container, an attested enclave, reached over the Tinfoil CLI's attested SSH tunnel. Select it with terminal.backend: tinfoil and terminal.tinfoil_container. Needs a Tinfoil organization with Containers enabled; the public template https://github.com/counterposition/hermes-tinfoil-workspace sets up a suitable workspace. Dangerous-command approval stays on, and the plugin never creates, starts, stops or bills containers. Disclosure — every tool call runs the user's installed tinfoil CLI (tinfoil ssh) and OpenSSH client as subprocesses; the CLI contacts Tinfoil's control plane to look the container up, then the enclave. The plugin passes TINFOIL_API_KEY, read through Hermes' secret scope, to the CLI as the tunnel key, and the admin key when set (TINFOIL_ADMIN_KEY, or an admin_ key in TINFOIL_API_KEY, which the CLI also accepts); beyond those the CLI and ssh get only an allowlist of Hermes' environment (PATH, home, temp, user, locale, SSH agent socket, certificate and HTTP proxy settings, the CLI's TINFOIL_CONTROLPLANE_URL and TINFOIL_CONFIG, Windows system directories). It never reads the CLI's saved login, and strips TINFOIL_API_KEY, TINFOIL_TUNNEL_API_KEY and TINFOIL_ADMIN_KEY from the environment of commands the agent runs. An SSH control socket under the system temp directory (hermes-tinfoil/) keeps the verified connection open for five idle minutes. A pre_tool_call hook rewrites a leading ~ in the path argument of read_file, write_file, patch and search_files to the container's home directory, only while terminal.backend is tinfoil, because Hermes otherwise expands it to the host's home. No telemetry.

counterpositionToolsv0.1.0Updated 6 days ago

About

A tinfoil terminal backend: Hermes' terminal, file and code tools run inside your own Tinfoil Container, an attested enclave, reached over the Tinfoil CLI's attested SSH tunnel. Select it with terminal.backend: tinfoil and terminal.tinfoil_container. Needs a Tinfoil organization with Containers enabled; the public template https://github.com/counterposition/hermes-tinfoil-workspace sets up a suitable workspace. Dangerous-command approval stays on, and the plugin never creates, starts, stops or bills containers. Disclosure — every tool call runs the user's installed tinfoil CLI (tinfoil ssh) and OpenSSH client as subprocesses; the CLI contacts Tinfoil's control plane to look the container up, then the enclave. The plugin passes TINFOIL_API_KEY, read through Hermes' secret scope, to the CLI as the tunnel key, and the admin key when set (TINFOIL_ADMIN_KEY, or an admin_ key in TINFOIL_API_KEY, which the CLI also accepts); beyond those the CLI and ssh get only an allowlist of Hermes' environment (PATH, home, temp, user, locale, SSH agent socket, certificate and HTTP proxy settings, the CLI's TINFOIL_CONTROLPLANE_URL and TINFOIL_CONFIG, Windows system directories). It never reads the CLI's saved login, and strips TINFOIL_API_KEY, TINFOIL_TUNNEL_API_KEY and TINFOIL_ADMIN_KEY from the environment of commands the agent runs. An SSH control socket under the system temp directory (hermes-tinfoil/) keeps the verified connection open for five idle minutes. A pre_tool_call hook rewrites a leading ~ in the path argument of read_file, write_file, patch and search_files to the container's home directory, only while terminal.backend is tinfoil, because Hermes otherwise expands it to the host's home. No telemetry.

Tinfoil Container backend for Hermes Agent

A terminal backend plugin: Hermes' terminal, execute_code and file tools
run inside a Tinfoil Container, your own
image in an attested enclave.

hermes plugins install counterposition/tinfoil-hermes-provider/sandbox
hermes plugins enable tinfoil-sandbox
hermes config set terminal.tinfoil_container my-box
hermes config set terminal.backend tinfoil

Requirements, settings and limits are in the
repository README.

How it works

  • provider.py registers the backend name tinfoil and answers Hermes'
    questions about it: where commands run, whether it is set up, what
    hermes doctor should show.
  • environment.py runs each command as
    tinfoil ssh <container> -- <ssh options> bash -c <command>. The Tinfoil
    CLI verifies the enclave's attestation and tunnels SSH over that verified
    TLS connection. An SSH control socket under the system temp directory keeps
    the connection open between commands.
  • The first connection also pins the SSH port. Without it the CLI logs a
    port notice before every command, and that line would corrupt the output
    Hermes' file tools parse.
  • A pre_tool_call hook rewrites a leading ~ in file-tool paths to the
    container's home, which Hermes would otherwise take from this machine.
  • The plugin has no Python dependencies and makes no network calls of its
    own. It runs two programs you installed: tinfoil and ssh.

README from the reviewed commit cae6859; it updates when the author re-pins.

More by counterposition

2 plugins by counterposition in the catalog.

counterpositiontinfoil-providerTinfoil confidential inference as a Hermes model provider. Open-weight models from Tinfoil's live catalog (Kimi, GLM, gpt-oss and others) run in attested hardware enclaves that neither the cloud host nor Tinfoil can read. Hermes reaches them only through Tinfoil's local tinfoil-proxy, which verifies the enclave's attestation and pins its TLS key before forwarding anything; there is no fallback to an unverified connection. The proxy starts on demand. Disclosure — Hermes sends requests, including a /v1/models read for the model list, only to the local proxy (127.0.0.1:3301, or TINFOIL_BASE_URL); the proxy is what contacts Tinfoil. When nothing listens on the proxy's port, the plugin starts the user's installed tinfoil-proxy binary in its own session and leaves it running after Hermes exits, logging to proxy.log in the plugin's data directory; it never downloads a binary, and TINFOIL_PROXY_AUTOSTART=0 turns this off. The proxy inherits only an allowlist of the environment (PATH, home, temp and user, locale and time zone, SSL_CERT_FILE/SSL_CERT_DIR, HTTP(S)_PROXY/NO_PROXY, and Windows system directories); every other variable, including all TINFOIL_* variables, is withheld. TINFOIL_API_KEY is read through Hermes' provider profile and sent to the proxy as the request's bearer token. The plugin writes catalog.json (the last model list it saw) and proxy.log under its plugin-data directory, registers no tools, hooks or middleware, and sends no telemetry.Communitymodels

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section