Describe the job. Reuse what fits; provision a new Bot when it needs its own persistent role.
hermes plugins install bot-forge
Bot Forge is a Hermes Agent plugin that lets any agent spawn a complete, working Bot Mode Bot from one sentence — no New Agent dialog, no setup:
| The new Bot gets | |
|---|---|
| 🪪 Identity | a unique, Proper Case name and a blob face in the Bots roster |
| 📜 SOUL.md | written by your agent for that one job |
| 🧠 Memory | starter facts, plus what Hermes already knows about you |
| 🛠️ Tools & skills | file, web and browser, plus what the role needs |
| ⏰ Routines | optional cron jobs that post into its Bot Chat |
| 💬 Bot Chat | introduction attempted; sign-in may still be needed |
| 🔌 Gateway | live host serving checked; a hot-rescan is requested when needed |
Creation failures attempt cleanup of that Bot. Sign-in and gateway readiness may remain pending; the result says which. A team is not an all-or-nothing transaction.
Does this job need a new Bot?
For a generic job or team request, the existing bundled skill asks the caller to inspect the roster and relevant skills/routines first. Reuse an existing owner, a skill, temporary delegation or a routine when sufficient. Create a new profile for a justified persistent responsibility, state or configuration difference, not just a new specialty. Profiles are not security sandboxes.
This is advisory guidance, not a deterministic classifier or a new planning service. Explicit authorized profile creation remains direct, with the existing duplicate and safety checks. The same decision applies to each proposed team member.
Demo
1. Ask any Bot for a new teammate. It checks the roster, designs the Bot and calls create_agent — the new Bot (Inkwell) appears in the roster while it works:

2. The new Bot is already alive. Its Bot Chat opens with it introducing itself:

Onboarding
1. Requirements
- Hermes Agent 0.21+ with the
hermesCLI on yourPATH - Hermes Desktop for Bot Mode (the CLI works too — Bots are profiles)
- Linux, macOS and Windows are tested. CI runs the suite on all three, and the skill's
platformsis derived from that matrix rather than typed by hand. Windows came last: the reports that arrived from there were real breakage — a manifest the doctor could not read (#41), a plugin that would not load on a clean install (#38), every inter-Bot call failing for want ofUSERPROFILE(#82), and a non-UTF-8 locale crashing the plugin outright (#92). Gateway services, sandboxes and Bot Screen are still skipped there by design, so the tests covering them do not run on Windows — 33 of 482 are skipped, and the rest pass
PyYAML is installed for you: plugin.yaml declares it under python_dependencies, and
hermes plugins install puts it in the environment the plugin runs in, re-applying it after
later updates. Nothing to add to your own environment; --no-deps skips it if you manage
Python packages yourself.
2. Install
hermes plugins install BkashJEE/hermes-bot-forge
No comments yet.