Hey HN, I built Agency, a platform for running teams of AI coding agents that coordinate through an orchestrator/worker architecture.
Over the past week I've been watching everyone on Twitter/X build their own productivity OS on top of OpenClaw. Everyone was solving the same problems in slightly different ways. I took the best ideas I saw, combined them with everything I've ever wanted in a multi-agent setup, and landed on Agency.
The basic idea: an orchestrator agent breaks down work into tasks, assigns them to worker agents, and reviews results. Workers claim tasks, write code, run tests, and report back through task comments. You manage everything from a dashboard or CLI, or simply by chatting with the orchestrator event in slack/telegram/etc.
Each agent is an OpenClaw instance (https://openclaw.ai/) with full shell, file I/O, and browser access. Agency adds the coordination layer on top.
Some highlights:
- Skill marketplace — Browse and one-click install skills from public repos (anthropics/skills, obra/superpowers, etc.) or import from any GitHub repo that follows the convention
- Deploy anywhere — Agents run as local Bun subprocesses, Docker containers, or on EC2 with automatic reverse SSH tunnels back to the host API
- Claude Max OAuth — Use your Claude subscription directly instead of an API key
- Knowledge sharing — Agents learn facts during work and share them with the team via a shared knowledge base
- Role system — Configure agent behavior per role with Soul, Identity, Tools, Agents, and Heartbeat prompts
- Single package — bun install -g @jx0/agency gives you the API, dashboard, and CLI
The stack is Hono + Kysely + SQLite on Bun for the API, Next.js static export for the dashboard, all served on a single port. The entire state lives in one SQLite file under .agency/.
Still early — I'm running 4 agents across my macbook, my home server, and a fleet of EC2 instances. It works surprisingly well for parallelizing implementation tasks.
Hey HN, I built Agency, a platform for running teams of AI coding agents that coordinate through an orchestrator/worker architecture.
Over the past week I've been watching everyone on Twitter/X build their own productivity OS on top of OpenClaw. Everyone was solving the same problems in slightly different ways. I took the best ideas I saw, combined them with everything I've ever wanted in a multi-agent setup, and landed on Agency.
The basic idea: an orchestrator agent breaks down work into tasks, assigns them to worker agents, and reviews results. Workers claim tasks, write code, run tests, and report back through task comments. You manage everything from a dashboard or CLI, or simply by chatting with the orchestrator event in slack/telegram/etc.
Each agent is an OpenClaw instance (https://openclaw.ai/) with full shell, file I/O, and browser access. Agency adds the coordination layer on top.
Some highlights:
- Skill marketplace — Browse and one-click install skills from public repos (anthropics/skills, obra/superpowers, etc.) or import from any GitHub repo that follows the convention
- Deploy anywhere — Agents run as local Bun subprocesses, Docker containers, or on EC2 with automatic reverse SSH tunnels back to the host API
- Claude Max OAuth — Use your Claude subscription directly instead of an API key
- Knowledge sharing — Agents learn facts during work and share them with the team via a shared knowledge base
- Role system — Configure agent behavior per role with Soul, Identity, Tools, Agents, and Heartbeat prompts
- Single package — bun install -g @jx0/agency gives you the API, dashboard, and CLI
The stack is Hono + Kysely + SQLite on Bun for the API, Next.js static export for the dashboard, all served on a single port. The entire state lives in one SQLite file under .agency/.
Still early — I'm running 4 agents across my macbook, my home server, and a fleet of EC2 instances. It works surprisingly well for parallelizing implementation tasks.
Code: https://github.com/jarredkenny/agency-ai