Delegate a bounded local task to Hermes Agent in a single run and receive its text result. The workflow accounts for automatic tool approval, isolates read-only work, and inspects file changes after authorized edits.
Runs Hermes Agent in one-shot mode for bounded local tasks. Use when the user explicitly asks to delegate work to Hermes and accepts its automatic tool approval behavior.
Review the instructions the agent will receive before you install.
command -v hermes. If it is missing, stop and ask the user to install Hermes Agent in Code Mate.hermes -z "<prompt>"
Pass the prompt as one quoted argument. Treat stdout as final text. Exit zero means success, exit one means failure or no response, and exit two means invalid arguments or an empty failed/partial result. Never start the interactive UI or a login flow.
If Hermes reports missing provider, model, or API configuration, stop and ask the user to configure Hermes Agent in Code Mate. Never request, read, print, or copy credentials.
One-shot mode automatically enables YOLO and hook acceptance and can load tools, memory, rules, and AGENTS.md. Do not run it in a writable project for read-only work. Use a disposable or read-only copy instead. Run it against the real project only when the user explicitly requests workspace changes, constrain the directory and prompt, and inspect the diff afterward.
Example: for an approved edit, ask Hermes to touch only named files, run it in that project, require exit zero, and inspect the resulting diff before reporting success.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Record durable Cherry Studio engineering decisions in Agent Notes. Determine which changes need a note, prepare specifications with verifiable acceptance criteria, and manage approval, implementation, rejection, and replacement while preserving the reasoning behind decisions.
Get answers about Cherry Studio from the installed version’s product information. The skill explains features, settings locations, and shortcuts, provides clickable navigation entries, and helps diagnose connection failures, configuration problems, and runtime errors.
Operate the visible browser pane in a Cherry Studio conversation to navigate pages, click controls, fill forms, capture screenshots, and investigate browser issues. It can work with authenticated websites while checking page state and action outcomes.
Operates native desktop apps through Cherry Studio Computer Use. It reads interface information, types, clicks, and captures windows, using fresh observations to choose actions and verify results within the permissions and capabilities available.
Develop and verify changes in a tracked Cherry Studio Electron instance, a running desktop app. Use real UI behavior, logs, and performance measurements to investigate problems, compare fixes, or test a pull request and report the results.
Run repeatable tests of Cherry Studio’s key workflows with Playwright, which checks application behavior through automated interactions. Collect results on macOS and Windows and produce English reports for release acceptance or development validation.