Authorization notice. Fish Audio Hermes is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Credentials. Your Fish Audio API key is saved to the active Hermes profile, so do not paste it into chat; `/fish` refuses keys sent in chat.
Who it is forA Hermes Agent user who wants replies, read-aloud and voice notes spoken aloud in the CLI or a messaging app.
The problemHermes needs a speech provider and a saved key before it can speak, and the setup has several steps.
The outcomeThe agent speaks through Fish Audio, and the setup check confirms that one test synthesis works.
What you need first
- Hermes Agent installed, with the plugin install command available
- A Fish Audio account and API key from https://fish.audio/app/api-keys
- Fish Audio API credit, or the free s2.1-pro-free model for new accounts (free through 30 November 2026)
Steps
- Run
hermes plugins install fish-audio --enableon the machine that runs Hermes. - Run
hermes fish loginand paste your key from https://fish.audio/app/api-keys. - Answer the provider prompt, or pass
--yesif you want Fish Audio to replace another speech provider. - Run
hermes fish doctorto make one short billed synthesis, orhermes fish doctor --no-synthto skip it. (inferred, check the README) - Ask the agent to read a short reply aloud and listen to the result.
Prompt for your agent
Using the repo 100yenadmin/fish-audio-hermes, install the Fish Audio plugin for Hermes Agent on <target machine> and run the setup check with `hermes fish doctor --no-synth`. Expected output: the plugin is enabled and the status check reports no errors. Verify that `hermes fish status` shows Fish Audio as the speech provider.
Caveat. Hermes 0.21.6 and newer ask before installing Python dependencies, and older Hermes versions install them without asking.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page