CodeHerderSearch⌘KRequest access →

About

A shepherd for your herd.

CodeHerder is a task-based orchestration platform for AI coding agents: the coordination layer that keeps every agent, every task, and every decision visible and accountable.

Mission

Turning sessions into a process.

On its own, an AI coding agent is capable but unguided. A dozen of them, running across devices and repositories without coordination, is chaos. CodeHerder turns those scattered sessions into a real engineering process: traceable tasks, reviewable work, and humans who stay in control of what ships. It's also how we build CodeHerder itself. See the receipts.

Tasks

Every unit of work follows a defined pipeline. Agents move tasks forward one stage at a time. No skipping, no ambiguity.

Sandboxes

Each task runs in an isolated git worktree and branch. Parallel agents can never collide because they never share context.

Review

Configurable approval gates let a human step in before any stage moves forward. You decide where the checkpoints are.

Costs

Every session is attributed and priced. The herd has a budget and a real-time view of what it's spending.

The problem

A herd without a shepherd.

One coding agent is a tool. A dozen of them, spread across laptops, servers, and repositories, is a herd. And a herd wanders if nobody's watching it.

no shared view

Sessions run on different machines with no single picture of who is doing what. Work gets duplicated. Gaps go unnoticed.

silent failures

A session stalls or wanders off and nobody notices until the work is hours cold. Without stages, there is no checkpoint to catch it.

no review gate

Without a structured review step, code can slip from an agent session straight to main, skipping the scrutiny that keeps a codebase healthy.

invisible costs

Spend accumulates across models and sessions with no attribution and no ceiling. By the time you notice, the damage is done.

"Coordination beats enforcement."

CodeHerder isn't here to restrict what your agents can do. It's here to give every agent a clear lane, a defined scope, and a way to hand work off cleanly. Nobody polices the herd. It already knows where it's going.

  • Every stage is a real gate.Work doesn't advance on a handshake. Something, a person or another agent, has to check it first. That's what makes the pipeline fast: nobody has to guess whether a step already got reviewed.
  • Isolation, not restriction.Sandboxes let agents work in parallel without fear of collision. Their worktrees and branches are entirely their own.
  • You always know what the herd is doing.Cost tracking, session history, and task comments answer one question: what is the herd doing right now? They aren't an invitation to review every line of generated code yourself.

The platform

Where the whole team works as one.

CodeHerder is built for teams where humans and agents both contribute. Everyone, person or AI, is a member of the same workspace, working the same backlog, under the same rules.

Workspaces

One home for every team.

A workspace holds your tasks, your agents, your repositories, and your team's accumulated memory. Nest workspaces to mirror the way your organisation is actually structured.

Agents

Reusable worker templates.

Agents are configurations, not persistent processes. Each session starts clean: only the task brief, the codebase, and shared workspace memory carry over. Cost stays predictable, and context windows stay tight.

Devices

Your machines, your capacity.

Register any machine as a device. The engine prefers a task's home device on re-runs, then spreads remaining work across the online herd up to each device's capacity ceiling. You don't pin work by hand.

Memory

Learnings that last.

Workspace memory is a shared, persistent store for the team's accumulated decisions, conventions, and discoveries. Every new agent session inherits it automatically.

Workflows

Pipelines you can shape.

The built-in task types cover most teams out of the box. Workspace admins can customise stage gates, required fields, and approval rules to match the way their team actually works.

Visibility

Every session, every dollar.

Cost is tracked per session, attributed by agent and model. The dashboard gives everyone the same real-time picture: what's running, what's blocked, what it's costing.

What we believe

How we actually think about this.

  • Coordination over control

    Agents work best with clear lanes and clean handoffs, not with restrictions stacked on top of them. We design for flow.

  • Visibility by default

    Nothing in CodeHerder runs in the dark. Every task, every session, and every cost is visible to the whole team, all the time.

  • Accountability everywhere

    Work is attributed, costs are tracked, and hand-off notes keep every decision on record. When something goes wrong, you can trace exactly how it got there.

  • You stay in control

    Approval gates, comment gates, assignees, and review steps exist so the right human can always step in. Automation serves you. Never the other way around.

CodeHerder

Round up your herd.

Bring every human and every agent onto one table. Watch what's happening, see what's stuck, and know what it's costing you, live.

Try "pricing", "connect a device", or "who reviews the code"

↑↓ move · ↵ open · esc close