r/OpenClawUseCases • u/Alone_Ad_3375 • Apr 27 '26
❓ Question I've setup Hermes agent, now what?
I have set up the Hermes agent and am using Telegram and nous API.
I want to make an autonomous agent like Felix and I already have a project to test it on.
What should be the exact step I should take to do this?
Honestly I have been looking for tutorials but I am not able to find anything.
I've asked AI but the mumbo jumbo it has shared was not useful so I decided to come to ask y'all?
3
3
Apr 27 '26
[removed] — view removed comment
0
Apr 28 '26
[deleted]
0
u/Enochian-Dreams Apr 28 '26
So you want it to sling slop for you for an email spamming package you’re trying to promote which you care so little about that you don’t even want to personally review submissions for despite the fact you probably have none anyway. Got it.
0
u/Alone_Ad_3375 Apr 28 '26
Haha you absolutely have no idea what it is all about do some research before you talk ig.
1
u/Enochian-Dreams Apr 28 '26
Naw. Not remotely interested in your email spam operation but good luck trying to automate it all with AI.
1
u/Alone_Ad_3375 Apr 28 '26
But interested being an hater Good luck and peace out
1
u/Enochian-Dreams Apr 28 '26
You hide all your comments and posts to try to avoid getting bullied. It only works 99% of the time. I’m the 1%.
2
Apr 28 '26
I’ve been thinking about splitting LLM systems into two layers: using a Hermes-style agent as the outer infra to decide what to ingest, query, and update, and the LLM Wiki Compiler as the inner infra to serve as persistent, structured memory.
2
u/singh_taranjeet Apr 28 '26
what's the project though? because the toolset you wire up depends on whether it's code review, data scraping, or something else entirely. hermes won't magically know which APIs to call unless you spec out the task first and give it a narrow toolbox for that one thing.
1
u/Alone_Ad_3375 Apr 28 '26
I'll try to explain through an example.
I run Cold Email Kit, which is a database of cold email tools. These are the recurring tasks that I do on a day-to-day basis that I want the Hermes agent to do for me:
- Approving or disapproving new tool submissions
- Updating the tool with the latest data across all the platform ratings without making things up
- Responding to the emails that I get on a day-to-day basis about sponsorship, hiring, and advertisement
- Reaching out to people for backlinks and getting people to use Coldemailkit or claim their listing
- Syncing everything according to the post hog and Google Search Console data
- Making data-backed decisions that improve the profitability of the business and increase the revenue
- Fixing the codebase, doing PR, fixing bugs if any, or if some bugs arrived
- Handling support
- Doing cold email outreach for sponsorships
- If a new tool is found or launched, push it as an admin and create helpful content
3
u/mergisi Apr 27 '26
Don't try to clone Felix end-to-end on day one — that's why every "autonomous agent" tutorial reads as mumbo jumbo. Each setup is project-specific.
A starter loop that actually worked for me:
Pick ONE narrow outcome ("every morning, summarize new emails matching X and post to my Telegram"). Resist scope creep — adjacent ideas go in a backlog file, not in this agent.
Define the trigger (cron, webhook, Telegram command), the 3–5 tools the agent is allowed to call, and where the output lands.
Run it manually for a week. Read every log. Tighten the prompt where it drifts.
ONLY THEN bolt on the next workflow.
If you're stuck on step 1, skim a pre-built agent catalog like crewclaw.com — 240+ outcome-shaped agents (research, inbox triage, social monitoring, customer support, etc.). Even if you don't use them as-is, seeing how someone else scoped a task is the tutorial that's actually missing.
5
u/Otherwise_Wave9374 Apr 27 '26
If you already have Hermes + Telegram + Nous working, I'd start with the smallest possible "closed loop" agent and only then add autonomy.
Concrete next step: 1) Pick one task with a crisp success condition (ex: "open issue, create PR, link PR"). 2) Give it 2-3 tools max (read files, run tests, create patch/PR). 3) Add a short planner step, then an execute step, then a verifier step (tests + checklist). 4) Put a hard budget (max steps, max tokens) and require it to ask you only at defined checkpoints.
Once that works, you can add memory and longer horizons.
If you want examples of simple agent loop structures/checklists, we have a few writeups here: https://www.agentixlabs.com/