All plugins

kiro-provider

Native Kiro model provider over HTTPS, with control-plane REST calls routed to the account region, and AWS Builder ID / IAM Identity Center / Google / GitHub device login. Disclosure — dynamically registers an AWS OIDC public client named hermes-kiro during AWS login; Google/GitHub login uses Kiro's device flow at prod.us-east-1.auth.desktop.kiro.dev and its /refreshToken endpoint. Stores OAuth grants in Hermes' profile-scoped auth.json credential pool; prompts, tool schemas/results and base64 images are sent to the account's Kiro runtime endpoint. Claude and GPT catalog models declare vision, open-weight families and unknown model ids stay text-only.

anpicasso1Modelsv1.2.0Updated 2 days ago

About

Native Kiro model provider over HTTPS, with control-plane REST calls routed to the account region, and AWS Builder ID / IAM Identity Center / Google / GitHub device login. Disclosure — dynamically registers an AWS OIDC public client named hermes-kiro during AWS login; Google/GitHub login uses Kiro's device flow at prod.us-east-1.auth.desktop.kiro.dev and its /refreshToken endpoint. Stores OAuth grants in Hermes' profile-scoped auth.json credential pool; prompts, tool schemas/results and base64 images are sent to the account's Kiro runtime endpoint. Claude and GPT catalog models declare vision, open-weight families and unknown model ids stay text-only.

This plugin has no README in the catalog yet.

More by anpicasso

7 plugins by anpicasso in the catalog.

anpicassojev-approvalsTypeSafe's Jev decision model as Hermes' smart-approval reviewer only: it cannot generate text and refuses every other task. Supports TypeSafe direct, OpenRouter, and configurable Jev-compatible HTTPS endpoints with optional endpoint-specific authentication; custom and aggregator routes use a plugin-owned dispatch placeholder that is never sent upstream, while TypeSafe direct still requires TYPESAFE_API_KEY. Validates typed answers and endpoint/redirect boundaries, redacts command credentials, caps oversized commands (64000 characters by default, halving to 16000 on a context-limit response) and never auto-approves a truncated command, and records bounded structured audit logs. Disclosure — each command routed to smart approval (redacted best-effort) and the operator's smart-policy text leave the machine for the configured third-party endpoint; provider or validation failures fail closed to ESCALATE.Communitymodels25anpicassohermes-plugin-chrome-profilesSwitch every Hermes browser surface — browser_exec, the built-in browser_* tools, and browser_vault_* — to a named Chromium-family profile (Chrome, Chromium, Brave, Brave Origin, Edge), local or remote, over CDP. The endpoint is published as the active Hermes profile's live CDP override, cleanup and the CDP supervisor are profile-scoped, and a browser the plugin launched is terminated on unload. Disclosure — a launched browser is user-visible and holds the user's live logged-in sessions; remote profiles connect to an endpoint the user already runs.Communityweb15anpicassooc-free-providerUnofficial OpenCode Zen free-model transport for Hermes. Discovers live zero-cost tool-capable models by intersecting OpenCode Zen and models.dev over HTTPS, persists only the last successful intersection for restart fallback, and bidirectionally translates compatible OpenCode and Hermes tool schemas, calls, choices, and replayed history while Hermes executes tools locally. No OpenCode CLI, Node.js, npm, or npx dependency. Disclosure — prompts, tool schemas, tool results, and other conversation content leave the machine for OpenCode and the selected model provider; model availability, retention, data use, and permission are governed by their current terms.Communitymodels15anpicassocursor-providerCursor model provider using the official proprietary Cursor SDK. Disclosure — uses Cursor's proprietary cursor-sdk (PyPI, bundled binary bridge on loopback) with the user's CURSOR_API_KEY; sends the full conversation, tool schemas/results and images (HTTPS URLs or base64) to Cursor; keeps private per-session SDK workspaces under HERMES_HOME/cache/cursor-sdk. Cursor built-in tools and MCP are requested off and Hermes keeps tool execution and approvals; native custom tools are opt-in (default off) with an inert executor. Plan-only exhaustion and rejected model parameters are terminal and fail closed without fallback. The SDK passes a loopback tool-callback token on the bridge argv (not the API key) and copies the gateway environment into the bridge process.Communitymodels6

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section