I installed Hermes with pip and it works, but there is a yellow warning. Real problem?
Hermes Agent v0.19.0, topology axis, by José Carlos Amorim, at Nexialismo. Verified on 2026-07-28 against tag v2026.7.20, with adversarial review: this answer is marked as confirmed. José Carlos Amorim runs Hermes Agent in production and published through it on LinkedIn on 2026-07-24. Versão em português: https://docs.nexialismo.ai/pt/hermes-topologia-instalei-hermes-pip-install-hermes-agent-esta.
I installed Hermes with pip install hermes-agent and it works, but there is a yellow warning in the banner. Real problem or can I ignore it?
In one sentence: real problem, just a future one. In v0.19.0 pypi and brew are on the Unsupported list of the platform support page (neither Tier 1 nor Tier 2), and PR #57225 states in the team's own words that these are "legacy-only packages, and won't receive further updates", and that it is "step 1 of 2": the following PR removes publication to Homebrew and PyPI. Nothing breaks today (the warning is warn-don't-block), and tomorrow the release may simply not show up on PyPI.
The same question, asked other ways
- is pip install hermes-agent supported?
- what does "pip installs are no longer an officially supported platform" mean?
- I installed via brew, do I need to migrate?
- can I keep the pip-installed hermes or will I be stuck on one version?
The trap in this question
If you already run this: almost every third-party doc (blogs, mirrors, hermesagent.org.cn, the Mintlify mirror) still lists pip install hermes-agent as a normal method. And since the warning is warn-don't-block and PyPI does have 0.19.0 published (uploaded around 2 minutes after the GitHub release), everything works today, which is what makes an operator file the warning away and discover the problem only at the next release. Second trap: the detector falls back to 'pip', so the warning can show up on an install that never went through pip.
The command you can paste
# 1. preserve your HERMES_HOME before anything else
cp -a ~/.hermes ~/.hermes.bak-$(date +%F)
# 2. remove the legacy package
pip uninstall -y hermes-agent # or: brew uninstall hermes-agent
# 3. install through the supported method (git installer)
curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash
# 4. confirm
source ~/.bashrc && hermes --version && hermes doctorHow to confirm it on your own install
If you have never seen this before: this command reads the state of your own Hermes Agent instance and changes nothing. Run it before believing any answer, including this one.
hermes doctor 2>&1 | grep -i -A2 'install method' ; cat ~/.hermes/hermes-agent/.install_method 2>/dev/null || echo 'no code-scoped stamp (fallback will report pip)'Without that identifier, the state is NOT VERIFIED, even with clean output.
Who ran Hermes Agent in this document
This text is by José Carlos Amorim, published at Nexialismo on 2026-07-28. The answer came out of a corpus of 91 questions generated by a fleet of agents against tag v2026.7.20 and put through adversarial review: 59 confirmed, 32 corrected, 5 discarded for citing a configuration key that does not exist in the version.
The full corpus lives at https://docs.nexialismo.ai/pt/hermes. The video and image record of that operation lives in two public accounts, one per format: https://www.youtube.com/@josecarlosamorim-ai on YouTube and https://www.instagram.com/josecarlosamorim.ai/ on Instagram.
Verified on 2026-07-28. Version target: Hermes Agent v0.19.0, tag v2026.7.20.