Hermes Agent

Tool

Hermes in VS Code: which extension to use

Development

Use ACP Client to connect VS Code to Hermes Agent. Identify the correct extension, check the local launcher and understand chat, diffs and approval boundaries.

Quick answer

The official Hermes guide recommends ACP Client by formulahendry, with Hermes Agent selected in its agent list. Hermes is the agent runtime; the extension is the ACP host. The documented connection uses command hermes with args ["acp"], not a Telegram token or an automatic connection to a remote VPS.

Choose this route for agent chat, visible tool activity and file diffs in your editor. Do not install an unknown extension just because its name includes Hermes, or assume that a sidebar implies inline autocomplete or dedicated memory-management controls.

Command map

hermes acp --version

Record the ACP version exposed by the intended installation.

Run in the client launch environment, not an unrelated host.

hermes acp --check

Check ACP dependencies and adapter readiness.

A pass is not proof of provider authentication or correct workspace access.

Features

  • ✓Agent chat and streamed responses over ACP
  • ✓Host-rendered tool activity and file diffs
  • ✓Terminal operations relative to the session workspace
  • ✓Hermes memory and skills from the configured runtime
  • ✓Permission requests with host-dependent UI and approval scope

Why this tool matters

Extension identity matters: the specific official ACP host guide links to formulahendry.acp-client. Confirm the publisher and item ID before installing. The detailed integration guide owns the end-to-end setup and recovery procedure; this page identifies the tool and its limits.

There are two distinct pieces: ACP Client owns the editor conversation surface, while Hermes provides the agent runtime and its provider configuration. The ordinary local setup launches a stdio process. Installing the client does not install or authenticate Hermes on every host.

Memory and skills follow the Hermes runtime/profile, not the brand name of the extension. A laptop installation and a VPS installation can have different credentials, files and state. Verify the intended workspace before allowing edits.

Current docs describe chat, file diffs, terminal activity and permission requests. They do not establish a separate inline-code-actions feature or dedicated memory-search panel in this client. Ask the agent to use available skills or memory tools instead of assuming a particular UI exists.

ACP permission options have different scopes. Start with allow once for unfamiliar actions. The host determines whether prompts reach a human; a protocol capability alone is not a sandbox or proof of confirmation.

Always-on execution and editor access are separate decisions. A disconnected editor does not by itself prove every underlying task stopped. Inspect the runtime and task state before retrying writes, and use the relevant gateway or hosting documentation for persistent operation.

Best use cases

Inspect a repository with agent tool output visible in the editor
Review proposed file diffs before broader changes
Use existing skills in the intended Hermes runtime
Run a harmless workspace-read check before granting write access
Choose an ACP client separately from an inline-completion tool

Related Hermes Agent guides

View ACP Client on Marketplace →

FAQ

Is this a separate official Hermes IDE?

No. The documented setup uses the ACP Client extension as a host and Hermes Agent as the runtime. Check the official ACP guide and the exact Marketplace publisher before installing.

Does ACP Client include a Hermes subscription?

The client connection does not replace Hermes provider configuration. Configure the provider used by the intended Hermes runtime and verify its billing independently.

Can I use a VPS Hermes from a local ACP configuration?

Not automatically. The local recipe launches a process in its client environment. Verify a supported remote connection path and actual repository access rather than inserting a dashboard URL as a command.

Does this prove inline code actions or memory-search UI are available?

No. The official Hermes ACP capabilities establish agent chat, tool activity, file diffs, terminal commands and permission requests. A dedicated UI feature needs separate client documentation.

What should I verify before letting Hermes edit files?

Confirm the launch host, runtime/profile, workspace path and a harmless read of an expected non-sensitive file. Then review the approval scope before permitting writes. The integration guide provides an acceptance prompt.

Related Resources