Load Lock

From its catalog listing
A machine-wide load broker for coding agents: Hermes, Claude Code, OpenCode, Codex, Cursor and any MCP client share one heavy-work budget, so builds and test suites take turns instead of thrashing the machine. 19 load_lock_* tools (acquire, queue, offers, honest waits, background jobs that release their permit on exit, machine inspection), a policy brief at session start, a Load Lock dashboard tab, and a Desktop pane, status-bar chip and palette command.
Good to know before installing
every tool shells out to the local load-lock CLI (Node >= 20, installed separately with npm), which auto-starts a per-user background daemon on a Unix socket with state in ~/.local/state/load-lock; load_lock_run_with_permit runs the command the agent passes on this host in its own process group, only when Hermes's terminal backend is local (it refuses under docker, ssh, modal and other sandboxes, resolving the backend via tools.terminal_scope and config), and a pre_tool_call hook sends any command Hermes's dangerous-command detector flags (imported from tools.approval_detection) to the same approval gate as the terminal tool; every child process (CLI, daemon, jobs) gets an allowlisted environment without provider API keys, plus any names the user lists in env_passthrough; machine inspection reads CPU, memory, load and cgroup limits; the optional auto_install setting (off by default) fetches the pinned npm package with npx, a network call to the npm registry; background work: the daemon, a heartbeat thread and job registry in the plugin process, and one idle `load-lock events --follow` tail in the process serving the dashboard; no telemetry, no credentials, no other network calls.
From its catalog listing.
How to install
- Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install load-lock - Said no? Turn it on later:
hermes plugins enable load-lock - 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
- aron98 (Community)
- Needs
- No API keys declared
- Adds tools
load_lock_acquireload_lock_claimload_lock_releaseload_lock_cancelload_lock_declineload_lock_rejoinload_lock_wait_for_turnload_lock_pendingload_lock_statusload_lock_inspect_machineload_lock_get_configload_lock_configureload_lock_attach_pidload_lock_mark_startedload_lock_run_with_permitload_lock_job_statusload_lock_job_stopload_lock_wait_for_completionload_lock_agent_guide- Adds hooks
pre_llm_callpost_compactionon_session_endpre_tool_call- Works on
- linux, macos
- Needs Hermes
- 0.23.0 or newer
- Version
- 1.7.1
- In the catalog
- 2026-11-11
Known issues (from its catalog listing)
- Needs the load-lock CLI >= 1.7.1: `npm install -g @aron98/load-lock@1.7.1` (Node >= 20). Without it every tool returns a clear error; the auto_install setting (off by default) can fetch the pinned version with npx instead.
- The Desktop pane and status chip ship disabled, like every Desktop half: turn them on once under Capabilities ▸ Plugins.
- Windows has a named-pipe transport that is unit-tested but not yet verified on a Windows machine.
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