Claude Cowork + Hermes Together
Most comparisons ask "Cowork or Hermes?" — but the highest-leverage setup uses both. Pair paid Claude Cowork for premium, high-judgment knowledge work with a free, always-on Hermes agent for the repetitive background running, and you get top-tier quality where it matters without paying premium rates for low-stakes automation. This guide maps which tool owns which job and gives you a concrete handoff workflow.
Cowork can run scheduled tasks in Anthropic's cloud on any paid plan, so a Monday inbox summary no longer needs a second agent. Hermes still earns its place when the job must run on your own hardware or network, use a non-Claude or local model, answer in Telegram or Discord, or run without drawing on your shared Claude usage limit. Anthropic also advises against scheduling Cowork tasks that send messages or make purchases.
Cowork thinks. Hermes runs. Use Cowork (paid, top models, polished UI, team artifacts) for planning, drafting, and high-stakes judgment. Use Hermes (free, self-hosted, always-on) for scheduled, repeatable execution that runs unattended and messages you the results.
Which tool owns which job
| Job | Best fit | Why |
|---|---|---|
| Planning, specs, strategy | Claude Cowork | Premium Claude models, projects and artifacts for high-judgment thinking. |
| Drafting documents & decks | Claude Cowork | Quality and iteration matter; the output is the deliverable. |
| Scheduled / recurring jobs | Hermes | Runs unattended on a server on a cron; no subscription burned on routine work. |
| Inbox triage, daily briefs | Hermes | Always-on, reaches you over Telegram/Discord, cheap on a free model. |
| Monitoring & alerts | Hermes | Background watchers that only ping you when something changes. |
| Multi-step execution of a plan | Hermes | Turns a Cowork-made plan into long-running tasks with its own skills. |
| Team collaboration | Claude Cowork | Shared projects, artifacts, and connectors built for teams. |
The handoff: shared artifacts as the seam
You don't need a special integration. The two tools meet at a shared file, repo, or task list:
- Cowork produces the artifact. A plan, spec, content calendar, or draft — written to a shared folder, a Git repo, or a doc the Hermes agent can read.
- Hermes picks it up. Point a Hermes skill at that location. It reads the artifact and executes the repeatable parts — publishing, filing, notifying, updating a tracker.
- Hermes runs it on a schedule. What was a one-time plan becomes a recurring job: Hermes re-runs the workflow daily/weekly and messages you the results or anything that needs a human.
- You review in Cowork. When the recurring job surfaces something that needs judgment, bring it back to Cowork for the high-quality pass. Loop closed.
Worked example: a content pipeline
- Cowork (paid): you co-write the week's content strategy and three polished draft posts in a Cowork project.
- Handoff: the approved drafts and a simple schedule land in a shared folder.
- Hermes (free, always-on): a skill reads the folder, formats each post, and publishes on the scheduled days — then messages you a confirmation on Telegram.
- Monitoring: Hermes also watches engagement and pings you only if a post underperforms a threshold.
- Back to Cowork: at week's end you review Hermes's summary in Cowork and plan the next batch.
The premium subscription did the creative, high-judgment work; the free agent did the repetitive running. That's the cost win — quantify it with the cost calculator.
Keep the combined setup safe
Two agents means two attack surfaces. Apply the same discipline to both: least privilege on every credential, approval gates on irreversible actions, and a hardened Hermes daemon (iteration limits, allowlists, local-only dashboard). The shared folder/repo is a trust boundary — treat anything Hermes writes back as data to review, not instructions to obey. See the responsible-use checklist before pointing either agent at production accounts.