Hermes does the work. Fractask remembers.
A long-running agent and a hierarchical task tree, finally in the same loop. Hermes spawns the work — across Telegram, Discord, Slack, WhatsApp, Signal, email, CLI. Fractask gives every action a place to live, every result a place to be found.
Hermes is the open-source autonomous agent from Nous Research — MIT-licensed, runs on your own server, tagline “the agent that grows with you.” Persistent memory. Auto-generated capabilities. Skills it keeps, session after session.
It works across the messengers your team already lives in. Schedules itself in plain language. Spawns sandboxed subagents for the parts that need them. It’s the closest thing to a colleague who’s actually there at 3am when you need something done.
The only thing it’s missing is somewhere to put the work.
The agent loops. The tree grows.
- 01
Every Hermes action is a Fractask node.
When Hermes picks up a goal, it lives as a parent task. Each subagent it spawns is a child. The tree IS the audit log.
- 02
Persistent memory, structured.
Hermes remembers across sessions. Fractask gives that memory a shape — projects, tasks, parts — so the next time Hermes shows up, it knows exactly where it left off.
- 03
Cross-channel work, single source of truth.
Start a job in Telegram, fork it in Slack, finish it via CLI. The channel is incidental. The Fractask tree is the same tree, every time.
- 04
Human-in-the-loop, where it matters.
Hermes flips a part to status="review" and pings you. You approve in the web app or with one MCP call. The agent moves on. No babysitting.
- 05
Scheduled work, made of parts.
Hermes schedules itself in plain English. Each fired run lands a fresh subtask under the right parent — recurring work compounds into a real history instead of vanishing.
Point Hermes at the Fractask MCP server. Six tools. No glue code. The two of them figure it out from there.