My Multi-Agent Weekly Journal Ritual
One of the most fun experiments I’ve been running lately is my Sunday journal entry. What started as a simple request for weekly summaries has turned into a beautiful little multi-agent ritual that feels like a real team huddle — even though I’m the only one on the team.
The Goal
The main purpose is to capture everything I actually worked on throughout the week in one honest, useful place. Not just the big projects, but the small wins, the troubleshooting sessions, the things I researched, the tools I installed or removed, and even what was happening on my home machine itself.
By pulling in system changes (packages upgraded, new tools added, things cleaned up, kernel events, etc.) I get a real “heartbeat” of the week — both the human work and the machine work. It becomes a living record that’s searchable in Obsidian and helps me see patterns over time.
The Flow
Every Sunday I run through this process:
Hermes starts — It pulls from its memory, recent conversation sessions, and the last 7 days of actual system activity on the machine (using pacman logs and journalctl). This gives the raw material of what got done and what changed on the system.
Claude joins — Hermes delegates to Claude Code with a clear prompt so it can add its own perspective (for example, the Omarchy Ted Lasso theme work and how we’re both connected to the same vault).
I blend — The different contributions get woven together into one cohesive, warm entry that still feels like my voice.
System heartbeat included — A dedicated “System Changes” section shows exactly what happened on the machine that week — installs, removals, upgrades, and any notable events.
Lands in Obsidian — The finished note goes straight into the
Journal/folder with proper tags and frontmatter so it shows up nicely in Dataview queries and the graph view.
Everything lives in one shared vault at /home/tim/Documents/Notes. Both agents can read and write the same files, so the collaboration feels natural and low-friction.
Why This Works So Well
- I don’t have to do any extra work — I just ask for the journal entry and the team handles the rest.
- Each agent brings different strengths: Hermes is great with session history and system logs, while Claude adds creative and code-related color.
- The final entry stays in Obsidian, so it’s fully searchable, linkable, and becomes part of the bigger knowledge base.
- The tone stays warm and friendly because both agents are prompted to match that voice.
Future Extensions
I’m already talking about bringing more players into the game. If Grok (or other agents) are installed, I can delegate to them the same way. The pattern is simple: one agent orchestrates, the others contribute through the shared vault or direct delegation.
This feels like the start of something really powerful — a small, personal agent team that helps me capture life, projects, and the actual state of my machine without any extra effort on my part.
This post was drafted as part of testing the exact workflow it describes.