Skip to main content

Hermes Agent

Hermes Agent is an autonomous agent from Nous Research that can run on your server, terminal, or messaging platforms such as Telegram, Discord, Slack, and email. Because it can write files, run commands, remember context, and keep working across sessions, it pairs naturally with OpenDocs for publishing the Markdown it creates.

Setup​

Install the OpenDocs CLI wherever Hermes runs commands:

npm install -g @opendocs.cc/cli
opendocs login --key od_live_xxxxx

For long-running Hermes environments, you can also set OPENDOCS_API_KEY in the environment instead of relying on an interactive login.

To make the workflow repeatable, add the OpenDocs SKILL.md to the context or skills Hermes uses for your project. Hermes can then publish, update, list, pull, and unpublish docs without you repeating the command details.

Example prompts​

Publish a weekly brief:

Write a weekly engineering brief as Markdown, publish it to OpenDocs,
and return the final URL.

Publish from a messaging platform:

Summarize today's deployment work as Markdown. Publish it to OpenDocs
with workspace visibility and send the link back here.

Update an existing doc:

Pull post abc123 from OpenDocs, add the new rollout notes, and publish
the update. Return the updated URL.

Scheduled reporting:

Every Friday, write a Markdown status report from this week's notes,
publish it to OpenDocs, and send the URL to the team channel.

Common workflows​

Long-running documentation​

Hermes is designed to keep context over time, which makes it useful for docs that evolve across weeks or months. Ask it to retain the postId when it publishes:

opendocs publish engineering-brief.md --json

Then later:

opendocs update engineering-brief.md --post-id abc123 --json

Cross-platform handoff​

Hermes can receive the request in one place and return the URL somewhere else:

Draft the incident summary, publish it to OpenDocs, and send the link
to Slack once it is ready.

Agent memory plus stable URLs​

OpenDocs gives Hermes a durable publishing target. Hermes can remember which post it created, while OpenDocs keeps the URL stable as the document changes.

Tips​

  • Use --json — Hermes can parse the published URL, slug, and post ID reliably.
  • Prefer workspace visibility — internal reports and briefs stay limited to your team by default.
  • Store the post ID — useful when Hermes updates a recurring report or living document.
  • Use environment auth for servers — OPENDOCS_API_KEY is the easiest path for unattended Hermes deployments.