Hermes Agent for VS Code
Run Hermes Agent inside VS Code with ACP: editor chat, file diffs, terminal commands, approvals, project memory, skills, and autonomous coding workflows without leaving your repository.
Quick answer
To use Hermes Agent in VS Code, install Hermes, install the ACP Client extension, choose Hermes Agent in the ACP panel, and open a repository. Hermes then runs as an ACP server so VS Code can show chat, tool activity, file diffs, terminal commands, approvals, memory, and skills in the editor workflow.
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 inside VS Code
- ✓File reads, patches, and multi-file diffs
- ✓Terminal commands, builds, and test verification
- ✓Persistent memory and reusable skills for repo conventions
- ✓Permission prompts for risky commands and edits
- ✓GitHub handoffs for PR review, CI, and issue workflows
Setup path
- 1Install and configure Hermes Agent with your model provider using hermes setup or hermes model
- 2Install the VS Code ACP Client extension from the Visual Studio Marketplace
- 3Open the ACP Client panel and select Hermes Agent from the built-in agent list
- 4If needed, add Hermes manually in VS Code settings with command hermes and args ["acp"]
- 5Open your repository in VS Code, connect, and ask Hermes to inspect files, patch code, run tests, or explain a diff
What actually connects VS Code to Hermes
Hermes runs locally as an ACP server with hermes acp. The VS Code ACP Client extension launches or connects to that server over stdio, then renders Hermes messages, tool calls, file diffs, terminal output, and approval prompts inside your editor.
- •Use VS Code for the human-in-the-loop coding session.
- •Use Hermes for the agent runtime: tools, memory, skills, provider routing, and terminal execution.
- •Use GitHub integration for unattended PR, issue, CI, and webhook work when the editor is closed.
The setup snippet if Hermes is not listed automatically
Most users can select Hermes Agent from the ACP Client's built-in list. If your VS Code setup needs a manual agent definition, add Hermes under acp.agents with command hermes and args ["acp"]. Run hermes acp --check first if the panel cannot connect.
- •Command: hermes
- •Arguments: acp
- •Health check: hermes acp --check
- •Optional browser tools: hermes acp --setup-browser
When VS Code is the right surface
Use the VS Code integration when a developer is actively steering a local repo: reviewing a file, asking for a patch, approving a terminal command, or iterating on failing tests. It is not mainly an autocomplete product; it is an editor surface for an autonomous tool-using agent.
- •Multi-file refactors where you want to inspect diffs before applying them.
- •Debugging loops that need terminal output, logs, browser checks, and source edits in one place.
- •Repo-specific workflows where Hermes should remember conventions through skills and memory.
VS Code, Copilot, and FlyHermes serve different jobs
Copilot is still excellent for inline completions. Hermes in VS Code is better when the task needs tools, filesystem changes, tests, memory, or multi-step execution. FlyHermes is the cloud path when you want hosted Hermes without running the local server, gateway, model credentials, and maintenance yourself.
- •Use Copilot for fast inline suggestions and editor-native completions.
- •Use Hermes in VS Code for permissioned agent work inside the repo.
- •Use FlyHermes when the desired outcome is managed cloud Hermes rather than local setup.
Common setup issues
- If VS Code cannot connect, run hermes acp --check in a terminal and confirm the hermes command is on PATH for VS Code.
- If browser tools are missing in ACP mode, run hermes acp --setup-browser and reconnect the VS Code ACP Client.
- If Hermes edits the wrong files, open VS Code at the repository root and start the ACP session from that workspace.
- If terminal commands run in the wrong environment, check the active Hermes profile, shell PATH, virtualenv, and workspace path before changing prompts.
- If you expected inline autocomplete, keep Copilot for completions and use Hermes for multi-step tool execution, memory, tests, and repo automation.
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.
Compare Hermes with Claude Code
See how Hermes differs from terminal-first coding agents, especially memory, skills, and gateways.
FAQ
How do I use Hermes Agent in VS Code?
Install Hermes Agent, install the ACP Client extension in VS Code, open the ACP Client panel, select Hermes Agent, and connect. If Hermes is not listed, configure acp.agents with command hermes and args ["acp"].
Is Hermes Agent a VS Code extension or a separate agent?
Hermes Agent is the agent runtime. VS Code connects to it through ACP, so the editor can show chat, diffs, tool calls, approvals, and terminal output while Hermes handles the actual agent work.
Does Hermes Agent replace GitHub Copilot in VS Code?
Not exactly. Copilot is strongest for inline completions and quick editor suggestions. Hermes is for autonomous tool use: reading files, patching code, running commands, using persistent memory, and coordinating multi-step tasks.
What command should VS Code run for Hermes ACP?
Use command hermes with args ["acp"]. You can also verify the install with hermes acp --check before connecting from VS Code.
Should I use VS Code, GitHub integration, or FlyHermes?
Use VS Code for active local coding, GitHub integration for unattended repo automation, and FlyHermes when you want the hosted cloud version instead of maintaining the server, gateway, provider credentials, and dashboard yourself.