Integration
Hermes Agent for VS Code
Connect Hermes Agent to VS Code with ACP Client. Check dependencies, credentials and workspace access, and avoid confusing local editor setup with a remote VPS session.
Quick answer
Use the ACP Client extension, with Hermes installed and configured where the client launches its agent process. Select Hermes Agent in the ACP panel, or configure command hermes with args ["acp"]. Run hermes acp --check first. This is agent chat and tool execution, not inline autocomplete. A Hermes installation on a separate VPS is not automatically connected to your local editor.
Uses the ACP Client extension: VS Code talks to Hermes through the standard Agent Client Protocol, not a separate closed editor fork.
Best for
Developers who want Hermes inside the editor without abandoning VS Code
Multi-file refactors where the agent should patch code and run tests
Debugging sessions that need terminal output, source context, and approval prompts
Teams comparing Copilot-style completions with tool-using coding agents
Users who may later move from local setup to managed FlyHermes cloud
Features
- ✓ACP editor chat, streamed responses and tool activity
- ✓File reads and patches with diffs rendered by the host
- ✓Terminal commands in the session workspace
- ✓Existing Hermes provider configuration, memory and skills in the selected runtime
- ✓Approval requests with host-dependent presentation and explicit scope
- ✓A separate GitHub workflow when repository automation is needed
Setup path
- 1Choose where Hermes will run before installing anything. The documented local setup launches
hermes acpover stdio; a remote Desktop connection or Telegram bot does not configure that process for VS Code. - 2Complete base Hermes installation and provider setup with
hermes modelon that host. Do not assume that signing into another coding extension supplies Hermes credentials. - 3Check ACP dependencies with
hermes acp --versionandhermes acp --check. If the ACP extra is missing, follow the official ACP installation instructions for your install checkout, then reactivate it and restart Hermes after a dependency change. - 4Install ACP Client by formulahendry, open its Activity Bar panel and select Hermes Agent. If defining it manually, use VS Code setting
acp.agentswith commandhermesand arguments["acp"]. - 5Open the intended repository and connect. Run the read-only workspace check below before allowing edits, dependency installation, git commits or pushes.
- 6Review the first tool call and approval scope. Start with allow once for unfamiliar operations; do not grant a permanent allowance merely to dismiss a connection problem.
What actually connects VS Code to Hermes
The official ACP host guide documents a stdio connection: the client starts Hermes and exchanges protocol messages with it. Hermes retains its runtime identity, provider configuration, memory, skills and tools; VS Code is the conversation surface. The client is not a separate model subscription or a Telegram frontend.
- •Use the extension identity reference if you are unsure which Marketplace item to install.
- •ACP supports chat, tool activity, file diffs and terminal commands; do not infer inline completion or a dedicated memory-search widget from those capabilities.
- •The default editor toolset intentionally excludes messaging delivery and cron management. Use the appropriate separate runtime workflow for those jobs.
Manual configuration and dependency checks
If Hermes is not listed automatically, the current docs use this settings object: { "acp.agents": { "Hermes Agent": { "command": "hermes", "args": ["acp"] } } }. Keep the executable and arguments separate. This is VS Code configuration, not a shell command.
- •Read-only checks:
hermes acp --version,hermes acp --check,hermes doctor,hermes status. A dependency check is not proof of a successful model request. - •For a PM-prepared source checkout at the documented default location, the official extra-install command is
cd ~/.hermes/hermes-agent && python -c "import pm; pm.sync_venv(['acp'], explicit=True)". Use your actual checkout and prepared environment; do not run it blindly from a different Python installation. - •If the launcher cannot be found, check the environment used by the extension, not just a different terminal. Changing a prompt cannot fix a missing executable.
- •Optional browser tooling has a separate bootstrap:
hermes acp --setup-browser. It is not required just to read repository files.
Local editor versus an existing VPS session
Installing ACP Client on a laptop does not turn hermes acp into a connection to a Hermes process on a VPS. The ordinary local configuration starts an agent command in its launch environment. Decide whether you want a new editor session against accessible project files or to view the remote session that already owns the work.
- •For local coding, install/configure Hermes locally and open the intended local repository. Credentials and files on a VPS do not appear automatically.
- •For an existing remote workflow, start with the Desktop remote-backend guide and verify the supported connection surface. Do not paste a dashboard URL or Telegram token into an executable setting.
- •If you use a remote development environment, verify where the extension actually launches commands and where the workspace exists. Remote client compatibility is not established by the local recipe alone.
- •Do not start a second agent editing the same branch merely to get a visual view. Confirm repository, branch and current uncommitted changes first.
Read-only workspace acceptance check
After connecting, use this prompt on a non-sensitive test repository: "Do not modify files or run installs. Show the working directory. Read the first heading of README.md from this workspace, report its exact path, and summarize git status if this is a Git repository. Do not read secrets, commit or push." This is a proposed acceptance procedure, not a claim that we ran your editor session.
- •Pass only when the reported path and README heading match the repository you intended. A connected badge or generic greeting is insufficient.
- •If the file exists only on another machine, stop and fix access/runtime selection before enabling writes. Do not grant wider home-directory access as a shortcut.
- •Review actual tool output rather than accepting an unsupported statement that files were read.
- •Record the host, workspace, selected provider and result without tokens. Provider authentication success, workspace access and permission behavior are separate checks.
Approval scope and shared state are not a sandbox
ACP can send permission requests to its host, but the host controls whether a person sees them. The current approval documentation distinguishes allow once, allow for session and persistent allow always. Do not assume every client presents every choice or that an editor panel isolates the operating-system account.
- •Allow once applies to the current call. Session approval is cleared when that session ends; permanent approval persists. Choose the narrowest scope that fits.
- •Hermes configuration and stored memory come from the runtime/profile in use, not automatically from every machine where you have installed Hermes.
- •Keep credentials out of prompts and repository files. See reusable skills for conventions, not secret storage.
- •If tools differ from the terminal, inspect the documented ACP toolset and runtime profile; do not enable every tool simply to make the lists match.
When to choose editor access or managed hosting
Choose VS Code when your goal is interactive repository work with visible tool activity and diffs. Choose a separate always-on workflow when work must continue independently of your editor. Compare self-hosted and managed responsibility before buying hosting; hosting alone does not establish ACP connectivity or access to local files.
- •The self-hosted Web Dashboard also has browser Chat; this is not a browser-chat-versus-no-chat choice.
- •For remote repository automation, use the GitHub integration guide and verify credentials, branch scope and deployment readback separately.
- •If maintenance is the obstacle, review managed hosting and costs. Confirm the offered access surface and file-transfer path before moving a project.
Sources and scope
Documentation checked October 24, 2026: Hermes ACP host integration, programmatic integration and the ACP Client listing. These are current documentation references, not a claim that every installed release or remote extension host behaves identically.
- •No provider benchmark, editor latency measurement or remote connection success is claimed here.
- •The optional creator video below shows a different VPS/Telegram workflow. It is context for remote operation, not an ACP setup demonstration or a prerequisite for VS Code.
Keep the remote-workflow example separate
A remote agent can work on a different checkout from the one open on your laptop. Use the remote repository workflow to understand that path, but finish the local ACP checks above if your immediate goal is seeing the intended files and tool activity inside VS Code. Do not infer that a video demonstrates a supported VS Code-to-VPS transport.
Optional demo video
Optional: remote coding through Telegram, not VS Code ACP — ZazenCodes
This existing ZazenCodes walkthrough concerns VPS, Docker and Telegram operation. It is a separate workflow, not proof of ACP extension setup or a requirement for local VS Code. Verify current provider, permission and deployment details in the relevant guides before following a recorded demonstration.
- 0:00Introduction — lead developer use case overview
- 1:30Tech stack: VPS + Docker + Telegram bot architecture
- 3:00Live demo: talking to Hermes on Telegram from a phone
- 5:00Deploying Hermes on Hostinger with one-click Docker install
- 8:30Setting up Telegram bot via BotFather, locking user ID
- 11:00Connecting GitHub CLI and cloning a repository
- 14:00Building a blog feature + AI image generation from Telegram
- 18:00Inside the VPS: Docker layers, SSH keys, .env file
- 21:00Navigating Docker container and Hermes data folder
- 24:00Closing thoughts: Hermes speed, slash commands, token usage
Common setup issues
- Agent missing or connection fails immediately: check the executable/PATH and ACP dependency extra in the client launch environment; run
hermes acp --checkthere. - Another coding extension authenticates but Hermes does not: use Hermes provider setup with
hermes model; credentials from a different extension are not the Hermes configuration. - Hermes exists only on a VPS: the ordinary local ACP recipe does not connect to that installation. Confirm the supported remote surface before changing local settings.
- Connected but wrong files: stop edits, verify the workspace path and perform the read-only README check. ACP binds file and terminal operations to the session working directory.
- Unexpected tool availability: check
platform_toolsets.acpandagent.disabled_toolsetsin the actual runtime profile against current official docs. Editor-supplied MCP servers have their own session scope. - Browser tools unavailable: follow the optional browser bootstrap only when the task needs a browser; file-only onboarding does not require it.
- Approval behavior differs from expectations: inspect host support and the scope granted. A protocol approval request is not a guarantee that the host displayed a human confirmation.
Keep building the workflow
Install Hermes Agent first
Base CLI setup, provider choice, PATH reload, and first smoke test before VS Code.
Use Hermes with OpenRouter
Hosted model setup, credits, rate limits, and provider fallback for tool-heavy editor sessions.
Connect Hermes to GitHub
Move from local VS Code steering to PR review, CI summaries, issue triage, and repository automation.
Create reusable Hermes skills
Save repo conventions and repeated debugging workflows so future VS Code sessions start smarter.
Compare Hermes with GitHub Copilot
Understand when to use inline completions versus an autonomous tool-using coding agent.
FAQ
Which VS Code extension should I install for Hermes?
The official Hermes ACP guide points to ACP Client by formulahendry. Open its panel and choose Hermes Agent, or define command hermes with args ["acp"] under acp.agents.
Does a VPS installation automatically connect to local VS Code?
No. The documented local setup launches a Hermes command in the client launch environment. A separate VPS, Telegram bot or Desktop remote connection does not automatically configure that launch or make remote files available.
Do I need a VPS or Telegram bot to use Hermes in VS Code?
No. They are separate operational choices, not prerequisites for the local ACP setup. Start with a working Hermes installation, provider configuration, ACP dependencies and the intended repository.
Why does hermes acp --check pass but the session still fails?
The check verifies ACP readiness, not a completed provider request or correct repository access. Verify provider configuration, client launch environment and a harmless read of an expected workspace file separately.
Does Hermes ACP provide inline autocomplete?
This setup documents agent chat, tool activity, diffs and terminal operations. It does not establish a Copilot-style inline-completion feature. Evaluate completion tools separately if that is the feature you need.
Are editor and terminal memories always shared?
They use Hermes state from the runtime/profile they actually connect to. The same configured runtime can reuse its memory and skills; separate hosts or profiles do not automatically share that state.
Is allow for session the same as allow always?
No. Current Hermes ACP documentation describes session-scoped permission that resets when the session ends, while allow always writes a persistent allowance. Host support determines which choices are presented; start with the narrowest permission.