Patchsmith
From its catalog listing
Adds `implement_task` and `apply_patch`. The first hands a single well-specified coding task to a local model served through Ollama (the measured backend) and returns the resulting diff. Propose mode runs in an isolated temporary checkout, preserves the source checkout, and saves a full patch for review. The second tool applies an approved saved patch only after hash, base, affected-file and path checks. The local model works inside a fixed toolset with no shell (read, grep, glob, git status/diff, write/edit, run the configured test command, finish) under hard turn and total token budgets shared across up to three fresh-context attempts. An optional local model is used only on the final allowed attempt; failures return a factual handback. Includes a path jail, read-only test files, an auto-finish when tests go green, a repeat-call guard, and revert of partial edits when a run is blocked. Your main model spends tokens only on the instruction and the returned diff.
Good to know before installing
runs git and the owner-configured test command (PS_TEST_COMMAND, never chosen by the model; it executes project code on the host) as subprocesses in the working directory with a minimal child environment plus an owner passthrough list (PS_ENV_PASSTHROUGH); in direct mode a local model writes implementation files inside the given workdir (never .git, node_modules, test files, .env* or .ssh/; the Hermes home, the user home and filesystem roots are refused as workdirs) and a run transcript with file excerpts under <workdir>/.patchsmith/; propose mode copies the checkout to a temporary Git worktree and keeps the patch, provenance record and transcript under <hermes home>/plugin-data/patchsmith/proposals/, with run summaries under <hermes home>/plugin-data/patchsmith/runs/. Task text and file contents go only to the local model endpoint set in PS_ENDPOINT (loopback or private-network address; public and link-local hosts refused). inspect_hardware runs fixed OS probes (nvidia-smi, sysctl, system_profiler, PowerShell CIM) and reads the endpoint's model list. No telemetry, no self-update, no stored credentials.
From its catalog listing.
How to install
- Install it. Hermes asks for any API keys it needs (this one needs
PS_ENDPOINT,PS_MODEL,PS_MAX_TURNS,PS_CTX_BUDGET,PS_ENV_PASSTHROUGH,PS_TEST_COMMAND), then asks whether to turn it on.hermes plugins install patchsmith - Said no? Turn it on later:
hermes plugins enable patchsmith - 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
- Bart Porcincula (Community)
- Needs
PS_ENDPOINTPS_MODELPS_MAX_TURNSPS_CTX_BUDGETPS_ENV_PASSTHROUGHPS_TEST_COMMANDAPI keys- Adds tools
implement_taskapply_patchtask_statusinspect_hardware- Needs Hermes
- 0.23.0 or newer
- Version
- 0.1.1
- In the catalog
- 2026-11-10
Using the Hermes desktop app? See where plugins live

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