Different setup methods
Some projects install as Hermes profiles. Others are collections, examples, or tools with their own setup process.
Learn · use · build · deploy Hermes Bots
A working cabinet of Hermes Bots
Browse practical Hermes Bots by the job you need done. Each listing explains what the Bot does, what it needs, how to set it up in Hermes Desktop, and its current review and test status. Each Bot keeps its own continuing conversation, role, memory, tools, and history. You can also plan your own Bot and follow step-by-step workflows that use several Bots together.
Practical starter roles Step-by-step setup guides Source and test status shown
See Bot Crews workflows 
IllustrationChoose your Bot Cabinet starting point
Choose your Bot Cabinet starting point
Choose a Hermes Bot
The Cabinet
Bots that work together
Bot Crews
Plan your own Bot
Bot Lab
Browse community projects
Community RegistryNew to Hermes Bots? Start with the Field Manual
Learn the basics, choose a role, and test it with sample material.
Understand what a Bot is
Learn how a Hermes profile gives a Bot its own continuing conversation, role, settings, memory, and history.
2Learn how to inspect a public Bot package
Review its source, requested access, setup, and test status.
3Read the first-test checklist
Learn how to test with low-risk sample material before adding access.
Why the Community Registry exists
Public Hermes profiles are difficult to compare
The Community Registry lists selected public projects with exact source versions, plain-English uses, and separate review and test status. Their setup methods, documentation, and requested access vary.
Unexpected files
A profile package can copy more files than a user expects when its file list is missing or too broad.
Private material
Before using a public package, check its current files and Git history for memories, sessions, local files, credentials, and client material.
Incomplete testing
A public repository shows what the publisher shared. Installation and Desktop testing require separate checks.
The Community Registry lists only a small set of projects with a clear purpose and current source information.
Browse community projectsInside every Bot Cabinet listing
Know what a Bot does before you set it up
Each listing explains the job, gives example requests, describes the expected result, lists setup requirements, and states the current review status.
Understand the review and test labelsOriginal files
Hermes Bots include downloadable public files. Community Registry listings link to the publisher’s repository and a recorded version.
Specific review status
Community Registry pages identify one exact source version and report automated source scan, human technical review, and Hermes Desktop test status separately. Starter pages state their own review and test status.
Clear access decisions
Bot pages list the information you provide, the tools or outside services involved, and the decisions that stay with a person.
Why Bot Cabinet exists
“I wanted to help people understand what a Bot can do and give them a practical place to begin.”
Damon Gardenhire built Bot Cabinet through LINCHPIN and AI for the Real World: a practical project for nontechnical people who want useful examples, clear setup guidance, and a better understanding of what Hermes Bots can do.
Meet the founder and learn why Bot Cabinet existsInside Bot Lab
Describe the job in eight practical fields
Bot Lab records the job, inputs, deliverables, tools, schedule, approval points, and first test. It gives you role instructions and a downloadable plan for Hermes Desktop.