Test Drive

From its catalog listing

Don't guess which plugin helps. Test-drive it. When Hermes hits a capability wall (it says it can't, or a tool fails as unavailable) test-drive appends one line naming the best catalog match; /testdrive <need> and test_drive_find show the top 3 with trust cards (tier, pin, keys needed, declared tools/hooks, disclosure); after you approve, test_drive_run or /testdrive run installs the candidate into a throwaway HERMES_HOME, runs your original request once with hermes chat -q, attempts cleanup and reports a before/after with tool-call evidence when available; keep goes through Hermes's own installer; /testdrive history keeps receipts.

Good to know before installing

fetches the public catalog index from hermes-agent.nousresearch.com (redirects only to https Nous hosts, cached 6 h); an approved drive installs the selected catalog repository and pin by URL through Hermes, whose custom-source scanner may block caution verdicts, and installs its Python dependencies from PyPI into the sandbox's own runtime, runs child hermes CLI processes (plugins install, chat -q, sessions export, gateway stop) with hard timeouts and process-group kill, sends your request to your configured model provider (twice with a baseline), and runs the candidate's code as your user inside the temporary profile (not an OS sandbox), including any network calls it makes; every test_drive_run is escalated to Hermes's approval gate (fails closed unattended) and the slash command asks via ask_choice or an explicit --yes; the child runs single-query mode with dangerous commands denied; the child gets only system env vars plus your model route's key and the candidate's declared requires_env, read through agent.secret_scope (literal credential fields are stripped from the model and provider config written to the sandbox's 0600 config.yaml; a drive whose key exists only as a literal is refused); no memory, sessions, .env or auth.json are copied; temp dirs hermes-testdrive-* are removed after drives when cleanup succeeds; cleanup failures are reported; stores the catalog cache, last gap per session and up to 50 drive receipts in its plugin-data folder; a transform_llm_output hook appends one nudge line to gap replies (off with nudges: false); optional llm_check calls your active model; no telemetry.

From its catalog listing.

How to install

  1. Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
    hermes plugins install test-drive
  2. Said no? Turn it on later:
    hermes plugins enable test-drive
  3. Restart Hermes so it loads the plugin.

Some plugins also need a sign-in or settings: see Full setup & settings. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide (opens in a new tab).

Category
Coding & developer tools
Maintained by
Xuefeng-Zhu (Community)
Needs
No API keys declared
Adds tools
test_drive_find test_drive_run test_drive_keep
Adds hooks
pre_tool_call pre_llm_call post_tool_call transform_llm_output
Needs Hermes
0.22.7 or newer
Version
0.1.0
In the catalog
2026-11-12

Known issues (from its catalog listing)

  • A test drive takes about 30-90 s and spends model tokens; plugins that need OAuth sign-ins, a messaging platform, the Desktop app, hardware or keys you don't have can't show their value in a throwaway profile (missing keys are reported and the run is skipped).
  • Models that sign in with OAuth (Nous Portal, Codex) are not reused in the sandbox; set test-drive's sandbox_provider/sandbox_model/sandbox_key_env to an API-key route.
Using the Hermes desktop app? See where plugins live
Hermes desktop Capabilities page, Plugins tab filtered to Official plugins built by Nous Research, each with an add button.
The official plugin catalog built into the app.Hermes desktop v0.22.5 · Capabilities > Plugins · Windows · captured Nov 1, 2026

Full setup & settings ↗Source code ↗

More in coding & developer tools

All coding & developer tools plugins

New Hermes Agent updates every day on X. Follow @HermesWatcher

← All plugins