Hermes Tools Reference for Rocky Workflows

Rocky works best when each job uses the narrowest reliable tool. Tool choice is a quality and safety decision: file tools should inspect source, browser tools should verify rendered pages, terminal commands should run builds and deploys, and media tools should only create public-safe assets.

Official reference: https://hermes-agent.nousresearch.com/docs/reference/tools-reference

Core tool lanes

File tools for reading, searching, writing, and targeted patches in known project files.
Terminal for builds, package managers, tests, Git, Cloud CLI commands, and long-running processes.
Browser and computer use for user-facing route checks, visual layout, console errors, and desktop apps.
Web tools for current public documentation and source research.
Image and media tools for approved public illustrations, screenshots, audio, and video artifacts.
Memory and skills for stable preferences and reusable workflows, not temporary project progress.

Selection checklist

Identify the artifact that must change or be verified.
Use read-only discovery before editing or deploying.
Prefer targeted file patches over broad rewrites.
Run the smallest meaningful check, then the release-level check.
Keep private data out of screenshots, prompts, uploads, and generated assets.

Common pitfalls

Using browser screenshots as proof that source data is valid.
Using terminal text checks as proof that a public page looks polished.
Sending private folders or customer data into image prompts.
Saving one-off task progress as durable memory.
Leaving background processes silent when a bounded task should notify on completion.

Verification steps

Confirm the changed files are exactly in scope.
Run syntax or build checks for code edits.
Render the user-facing route in at least desktop and mobile widths.
Inspect console errors when behavior depends on JavaScript.
Report the real command outputs or URLs that prove completion.