This plugin has no README in the catalog yet.
All plugins
hermes-nous-prices
Browse Nous Portal model prices and account balances in Hermes Desktop.
More by Adolanium
30 plugins by Adolanium in the catalog.
AdolaniumgadgetTalk to your Hermes from small ESP32 devices with a screen, microphone and speaker: hold a button, ask, and hear the answer. Adds a gateway platform where each device is a chat, plus tools to list devices, show a card on a screen and run device actions (LEDs, relays). Disclosure — the gateway listens for devices on a WebSocket port (8765, all interfaces by default; plain ws:// unless tls_cert/tls_key are set). New devices need a Hermes pairing code unless listed in GADGET_ALLOWED_USERS; GADGET_ALLOW_ALL_USERS skips pairing (development only). A paired device answers the agent's command approvals for its own chat (allow once or deny), within Hermes's approval timeout. The first approved device becomes the platform's home channel by default. Session hooks feed a dashboard on paired devices with each agent session's platform, a short id and its state (idle, busy, waiting for approval); a device that can switch profiles also sees the offered profiles' sessions. Optional profile switching (off unless profiles is set in the default profile's gadget config) lets a device paired on the default profile talk to the listed profiles; each profile approves the device through its own pairing flow (the device shows the hermes -p <profile> pairing approve command), the plugin writes nothing into other profiles, and revoking the device in the default profile sends it back there. A paired gadget that draws faces gets the answering profile's face: its gadget-face.bin, or its Hermes avatar (assets/avatar.*) converted with Pillow when installed; the plugin only reads these files, and profile_faces: false turns this off. platforms.gadget.extra.stt_language sets the transcription language of gadget recordings through the pre_transcription hook; other platforms' audio is untouched. Spoken replies that are not WAV are converted with the local ffmpeg; Opus reply audio uses the host's libopus when installed (loaded with ctypes, not bundled). hermes gadget update --latest downloads firmware from this repository's GitHub releases, checks size and SHA-256 against the release manifest (files carry build provenance attestations) and sends it to the device. A device that advertises camera.capture returns stills that are saved as PNGs under ~/.hermes/gadgetpix/ and kept until removed by hand. A Hermes Desktop page (desktop/plugin.js, plugin SDK only) runs a gadget in the window that connects to the local gateway as a device of its own: its device key, and the gateway access token when one is required, are kept in the page's plugin storage, it pairs like any device, and it uses the microphone only while its talk button or Space is held. The plugin's dashboard routes, behind the dashboard's login, can approve the pairing code a device is showing and send a card or run an advertised action on a connected, paired device; the requests pass through files under plugin-data/gadget/desk/. gadget_play plays audio on a device's speaker: a local file only from Hermes's audio cache and the folders in play_dirs, or an http(s) URL fetched under Hermes's URL safety policy (private and internal addresses refused, every redirect checked), decoded by the local ffmpeg, which is given no network or file access of its own and reads audio containers only; playback stops after play_max_minutes (60). Interpreter mode (hermes gadget interpret or gadget_interpret) translates what two people say on a device: the plugin transcribes each recording, asks the model for the translation through Hermes's plugin completion API with no tools, and speaks it; nothing reaches the agent or a session, and no transcript is kept. Widgets set with hermes gadget widget or gadget_widget are kept under plugin-data/gadget/. hermes gadget diag <device> and the dashboard's Save diagnostics report ask a connected device for its report and save it with the gateway's last 500 Gadget log lines, as a text file: from the CLI to --out or the current folder, from the dashboard as a browser download. hermes gadget bot-chat hands requests to the gateway through files under plugin-data/gadget/bot-chat/ and reads the profile's session store read-only. Messages and cron output sent to a device outside a turn are spoken on devices that speak replies. Otherwise writes only under plugin-data/gadget/. Uses Hermes's own STT, TTS and image cache; no telemetry. Independent community project, not affiliated with Nous Research.Communityplatform573AdolaniumwhiteboardAn agentic whiteboard. Say what you're planning and Hermes lays it out as a route, columns or a map, with hand-drawn stickers. Add rough notes and Hermes proposes groups, owners and action items that you accept one by one and can take back. Hand an action item to Hermes and an agent does it on the board and delivers the result next to the note with its sources, or run the whole route and get a brief at the end. Select anything and ask about it. Once you allow it, any chat can read your boards and propose changes. Link a board to the chat its work is in: the board shows what that chat is doing, and the chat hears what you change on the board. Send notes to Hermes Kanban or lay a Kanban board out as a whiteboard. Disclosure — laying out a board, grouping notes, unpacking a result and the brief each start a hidden Hermes session told to use no tools; Hand to Hermes, Run the route and Ask start hidden sessions that use your Hermes tools and read third-party web pages, at most three at once, each stopped after 4 minutes or 24 tool calls; approval prompts inside these sessions are denied; export writes the one Markdown or CSV file you name in the system dialog, through the plugin's own backend; boards live in Desktop plugin storage, with a copy under plugin-data/whiteboard/ only after you turn on chat access, which starts off, and each Hermes profile that has the plugin keeps its own copy; a Planning model and an Agent model in Settings name a model you are signed in to in Hermes when a session is created, and a refused model stops the run; with the Sheets or Data plugin installed, a click on that page pins notes to the open board through a window event, with no file, backend or model involved; Send to Kanban and New board from Kanban make the plugin's backend run the hermes kanban command, with no shell and with note text passed after -- and on standard input, to list boards, create cards and read a board; cards are created in Blocked with no assignee, and in Triage, which Hermes works through on its own, only when you tick a box; while the page is open on a board that has Kanban cards it reads those Kanban boards about every 25 seconds, and it never changes a card after making it; a board can remember the id of the chat it is linked to, the page places a request in that chat's message box for you to send and never sends it, and after that it listens to that one chat for up to 30 minutes and reads its answer from the transcript; the plugin registers four hooks (pre_llm_call, post_llm_call, on_session_end, post_compaction) that run on every chat turn and return at once unless the chat is linked to a board; for a linked chat they keep the state of its latest turn and the first line of its answer under plugin-data/whiteboard/, and, only while chat access is on, add to the message you send in that chat a short notice that the board exists and the notes you added, edited or removed on it since the chat's last turn; the plugin never sends a message to a chat; the linked chat can put a doing, done or blocked mark on its own board's notes with no review, which changes nothing else and clears with a click; which chat each board is linked to is kept under plugin-data/whiteboard/ as ids only, whether or not chat access is on; no telemetry, no credentials, no background processes of its own, and no command other than hermes kanban. Independent community project, not affiliated with Nous Research.CommunityDesktop app98Adolaniumhermes-resetwatchTrack subscription quotas and reset times in Hermes Desktop. Disclosure — probe.py re-executes itself under the Hermes Python interpreter located via HERMES_PYTHON / VIRTUAL_ENV / the parent process or the Hermes installer's managed venv (HERMES_HOME/installs). Every credential read is read-only and nothing is refreshed or stored: it reads provider API keys from the process environment, the Hermes .env (through Hermes's get_secret helper, else read directly), the Vaultwarden plugin's local secret cache (cache/vaultwarden_cache.json, only when Vaultwarden is the sole enabled secret source, keyed by a hash of BW_SESSION, which is never sent) and Docker s6 container env files; Hermes's saved OAuth logins (the credential pool through Hermes's read_credential_pool helper, else auth.json directly, and HERMES_HOME/.anthropic_oauth.json; for Nous plans with usage windows, the saved Nous portal login through Hermes's stored_token_account_info helper, sent as it is to the Nous portal and never refreshed); and other coding-assistant CLIs' local logins: Claude Code (credentials file, macOS keychain or Windows Credential Manager), Codex, Cursor (macOS keychain and the IDE's state.vscdb, opened read-only), Kimi, Grok, ZCode and Command Code. For GitHub Copilot (on by default) it tries COPILOT_GITHUB_TOKEN / GH_TOKEN / GITHUB_TOKEN (through Hermes get_secret, else the process environment), then the Copilot editor's apps.json / hosts.json, then runs gh auth token (prompts disabled, 3-second limit), trying each token in turn until GitHub accepts one. For Codex, a 401 or 403 is retried once with another saved login for the same account. It sends each key only to its own vendor's usage endpoint, presenting the vendor client's identity headers where a private endpoint expects them (Claude Code and Codex CLI user agents, the Grok CLI client headers, and for Copilot the VS Code / Copilot Chat editor headers on api.github.com/copilot_internal/user, which GitHub does not document); environment variables such as GROK_CLI_CHAT_PROXY_BASE_URL (honored only for https grok.com / x.ai hosts), CLAUDE_CONFIG_DIR, CODEX_HOME and GROK_HOME change which host or file it uses. Usage results are cached under HERMES_HOME/cache/resetwatch, never tokens. It exposes nothing to the model: it is a Desktop page only.CommunityDesktop app92Adolaniumhermes-rssRead RSS and Atom feeds and discuss articles in Hermes Desktop. Disclosure — feeds and full articles are fetched with curl through the gateway's shell.exec on the connected Hermes host (public-IPv4 SSRF guard); opt-in AI grading sends article excerpts to your configured model and creates HERMES_HOME/skills/rss-importance-grading/SKILL.md if missing; opt-in image loading fetches publisher images directly from Desktop.CommunityDesktop app66
Developer Mode
Explore built-in Hermes toolsets and actions.

Adolanium


