Holon

Agents that act and follow through. Run Holon on your computer or a team server. Connect events and schedules so agents can act, save progress, and ask for your input when needed.

THE HOLON BLOG

Work that keeps going.

The ideas behind Holon, the design that supports them, and the people putting agents to work.

START HERE · PRODUCT

What is Holon? Let agents keep working in your environment.

Give recurring work to agents with ongoing roles. A tour of the local workbench, from continuous review to remote development and team use.

Meet Holon

Design & practice

How it works. How to use it.

DESIGN

WorkItems: separating work state from conversations

An API migration and two PRs show why goals, progress, and waiting conditions need a home of their own.

Explore the design
HANDS-ON GUIDE

Build a reviewer that follows PRs through

Set up the code-reviewer template, agree on permissions, and subscribe to PRs. Follow revisions and CI through to the merge decision.

Set up continuous review
TEAM STORY

From personal AI tools to shared team agents

A small team's 77 days of recorded usage, device investigations, and hands-on testing show where shared agents fit—and where people still step in.

Read the team story

Try it with one responsibility.

Install Holon, connect a provider, and give your first agent a bounded job.

Get started
What is Holon? Multiple agents working in your environmentAssign recurring work to established roles, let agents follow up in the background, and reconnect when needed. An ongoing review example introduces Holon's local workbench for remote development and team collaboration.Holon's WorkItem architecture: separating work state from conversationFollow an interface migration from launch to retirement to see how WorkItem differs from Goal and Loop: it keeps objectives, progress, external dependencies, and delivery together across release cycles.Beyond a one-time review: build a reviewer that follows PRs with HolonCreate a reviewer with built-in working rules and Skills, set its responsibilities and merge permissions, and have it discover PRs and follow fixes and CI updates.From personal AI tools to team collaboration: an agent-native case studyHow a small team moved from individual AI tools to shared agents, with 77 days of retained usage records, device investigations, and a hands-on test of silent piano keys.