A perpetual studio on your server.
Hermes is a self-hosted agent that lives on your machine, remembers what it learns, and listens on Telegram, Slack, WhatsApp, Signal, Discord, Email, and the CLI. Add pica and the same agent renders the asset, on a schedule, in the thread, without you.
Two installers, one workspace, one Hermes that grows from there.
Install Hermes Agent on the server you want it to live on. Open source, MIT licensed. WSL2 if you're on Windows.
Configure the chat surfaces Hermes should listen on, and the model providers it should reason with. Hermes saves the config to disk and remembers.
Install pica and drop the official skill into Hermes' agent workspace. From the next message onward, Hermes can call pica generate as a native verb.
An agent that ships, on its own, while you sleep.
Hermes was built to run unattended. Pica gives it a creative output channel that compounds the longer it runs.
- Scheduled renders
- Hermes does natural-language cron. Tell it once: every Monday at 9, render seven posts in the brand kit. It runs unattended and ships through the gateway.
- Multi-surface dispatch
- The same generated asset can land in Telegram, Slack, WhatsApp, Signal, or Email — Hermes picks the surface, pica produces the file.
- Subagent fan-out
- Hermes can spawn isolated subagents with their own context. Use one to render four palette variants in parallel without polluting the main thread.
- Persistent memory
- Hermes remembers your brand kit, your house style, the last campaign. Pica scopes outputs to the project; together they compound across runs.
- Real sandboxing
- Local, Docker, SSH, Singularity, or Modal backends with namespace isolation. Pica generations execute inside the same hardened envelope.
Three moments Hermes with pica handles natively.
9am, every Monday
Hermes wakes on schedule, asks pica to render the week's seven posts in the saved brand kit, and queues them into the surfaces you told it to publish to.
One asset, every surface
Tell Hermes to ship the launch image. It renders once with pica, then dispatches the same file to Telegram, Discord, and Slack channels in parallel.
Subagents in parallel
Hermes spawns four isolated subagents. Each one renders a variant of the same brief through pica, then returns thumbnails to the parent thread for review.
One server. Many surfaces. Pica turns Hermes into a studio that never sleeps.