Tool
Hermes VS Code Extension — Chat, Skills & Memory in Your Editor
VS Code sidebar extension for Hermes Agent. Chat with Hermes, run skills, and manage memory without leaving your editor.
Quick answer
A Hermes VS Code extension puts the agent in your editor sidebar: chat with Hermes, run skills, and search memory without leaving VS Code. It connects to the same Hermes you run in the terminal, so memory, skills, and provider config are shared across the editor and CLI.
If you live in VS Code, an editor-side panel keeps Hermes one keystroke away — chat, skill runs, and memory search against the same agent your terminal drives.
Features
- ✓Sidebar chat
- ✓Inline code actions
- ✓Skill runner
- ✓Memory search
Why this tool matters
The value of an editor extension is proximity: you stay in context while the agent reads, runs skills, and recalls what it learned earlier. Because it points at your existing Hermes, there is no second memory or second config to keep in sync.
Hermes sits between a code-focused CLI and a messaging agent, so an editor surface is a natural fit for the coding half of that. It is best for in-flow questions and skill execution rather than long autonomous runs, which still belong in a persistent session.
Sharing one agent across editor and terminal means a skill you author in the CLI is immediately runnable in the sidebar, and memory written in either shows up in both. That single-source-of-truth behavior is the point.
For heavier, always-on work — scheduled jobs, channel gateways — the editor is the wrong home, because it lives and dies with your editor window. Keep those on a persistent install and use the extension for interactive coding.
Best use cases
FAQ
Yes — it connects to your existing Hermes, so memory, skills, and provider config are shared. A skill authored in the CLI is runnable in the sidebar, and memory written in either appears in both.
No. The extension lives with your editor window. Scheduled jobs and messaging gateways belong on a persistent install; use the extension for interactive, in-flow coding.
In-context coding help: asking about the current file, running skills, and searching memory without leaving VS Code. Long autonomous runs still belong in a persistent session.