Plugins by Kame696
2 plugins by Kame696 in the catalog, most-starred first.
Kame696hermes-kame-api-rotationSmart API key rotation: the healthiest key for every call, each 429 / RESOURCE_EXHAUSTED / quota refusal sized from its own evidence. Install with its companion hermes-kame-provider, which hands Hermes this plugin's rotating client through ProviderProfile.create_client (and create_messages_client where Hermes offers it); no core override. When Hermes has a fallback list, a reply whose model is busy, resting or slow moves down a ladder: the model the reply started on, then the main model (model.default), then the rest of the list; a model of the same provider answers inside the plugin on the same keys and endpoint, a model of another provider is handed to Hermes' own fallback (which walks the list), and a late reply can be raced by the next model of the same provider; nothing moves once part of the reply is on screen, and never_fall_back_to_another_model turns every switch off (the plugin reads the model and fallback_providers from config.yaml, read-only; no new network destination). Disclosure — /kame-keys add|import|split, and on start a key variable holding several comma-joined keys, write one auth.json pool row per key through Hermes' pool API after an owner-only plaintext backup (last 5 kept; switch: resolver_disabled); settings changed from /kame or the Desktop panel are saved as KAME_* lines in Hermes' .env; key-redacted, size-capped owner-only local logs (current file plus one previous), a status file, a small lifetime-counters file (replies answered and saved, requests sent per model in 24 hours, the provider's stated daily limit; no key, prompt or text) and a small model-health file (the time and the success or failure of each model's last judged outcomes, at most 7 days; no key, prompt or text) per profile; the Desktop panel reads that file and queues its settings requests through its own dashboard/plugin_api.py route (GET /state, POST /control, this plugin's plugin-data folder only); after Hermes' own fallback answered a reply, the Desktop page sets that conversation's model back to the model the reply started on with config.set --session (never --global; config.yaml is not written); while every key is resting and no fallback model can take over, chats (CLI, Desktop, messaging gateway) keep waiting with no total limit (each key's rest capped by max_hold_seconds) and cron runs give up after 300 s with the provider's refusal unless max_total_wait_seconds is set. Optional speech: where Hermes offers register_tts_provider, the plugin registers a text-to-speech provider named kame-gemini, unused until the owner sets tts.provider: kame-gemini; it sends each sentence to Gemini's own endpoint on the owner's Gemini keys, rotated like the chat's, rests a refused key as long as Google said and waits at most once, under 2 s, for a key about to come back. Optional listening: where Hermes offers register_transcription_provider, the plugin registers a speech-to-text provider named kame-gemini, unused until the owner sets stt.provider: kame-gemini; it sends the recording to Gemini's own endpoint on the same keys, rotated the same way. Extra billed requests (chat replies only, plain API keys only - a credential Hermes records as a subscription is never raced; hedge_mode off turns them all off): a late reply, or one whose model has just answered busy (a 5xx on a key: the next model of the list is then asked beside the retry at once), may also be sent to up to two more keys of the same model (about 10% of replies, 30% in "Faster", bursts of 3), to up to two next models of your fallback list on the same provider, keys and endpoint, and to one more model of the list when it stays silent; a best model that is busy, or remembered as failing (its latest judged outcome failed, with at least two failures in its last ten within seven days; the reply then starts on the next model of your list, and KAME_NO_REMEMBERED_TROUBLE=1 turns this off), may be asked again beside a reply every 20 s - less often the longer it keeps failing, at most every 5 min - and that ask is heard to its first word or 30 s; a model of the list left out for its record is a candidate again 10 min after its latest failure (doubling, at most 2 h); when keys keep coming back out of quota the next attempt asks 4, then 8, then up to 16 keys at once (probe_burst_max_legs); and a reply that showed a thought and then went quiet with nothing shown past its learned limit (8-20 s, at most 90 s; thought_quiet_s sets it, 0 turns it off) may be asked once more on another key of its model (the same key when it has only one) and once on the next model of your list (another key of the same model when no other model may be asked), its thoughts still shown live, the first to show text or a tool call being the answer; if those stay silent too, the reply is handed to the next entry of your list; and an answer that has begun and then sends nothing for answer_quiet_s (45 s; 0 turns it off; never while a tool the provider runs on its side is in flight) is continued with one more request. Titles and other background jobs are limited to a few requests and are stopped with a timeout so Hermes moves them down your own list; a title on a model remembered as failing, or busy, goes once to the first healthy model of your list on the same provider.Communitymodels4Kame696hermes-kame-providerCompanion to hermes-kame-api-rotation (install both). A model-provider plugin that re-registers Hermes' bundled API-key profiles unchanged except for create_client and create_messages_client, which return the rotation plugin's key-rotating client; otherwise None and Hermes builds its own. Same endpoints as Hermes, no third-party service, no core override.Communitymodels4
GitHub profile
