Hermes Apollo is an opinionated distribution of NousResearch/hermes-agent tuned for competitive programming, rigorous software work, Remotion-based video generation, and local Browser Use workflows.
This repo is not a dump of a live ~/.hermes directory. It keeps upstream Hermes intact and layers Apollo defaults on top through versioned files and a small installer.
- A global Apollo identity via
SOUL.md - Config overrides for a more technical default setup
- Apollo skills for:
- competitive programming
- Remotion video generation
- Browser Use CLI workflows
- A local Browser Use wrapper for direct, local-first usage
- Upstream Hermes source code plus an Apollo distribution layer
- A reproducible way to apply Apollo defaults into
~/.hermes - A cleaner upgrade path than hand-editing a live install
- A snapshot of your runtime sessions, memories, or secrets
- A replacement for upstream Hermes documentation
- A custom fork that rewrites core Hermes behavior everywhere
The Apollo-specific files live here:
apollo/
defaults/
SOUL.md
MEMORY.md (seeded into memories/ on fresh install)
oracle-prompt.md
config-overrides.yaml
bin/browser-use-direct
skills/
software-development/competitive-programmer/
remotion/remotion-video-generator/
browser-use/browser-use-cli/
scripts/
install-apollo.sh
If you already have Hermes installed and just want the Apollo behavior:
git clone https://github.com/tradewife/hermes-apollo.git
cd hermes-apollo
bash scripts/install-apollo.shThat installs Apollo defaults into ~/.hermes.
scripts/install-apollo.sh does the following:
- writes
~/.hermes/SOUL.md - writes
~/.hermes/oracle-prompt.md - deep-merges Apollo config overrides into
~/.hermes/config.yaml - copies Apollo skills into
~/.hermes/skills - installs
~/.hermes/bin/browser-use-direct - seeds
~/.hermes/memories/MEMORY.md(fresh installs only; never overwrites existing)
~/.hermes/.env~/.hermes/auth.json- sessions
- memories
- runtime state files
If you do not have Hermes installed yet, install Hermes first, then apply Apollo:
git clone https://github.com/tradewife/hermes-apollo.git
cd hermes-apollo
bash setup-hermes.sh
bash scripts/install-apollo.shIf you already manage Hermes another way, that is fine too. Apollo only needs a working Hermes install plus a writable ~/.hermes.
Apollo includes a Browser Use skill and a local wrapper entrypoint:
~/.hermes/bin/browser-use-directFor local-only Browser Use workflows, Apollo prefers that wrapper over the standard Browser Use session-server flow.
Browser Use itself is still installed separately. A typical setup is:
uv tool install browser-use
~/.hermes/bin/browser-use doctorIn restricted Linux environments, the official browser-use install command may fail on the sudo dependency step. In those cases, Playwright-only browser installation may still work.
Apollo includes the remotion-video-generator skill and a configured remotion-documentation MCP server entry in the Apollo config overrides.
Apollo does not install Remotion into every project automatically. Remotion remains a per-project dependency when you actually build video pipelines.
To reapply Apollo defaults after changing the Apollo layer:
bash scripts/install-apollo.shThis is safe to rerun. It reapplies Apollo defaults without replacing your .env, auth, or runtime state.
Apollo is designed to keep upstream Hermes easy to update.
Safe pattern:
git pull --rebase upstream main
bash scripts/install-apollo.shThe important distinction is:
- upstream Hermes code lives in the repo
- Apollo customization lives in
apollo/ - live runtime state lives in
~/.hermes
That separation is the whole point of this fork.
For Hermes core features, commands, and architecture, use the upstream documentation:
This repo inherits the upstream Hermes Agent license. See LICENSE.