Tools guides

A practical guide to toolsets overview in a verified Hermes/Rocky workflow.

A practical guide to terminal tool in a verified Hermes/Rocky workflow.

How Rocky uses file tools safely to read, search, write, and patch project files without accidental broad edits.

A practical guide to web search and web extract in a verified Hermes/Rocky workflow.

A practical guide to browser automation in a verified Hermes/Rocky workflow.

A practical guide to macos computer use in a verified Hermes/Rocky workflow.

How Rocky uses vision tools to inspect screenshots, images, layouts, and visual evidence while still verifying important claims.

A practical guide to image generation tool in a verified Hermes/Rocky workflow.

A beginner-friendly guide to enabling Hermes tools gradually: web, file, terminal, browser, vision, image generation, gateway, and automation tools.

How to understand where Hermes terminal and file operations are running, especially when using local, Docker, SSH, or other remote backends.

How to decide which tools Rocky should use for a workflow, from read-only research to file edits, desktop automation, image generation, and deployment.

A public-safe checklist for connecting MCP servers to Rocky through Hermes without guessing at tool availability or exposing credentials.

Choose the right Hermes tool for file work, browsing, desktop control, media generation, and verification without crossing safety boundaries.

Choose Hermes toolsets intentionally so Rocky has enough capability to act without exposing unnecessary surfaces.

Use terminal access responsibly: prefer read-first discovery, avoid destructive commands, keep secrets out of logs, and verify command results.

Run builds, tests, servers, and interactive CLIs without losing process visibility, completion signals, logs, or cleanup responsibility.

Reduce repeated schema overhead by loading MCP and plugin tools on demand while preserving real approvals, hooks, guardrails, and tool identities.

Catch type errors, undefined names, missing imports, and project-wide semantic issues after file edits by pairing syntax checks with language servers.

Give each coding agent an isolated branch and checkout so parallel work cannot overwrite another agent’s files or rollback history.

Decide when core code is justified, then register a schema, availability check, handler, toolset membership, tests, and safe error contract.

Follow a Hermes tool from self-registration and toolset filtering through availability checks, central dispatch, hooks, and structured error handling.

See how persistent CDP supervision surfaces blocking JavaScript dialogs and cross-origin iframe targets without bloating unsupported browser sessions.

Use execute_code for multi-tool Python workflows while preserving tool limits, environment isolation, and concise final output.

Use the read-only x_search tool for cited X discovery, validate filters, and recognize degraded unsourced responses.

Route Hermes terminal and file work into a Vercel Sandbox microVM with the supported SDK, authentication, runtime, snapshot, disk, and background-process settings.

Select among Hermes' eight web backends, split search from extraction when useful, control auto-detection, and verify the active provider without configuration surprises.

Compare Chrome, Chromium, CDP, and browser-provider options by runtime, isolation, login continuity, and verification needs.

Preserve working directory and exported variables across terminal calls when the backend benefits, while understanding one-shot fallbacks and precedence.

Select core, composite, platform, and dynamic toolsets with a least-privilege workflow and clear verification gates.