Updating & Uninstalling
Updating Git installs Update to the latest version with a single command: This pulls the latest code from , updates dependencies, and prompts you to configure a
- Section
- Getting Started
- Source
- hermesbible.com/docs/getting-started/updating
Updating Git installs Update to the latest version with a single command: This pulls the latest code from , updates dependencies, and prompts you to configure a
Excerpt from the official Hermes Agent documentation, quoted for reference. View sourceWhat this page covers
- Updating
- Git installs
- pip installs
- What happens during an update (git installs)
- Updating against a non-default branch: --branch
- Local changes on non-interactive updates
- Preview-only: hermes update --check
- Full pre-update backup: --backup
- Windows: another hermes.exe is running
- Recommended Post-Update Validation
Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.
Upstream outline
- Updating
- Git installs
- pip installs
- What happens during an update (git installs)
- Updating against a non-default branch: --branch
- Local changes on non-interactive updates
- Preview-only: hermes update --check
- Full pre-update backup: --backup
- Windows: another hermes.exe is running
- Recommended Post-Update Validation
- If your terminal disconnects mid-update
- Checking your current version
- Updating from Messaging Platforms
- Manual Update
Section map
Updating
Maps updating to the Getting Started documentation path, with the source page reserved for exact commands and updates.
Git installs
Maps git installs to the Getting Started documentation path, with the source page reserved for exact commands and updates.
pip installs
Maps pip installs to the Getting Started documentation path, with the source page reserved for exact commands and updates.
What happens during an update (git installs)
Maps what happens during an update (git installs) to the Getting Started documentation path, with the source page reserved for exact commands and updates.
Updating against a non-default branch: --branch
Maps updating against a non-default branch: --branch to the Getting Started documentation path, with the source page reserved for exact commands and updates.
Local changes on non-interactive updates
Maps local changes on non-interactive updates to the Getting Started documentation path, with the source page reserved for exact commands and updates.
Preview-only: hermes update --check
Maps preview-only: hermes update --check to the Getting Started documentation path, with the source page reserved for exact commands and updates.
Full pre-update backup: --backup
Maps full pre-update backup: --backup to the Getting Started documentation path, with the source page reserved for exact commands and updates.
Implementation notes
- Use this Getting Started doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
- Primary decision areas: Updating, Git installs, pip installs, What happens during an update (git installs), Updating against a non-default branch: --branch. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
- Useful search signals for this doc: updating, uninstalling, installs, update, latest. These are derived from the public title and summary so the clone remains lightweight.
Decision table
Use when you need orientation for updating & uninstalling before applying exact upstream commands.
Open the source anchor for Updating and confirm platform-specific requirements before changing configuration.
Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.
Verification checklist
- Use this page to orient yourself within Getting Started, then open the linked source page for exact current syntax.
- Start with the source section for Updating; do not rely on the local summary for commands or secrets.
- Check platform, install method, provider, and credential assumptions before changing a real environment.
- Review the source section for Git installs if the page involves setup, automation, messaging, or runtime behavior.
- After applying anything from the source, run the smallest relevant smoke test before widening scope.
Risk notes
Keep human review before sending public posts, customer messages, trading instructions, or team notifications.
Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.
What this page covers
- Updating Git installs Update to the latest version with a single command
- This pulls the latest code from , updates dependencies
- prompts you to configure a
Source mirror note
This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.
Open source page