Use Hermes-owned skills, connected services, browser workflows, messaging, schedules, or external automation through bridge policy. Do not use for ordinary local code edits.

Ask Hermes to inspect its configured capabilities in plan mode. Hermes may access open-world tools, so review the response before taking or approving an external action.

Inspect bridge status, configured presets, skills, toolsets, providers, models, and policy before deciding whether Hermes owns the requested capability.

List configured bridge presets and their declarative Hermes skills and toolsets.

Check whether the configured Hermes CLI runtime is available without running a provider request.

Start a long Hermes plan, draft, or approval-preview job and return immediately. Direct execute requests are converted to request-approval; use hermes_prepare and hermes_approve for execution.

Read lifecycle metadata for an asynchronous Hermes job without returning its output.

Read the bounded stdout/stderr result of a completed asynchronous Hermes job.

Idempotently cancel a queued or running asynchronous Hermes job.

Create a local, non-executing preview and short-lived one-shot approval ID without invoking Hermes or its tools. The caller must show preview.action to the human before approval.

Consume a prepared approval ID exactly once and submit the unchanged request for execution. This can cause external side effects.

Consume a prepared approval ID without executing the external action.