Architecture by Leverage: The Five-Sentence Design Philosophy That Changed How I Build Agents

Mon, 18 May 2026 14:58:50 -0400

I saw something in the Hermes Agent Discord that stopped me mid-scroll.

Not a feature announcement. Not a breaking change notice. Not a philosophical debate about agent architectures. Just someone — user sovthpaw — describing how they actually use their agent in five sentences:

If you upload your Obsidian knowledge base to your Google Workspace, you can version control, share, and backup your knowledge base.

My agent GitHub integration is largely centered around an /llm-wiki (or /obsidian works) in my agent’s own dedicated repo.

The Hermes Kanban: A Complete Guide to Multi-Agent Task Orchestration

Mon, 18 May 2026 00:00:00 +0000

The Hermes Kanban: A Complete Guide to Multi-Agent Task Orchestration

Ahead of the release: This guide covers the kanban system as it will be once PRs #27572 (orchestrator-driven auto-decomposition) and #27813 (artifact delivery) are merged. Both have been reviewed and approved by the Hermes maintainers. If you’re reading this before they land, your kanban board has the specify tool but not the decompose tool, and kanban_complete doesn’t yet accept the artifacts parameter — everything else applies today.

If you’ve used Hermes Agent for more than a weekend, you’ve probably discovered delegate_task. It’s the obvious tool when you need a subagent to handle a subtask: fork work to a child, wait for it to return, collect the result. It looks like a function call. It works like a function call. And for one-shot reasoning subtasks, it’s the right tool.

Engineering on Notes from the Rabbit Hole

Architecture by Leverage: The Five-Sentence Design Philosophy That Changed How I Build Agents

The Hermes Kanban: A Complete Guide to Multi-Agent Task Orchestration

The Hermes Kanban: A Complete Guide to Multi-Agent Task Orchestration