Skip to content

hermes-full-layer

Recipe card from the charly-hermes plugin (Images — the deployable catalog).

Metalayer composing Hermes AI agent with a complete tool suite for standalone deployment. No browser included — use with selkies-desktop via cross-container env_provide: BROWSER_CDP_URL for shared browser automation.

# the hermes-full metalayer is a candy entity; composition is an inline candy: list in the body
hermes-full:
candy:
version: 2026.156.1921 # mandatory CalVer
candy: # the candies it pulls in
- hermes # AI agent with browser tools, MCP, LLM auto-config
- claude-code # Anthropic Claude Code CLI
- codex # OpenAI Codex CLI
- gemini # Google Gemini CLI
- dev-tools # bat, ripgrep, neovim, gh, direnv, fd-find, htop, etc.
- devops-tools # AWS CLI, Scaleway, kubectx, OpenTofu, wrangler, jq, rsync
- charly # OpenCharly CLI for in-container management
- tmux # Terminal multiplexer for persistent sessions

The hermes candy declares env_accept: BROWSER_CDP_URL. When deployed alongside a selkies-desktop container, the chrome candy’s env_provide injects BROWSER_CDP_URL=http://charly-selkies-desktop:9222 into the hermes quadlet via charly config --update-all. Hermes browser tools (browser_navigate, browser_click, browser_snapshot) then control the desktop Chrome across the container network.

Without a browser provider, hermes browser tools fall back to local headless mode (requires hermes-playwright candy) or are unavailable.

charly.yml
hermes:
candy:
base: fedora
candy:
- agent-forwarding
- hermes-full
- dbus

Use when working with the hermes-full metalayer, full-featured standalone hermes deployments, or the composition of hermes with AI CLIs and developer tools.

  • /charly-image:layer — candy authoring reference (charly.yml schema, plan steps, service declarations)
  • /charly-check:check — declarative testing (check: block, charly check box, charly check live)