Hermes Personal Paper

What Hermes Personal Paper does

The generator assembles tomorrow's edition as a folder of markdown articles, which the separate Vael Paper engine reads and prints as a broadsheet-style static site. Desks write the sections, and some are code while others are model prompts. Data desks render tables and charts in Python, so the model never invents a figure, and each desk runs a write, check and fix loop and does not publish on red. The masthead lives in editions/paper.json, material goes in an inbox/ folder, and sections, sources and desks are files you own.

You talk to Hermes once, and a scheduled cron run writes, checks, fixes and publishes an edition every night at 4 a.m. Every desk is a short prompt over a little material, so a modest local model is enough. The README admits that a nightly run on a modest local model reads plainer than the sample edition, whose stories were written with Claude. Provenance for each sample article is recorded in samples/edition/PROVENANCE.md.

Key features

• Nightly edition built from calendar, budget, feeds, notes and live data feeds
• Data desks that render figures, tables and charts in Python
• Write, check and fix loop that blocks publishing on failures
• Scheduled cron run at 4 a.m. with one Hermes conversation to set up
• Masthead, sections, sources and desks stored as files you control

When to use it

• Waking up to a finite daily briefing instead of an endless feed
• Summarizing your Friday calendar and budget into a lead story
• Writing a custom desk for a topic you follow, following the README examples

Who it is for: Hermes Agent users who want an unattended daily personal briefing run on a local or small model.

How it fits with Hermes Agent

Built for Hermes Agent: a scheduled Hermes cron job generates the edition, and the README also has a section on running it on another agent.

FAQ