Time to complete
~10-15 minutes
CLI
Use Hermes through the command line with clear first commands and practical next actions.
CLI is the direct path for local daily usage. This page covers when to use it, what to run first, and when to continue to gateway or skills.
Commands
hermesPrimary command for direct local interaction.
hermes setupInitialize or repair setup state for CLI usage.
hermes updateUpdate Hermes to the latest supported release.
hermes doctorDiagnose environment and configuration issues quickly.
Troubleshooting hint
If CLI behavior is inconsistent, run `hermes doctor` first, then retry after `hermes setup` and environment verification.
Steps
1. Use `hermes` as your primary command-line entry point.
2. Run `hermes setup` when you initialize or reconfigure local usage.
3. Run `hermes update` on a controlled cadence to keep versions current.
4. Run `hermes doctor` whenever behavior looks inconsistent.
5. Move to gateway for messaging integrations, or to skills for reusable workflows.
Prerequisites
- Hermes installation and basic setup are complete.
- You can run Hermes commands in your target terminal environment.
Notes
- Use CLI first when you want predictable local control and debugging.
- Continue to gateway when your target interaction channel is messaging apps.
- Continue to skills when you need reusable task patterns for team workflows.
Next step
Related Guides
Gateway
Add messaging-platform routing after CLI basics are stable.
Set Up GatewaySkills
Model repeatable usage patterns as reusable skills.
Open SkillsMemory
Add persistent context to long-running CLI workflows.
Open Memory