hermes-agent-builder

Guided Desktop workspace in BOTS: tailored questions, reference files, editable instructions and capabilities, version comparisons, model-only trials, and native Bot Chat handoff. Saves specialists as separate Hermes profiles and installs the Builder companion plugin into its own bot profile. Disclosure — "Talk to Builder" auto-creates a hermes-builder profile cloned from the active profile with copied .env/auth.json and copies+enables this plugin there outside the catalog installer (uninstall does not remove that copy); "Save agent" creates new profiles the same way and rewrites their tool/skill selection.

itsflowniumDesktopv1.0.0Updated 1 month ago

About

Hermes Agent Builder

Maintained by itsflownium. A community plugin for Hermes Desktop.

A dedicated Hermes Desktop section that turns a conversation about your needs into a reusable specialist agent.

Describe the job → answer Hermes's questions → refine the blueprint → try real work → save the agent.

The entry appears only while BOTS is selected. Saved specialists live in the native bot roster. The package uses Hermes's native Desktop Plugin SDK, plugin API namespace, model facade, and profile creation/configuration APIs. It does not patch Hermes core.

Demo

Watch the 69-second Launchsmith demo — a release-writing specialist built from a real brief, from interview through native Bot Mode handoff.

Builder workspace

The recording uses the actual plugin UI in an isolated demo shell, with model responses replayed from a real run to shorten waiting. Native profile saving and its canonical Bot Chat were verified separately. The film labels those boundaries. The logo and music are original.

Install

Install directly from this repository:

hermes plugins install https://github.com/itsflownium/hermes-agent-builder
hermes plugins enable hermes-agent-builder

Catalog inclusion is pending maintainer review. After admission, the install identifier will be hermes-agent-builder.

Requires a recent Hermes Desktop with the Desktop Plugin SDK and Plugin LLM Access (validated against Hermes source 449fae030a, September 2026), and Python 3.11 or newer.

Extract the package, then run from this folder:

macOS:

python3 install.py --enable

Windows PowerShell:

py -3 install.py --enable

If Python cannot find Hermes, use its Python interpreter or run the native enable command separately:

hermes plugins enable hermes-agent-builder

In Hermes Desktop, open Capabilities → Plugins, rescan if needed, then enable Hermes Agent Builder's Desktop component. The agent and Desktop components have separate native enable switches. Reconnect an already-running backend once to mount the API routes. Your model must be signed in/configured in Hermes.

Use --home <path> for an explicit profile home; use --update for a code update. Runtime data remains in Hermes's profile-scoped plugin-data/hermes-agent-builder/ and survives code updates.

Use

Select BOTS, then choose Agent Builder in the top bar. Talk to Builder opens the conversational companion in the native bot roster.
Describe a recurring task. Add a short text reference file if useful.
Answer Hermes's tailored questions in your own words or choose a suggestion.
Review the agent's name, instructions, capabilities, and examples. Refine it conversationally or edit its instructions directly.
Choose Try it and provide a real task. After a refinement, compare the two versions on the same prompt.
Choose Save agent, then Open in Bot Mode to start its canonical native Bot Chat.

The saved agent gets a separate profile. It clones the source profile's configuration and installed skills, with fresh memory and chat history. Hermes handles credential inheritance; messaging channels are not cloned. The builder selects the requested skills/toolsets and leaves MCP servers disabled until configured in Hermes. Review access in the native profile editor if your specialist needs connected services.

The exact tool list is pinned, including an empty selection for a conversation-only bot. Hermes's essential hermes-agent skill always remains enabled; other skills follow your selection.

The trial uses instructions and supplied reference material with the host's model. It does not execute connected tools or simulate their results. Use the saved agent's native chat to exercise tools. Each blueprint change starts a new trial context; old trial results do not validate new instructions.

Reference files: UTF-8 .txt, .md, .csv, .json, .yaml, .yml; up to six files and 60,000 characters combined. Reference contents are source data, not standing instructions.

Copy blueprint copies portable instructions and references, without credentials, chat history, or memory. Drafts are persisted on the backend. Saved profiles are managed through Hermes's profile editor.

Briefs and answers also survive frontend reloads. Model requests have bounded timeouts, elapsed-time feedback, and a Stop waiting control. Stopping the wait does not cancel a server request already running; check My agents before retrying. Optional malformed model suggestions are ignored so the actual question and free-text answer remain usable.

CLI and agent use

/build-agent Make a study coach that explains one concept at a time and asks me a practice question.

The agent_builder tool creates or refines a draft in a normal conversation. The desktop section provides the full guided interview and save flow.

Platform support and validation

One package runs on macOS and Windows: no shell-dependent runtime, hardcoded Unix paths, Node APIs in the renderer, or external JavaScript imports. The installer resolves native Hermes homes (including Windows LocalAppData) and preserves profile data. The UI adapts to narrow windows, native themes, keyboard control, and reduced-motion preferences.

The code avoids platform-specific runtime dependencies, and installer paths containing spaces are tested. A native Windows/Electron run still needs validation on Windows; this package does not claim it was performed.

See VALIDATION.md for the completed checks and demo evidence.

Development

The Python backend registers commands/tools through register(ctx) and calls ctx.llm. REST requests invoke the same registered command. Storage resolves the active profile on every operation; SQLite transactions prevent stale in-flight responses from overwriting newer drafts.

The desktop half is plain ESM using only @hermes/plugin-sdk and React. No frontend build step is required.

Files:

plugin.yaml                  native plugin manifest
__init__.py                  registrations
builder.py                   interviews, blueprints, trials, storage
desktop/plugin.js            BOTS-only entry and guided builder UI
dashboard/plugin_api.py      profile-aware REST endpoints
install.py                   portable installer
examples/launch-brief.md     real demo source material

README from the reviewed commit 6ed39da; it updates when the author re-pins.

More by itsflownium

4 plugins by itsflownium in the catalog.

itsflowniumcrystallizeSpend less on repeated work in Hermes chats and cron jobs, without making your model think less: trims repeated context and tool output in chats, and lets a cron job skip its AI run when its input has not changed, with local receipts showing what each change saved. Disclosure — reads Hermes session costs, user-message counts and final cron answers (state.db, read-only), cron outcomes and job definitions (cron/executions.db, cron/jobs.json) and your config and rate cards; looks up public model prices from the active route's /models endpoint and models.dev once a day with no credentials or chat data (off with hermes crystal prices --lookup off); the optional helper, compare and check features make paid model calls through your own Hermes route; cron tuning, promote and undo run hermes cron CLI commands that edit the chosen job, choosing a helper model or deferring tools runs hermes config set (auxiliary.crystallize_chat, tools.tool_search.defer), and generated pre-run wrappers, drafted snapshot scripts (which replay the job's recorded shell commands and URL reads) and approved snapshot scripts are written under scripts/crystallize/, scripts/crystallize-drafts/ and scripts/crystallize-native/ and run as ordinary cron scripts once attached; in CLI and TUI chats posts one short status line after each turn with ctx.post_message (never on Desktop or messaging platforms; off with /crystallize line off); stores captured tool results, cache entries and receipts in its plugin-data folder; no telemetry, no credential reads, no self-update.Communityautomation itsflowniumgambitPlay chess in a Hermes terminal or Desktop pane, understand mistakes, and replay or practice public Chess.com and Lichess matches. Disclosure — runs a locally installed Stockfish executable (the path you set in plugin settings, or one found on PATH) as a subprocess that inherits Hermes' environment; fetches public games for a username you enter from api.chess.com and lichess.org; uses your configured Hermes model for each opponent move; and in Coach mode the Desktop pane automatically sends coaching requests into the bound chat when it is idle, each starting a model turn.Communitytools itsflowniumletheTake one chat off the record with /lethe: nothing reaches memory, your profile or skills, the transcript is deleted, and a river shows every write it kept out. Use an external memory provider? Copy this into a Hermes chat and replace <PROVIDER> with yours: Extend my local Lethe plugin (~/.hermes/plugins/lethe) so off-the-record chats also skip my <PROVIDER> memory provider's per-turn sync, session-end extraction and save tools when store.is_on(session_id) is true. Show me the diff, add a test, then run hermes gateway restart. Disclosure — Deletes the off-the-record chat's transcript (and its compression chain) from Hermes's session database via SessionDB.delete_session when the chat ends, on /lethe-end or /lethe-forget, or from the Desktop panel's Delete transcript now (unless keep_transcript is on); while on, it blocks memory, user-profile and skill writes plus provider tools whose names look like saves, and adds a fixed off-the-record note to each turn's context; external memory providers' per-turn sync is not blocked.Communitymemory

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section