# AI use cases for Hermes Bot Forge (BkashJEE/hermes-bot-forge) Repo: [BkashJEE/hermes-bot-forge](https://github.com/BkashJEE/hermes-bot-forge) | Use cases: 5 | Page: https://dedupedai.com/use-cases/bkashjee-hermes-bot-forge/ Bot Forge is a Hermes Agent plugin that builds a complete, working Bot, with a name, face, SOUL.md, memory, tools, skills and gateway, from one sentence. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Build a single-purpose Bot from one sentence: https://dedupedai.com/use-cases/bkashjee-hermes-bot-forge/build-a-single-purpose-bot-from-one-sentence/ - Assemble a small team of Bots with one lead: https://dedupedai.com/use-cases/bkashjee-hermes-bot-forge/assemble-a-small-team-of-bots/ - Keep every Bot on one shared operating policy: https://dedupedai.com/use-cases/bkashjee-hermes-bot-forge/keep-every-bot-on-one-shared-policy/ - Route Bots to a local model when sign-in fails: https://dedupedai.com/use-cases/bkashjee-hermes-bot-forge/run-bots-on-a-local-model-fallback/ - Share one OAuth login across new Bots: https://dedupedai.com/use-cases/bkashjee-hermes-bot-forge/share-one-oauth-login-across-bots/ ## How to build a single-purpose Bot from one sentence with Hermes Bot Forge Repo: [BkashJEE/hermes-bot-forge](https://github.com/BkashJEE/hermes-bot-forge) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Describe a job in one sentence and get a working Bot with its own identity and tools. **Who it is for:** A solo operator who needs a dedicated assistant for one recurring job, such as writing social posts, and does not want to set up a new agent by hand. **The problem:** Setting up a separate agent with its own role, memory and tools takes manual configuration for every new job. **The outcome:** A new Bot appears in the Bots roster with a name, face, SOUL.md written for that job, and an introduction in its Bot Chat. ### Steps 1. Run `hermes plugins install bot-forge` 2. Run `hermes plugins enable bot-forge` 3. Run `hermes gateway restart`, then quit and reopen Hermes Desktop 4. Run `hermes bot-forge-doctor` and fix anything it reports as missing 5. Open Bot Mode, click the Bot you enabled, and type: make me a bot that writes x.com posts and threads 6. Wait 1 to 3 minutes, then open the new Bot and check that its Bot Chat has its introduction ### Prompt to paste into your agent ```text Using the repo BkashJEE/hermes-bot-forge, ask my enabled Bot to create a Bot for . Expected output: a reply naming the new Bot, its job and the tools it received. Verify by running `hermes bot-forge-doctor` and confirming the new Bot appears in the Bots roster. ``` ### Caveat The reply says whether the Bot still needs a sign-in or a gateway rescan, so check the result before relying on the new Bot. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/bkashjee-hermes-bot-forge/build-a-single-purpose-bot-from-one-sentence/ ## How to assemble a small team of Bots with one lead with Hermes Bot Forge Repo: [BkashJEE/hermes-bot-forge](https://github.com/BkashJEE/hermes-bot-forge) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Create a lead Bot and its members in one team request. **Who it is for:** A manager or operator who needs several Bots that split one larger job, each with a clear responsibility. **The problem:** Building each team member by hand is slow, and a half-built team is hard to track. **The outcome:** A lead Bot and its member Bots are created, with a per-member result saying what finished and what is still pending. ### Steps 1. Complete the install and enable steps for Bot Forge on your main profile or manager Bot 2. Run `hermes bot-forge-doctor` and confirm the manager profile is listed as enabled 3. Ask the manager Bot to create a team with `create_team`, naming a lead and its members and their jobs 4. Review the result, which reports each Bot's sign-in and gateway status 5. Run `check_agents` to confirm the team members exist and their configs are correct ### Prompt to paste into your agent ```text Using the repo BkashJEE/hermes-bot-forge, ask the manager Bot to run create_team for with a lead and members. Expected output: a per-member result listing each Bot as created, pending sign-in, or failed. Verify by running check_agents and confirming every member is listed. ``` ### Caveat A team is not all-or-nothing, so a partial result is expected and each pending member has to be checked separately. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/bkashjee-hermes-bot-forge/assemble-a-small-team-of-bots/ ## How to keep every Bot on one shared operating policy with Hermes Bot Forge Repo: [BkashJEE/hermes-bot-forge](https://github.com/BkashJEE/hermes-bot-forge) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Edit one policy file and push it to every Bot built by Bot Forge. **Who it is for:** An operator with several Bots who wants the same rules on each one, such as no spending without asking, without copying text into every SOUL.md. **The problem:** Rules pasted into many SOUL.md files drift apart over time and are hard to keep consistent. **The outcome:** One edited policy file reaches each Bot, and stale Bots are listed so you can refresh them. ### Steps 1. Run `$EDITOR ~/.hermes/shared/BOT-POLICY.md` and edit the shared policy 2. Run `check_policies` to list which Bots are stale or opted out 3. Run `update_agent` with `refresh_shared_policy: true` for each stale Bot 4. Run `check_policies` again to confirm no Bot is listed as stale ### Prompt to paste into your agent ```text Using the repo BkashJEE/hermes-bot-forge, edit ~/.hermes/shared/BOT-POLICY.md and then run check_policies. Expected output: a list of stale Bots and Bots that opted out with no_shared_policy. Verify by refreshing one stale Bot with update_agent and confirming it no longer appears in the stale list. ``` ### Caveat The policy is prompt text the model is asked to follow, not enforced, so nothing blocks a tool call that breaks a rule. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/bkashjee-hermes-bot-forge/keep-every-bot-on-one-shared-policy/ ## How to route Bots to a local model when sign-in fails with Hermes Bot Forge Repo: [BkashJEE/hermes-bot-forge](https://github.com/BkashJEE/hermes-bot-forge) | Difficulty: Advanced | Time: 60 minutes | Basis: From the README Set a fallback model so new Bots still run when their inherited login is not ready. **Who it is for:** A user whose main model uses OAuth sign-in, who wants new Bots to keep working on a local model server. **The problem:** An OAuth-based Bot needs a per-Bot sign-in before it can answer, which stops it from working right away. **The outcome:** New Bots switch to a configured local model when their inherited model cannot sign in. ### Steps 1. Run `hermes plugins enable bot-forge` on the profile that creates Bots 2. Open that profile's config.yaml and set `plugins.entries.bot-forge.settings.fallback_model` to a local model with its base_url 3. Run `hermes bot-forge-doctor` to confirm which sandbox backends and models this machine can run 4. Create a Bot and check its result for the sign-in status ### Prompt to paste into your agent ```text Using the repo BkashJEE/hermes-bot-forge, set fallback_model in the bot-forge settings to a local model at and create a Bot. Expected output: a result that names the model the Bot is using and whether a sign-in is still needed. Verify by running hermes bot-forge-doctor and checking the model status it reports. ``` ### Caveat The README says a local model server must be running at the base_url you set, and it does not say the plugin starts one. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/bkashjee-hermes-bot-forge/run-bots-on-a-local-model-fallback/ ## How to share one OAuth login across new Bots with Hermes Bot Forge Repo: [BkashJEE/hermes-bot-forge](https://github.com/BkashJEE/hermes-bot-forge) | Difficulty: Advanced | Time: 30 minutes | Basis: From the README Copy the root profile's login into a separate file so new Bots can use it. **Who it is for:** A user with an OAuth model subscription who wants new Bots to work without a sign-in for each one, and accepts that the helper is unsupported. **The problem:** Every new Bot needs its own sign-in for an OAuth model, which adds a manual step for each one. **The outcome:** New Bots can use the shared login, copied as an independent file with permissions 0600. ### Steps 1. Review the README section on the shared login helper and confirm you accept that it is unsupported 2. Run `python extras/share_login.py` from the repo 3. Create a new Bot and check its result for the sign-in status 4. Confirm the Bot's credential file has permissions 0600 ### Prompt to paste into your agent ```text Using the repo BkashJEE/hermes-bot-forge, run python extras/share_login.py and then create a Bot for . Expected output: a Bot whose result does not ask for a per-Bot sign-in. Verify that the copied auth file has permissions 0600 and that auth.lock was not copied. ``` ### Caveat The README says the plugin itself never touches credentials and that this helper is unsupported and runs only when you run it yourself. Risk, credentials: The helper copies your root profile's auth.json, so every Bot receives a copy of that login and you must protect those files. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/bkashjee-hermes-bot-forge/share-one-oauth-login-across-bots/