Roll Your Own Coding Agent
Build a minimal coding agent from scratch — the tool-calling loop, context, and the Guide/Generate/Verify/Solve cycle in real code — so you understand exactly what's under Claude Code and Cursor.
Read guideField Guides Tagged as "Agents"
Agentic systems, coding agents, and multi-agent orchestration.
Context Engineering: The Craft of AGENTS.md
A build-along on writing, structuring, and evolving the context files — AGENTS.md, CLAUDE.md, constitution.md — that steer coding agents. From a blank file to a living system that compounds every cycle.
Read guideRunning the Fleet: A Field Guide to Multi-Agent Orchestration
You built one agent that knows you cold — its own personality, a memory that survives, skills it runs your way. It's a great employee. It's also still one employee, doing one thing at a time, waiting on you to hand it the next task. This guide is about the next move: turning that single agent into a coordinated fleet that plans, executes, and monitors real goals while you supervise instead of operate. It's the deep-dive sequel to [Building Your Agentic OS](/guides/building-your-agentic-os) — where that guide ended by pointing at the horizon, this one walks the whole distance. We build it on Hermes, because Hermes already ships the hard parts: profiles (every agent a full citizen with its own identity and memory), a durable kanban board that coordinates them, a decomposer that routes a dropped-in goal to the right specialists, and a way to package a whole agent as a git repo and hand it to your team. Concrete throughout, honest about the sharp edges, and built so the foundation you already laid is exactly what scales up.
Read guideBuilding Your Agentic OS: A Field Guide
Two people can use the exact same AI agent and get wildly different results. It's almost never the prompting. One of them built a system underneath the tool — a layer that gives the agent a persistent identity, a real memory, and a set of skills it runs the same way every time — and the other is still re-explaining themselves at the start of every session. This is a field guide to building that system, in three moves. First, the OS itself: a plain-files architecture you can stand up this afternoon on whatever agent you already use, built around three pillars — personality, memory, and skills. Second, the pivot — graduating that static setup onto Hermes, Nous Research's open-source, self-hosted agent, so the files stop being a brief you read aloud and become a teammate that runs on its own. And third, where it's all heading: coordinating many agents to plan, execute, and monitor real goals, with the orchestration, shared memory, and governance that make a true agentic OS. Everything here is portable by design, and you build it one working piece at a time — starting with a single agent that actually knows you.
Read guide