How-To Series · Episode 49 / 59 · Module 7: Power Tools

Hermes · In Your Editor (ACP)

Chat, diffs, terminal, approvals. Native, in VS Code, Zed, or JetBrains.

After this videoYou can now run Hermes as an editor-native coding agent.

ACP, the Agent Client Protocol, lets Hermes run as an agent server your editor talks to over stdio. VS Code, Zed, and JetBrains render Hermes natively: chat, tool activity, file diffs, terminal commands, approval prompts, and streamed thinking. Install the extra (pip install -e '.[acp]') and launch hermes acp (it logs to stderr; stdout is reserved for ACP JSON-RPC). Wire it up: VS Code via the ACP Client extension, Zed via the ACP registry (needs uv), JetBrains via an ACP-compatible plugin. In editor mode Hermes runs a coding-tuned toolset (files, terminal, web, memory, code execution, delegation, vision) and drops messaging + cron, using your same config, skills, and credentials. Dangerous commands route back to the editor as a prompt with three tiers: allow once, allow for session, allow always.

About these resources. Every command in this video comes from the ACP Editor Integration doc.

Sources · What this video distills

1 docs page · every command below traces to one of them
Primary · ACP server model, install/launch, VS Code / Zed / JetBrains setup, the hermes-acp toolset, approvals
ACP Editor Integration
Read ↗

Commands shown · Copy and paste

each shows the source doc it came from
Install + launchfrom source ↗
pip install -e '.[acp]' · hermes acp
Health checkfrom source ↗
hermes acp --check
VS Code (settings.json)from source ↗
"acp.agents": { "Hermes Agent": { "command": "hermes", "args": ["acp"] } }

Going deeper · Related Hermes docs

further reading · not sources of facts shown above

Next in the series · Episodes that build on this

E42
Connect Anything With MCP
E48
As an API Server
E47
As a Python Library