← Back to Hermes

Hermes companion stack

Recommended tools and companion stack

Hermes sits inside a larger working stack: shell habits, editor bridges, session hygiene, proof routines, and rollout discipline.

Stack ruleTreat the local CLI as the foundation even when Hermes is used through an editor or messaging surface.

Hermes is not only a runtime choice. In practice, it sits inside a larger working stack: editor, terminal, session habits, validation routines, approval judgment, and rollout discipline.

Current best-supported editor lane

local Hermes runtime install
hermes setup
VS Code extension install
sidebar interaction through the local runtime

Useful bridge hooks

hermes.debugLogs
hermes.path
local hermes acp spawn behavior

Core operator skills matter as much as tools

provider/model configuration judgment
session hygiene and continuity management
approval/security posture awareness
messaging-surface behavior awareness
debugging and recovery-vs-rebuild judgment

What is still thinner than the rest

broader editor and IDE coverage beyond the first VS Code lane
richer toolchain examples for testing and observability in longer-running coding workflows
stronger evidence for deeper companion-stack diversity

Related pages

Trust, risks, and known limits