Project 02 / Hermes Agent
Less time repeating
the context.
A customised implementation of the Hermes framework for Rathin's daily work. Memory, connected tools and scheduled tasks keep useful context close to the work.
Repeated work needs somewhere to live.
Research, reports and monitoring often involve the same instructions and scattered information. A persistent setup keeps preferences and reusable workflows available between conversations.
Built on Hermes. Configured around the work.
The underlying agent framework is Hermes. This project is the customised setup around it: stored knowledge, connected tools, voice interaction and a multi-platform gateway.
A conversation can lead to an action.
The agent can browse the web, run code, manage files and execute scheduled tasks. Telegram and Discord provide ways to interact with the same system.
Useful context survives the conversation.
Persistent memory and reusable workflows reduce repeated setup. The system can use saved preferences and project knowledge when the next task arrives.
Inside the project.
This shows how the Hermes agent works. This is not the actual user interface — you can access the actual UI through the CLI, Telegram, Discord, or the Hermes desktop app. This is just to explain how it works in real life. It works very similarly to this. This is the agentic harness I'm using.