The coordination layer for teams that build with agents

Huskies in harness, pulling you forward.
Not a pack of lone wolves.

Everyone on your team is talking to a model. Nobody is talking to each other. Five people, five private sessions, five versions of what is in flight, and then a month-long pull request fight nobody really wins.

Huskies puts the whole team, humans and agents, on one board with one set of rules: a card before any code, gates before any merge, and a room where everyone can see what is happening.

curl -fsSL https://huskies.dev/install.sh | sh

Free and open source, on your own machines with your Claude login. Or sign up and we run it for you.

#217 login timeout
Card asked in #dev from a phone
Code coder-2 · 3 files · 2 tests
Gates lint · build · 41 tests green
Merge rebased, squashed, no conflicts
Shipped v1.4.2 tagged · #dev told

How it works

  1. 01

    Say what should exist

    A card with acceptance criteria, written where the team can read it. From the board, your editor, or Slack on your phone.

  2. 02

    A coder picks it up

    Its own worktree, its own branch, tests written against your criteria. Several coders at once, none of them in each other's way.

  3. 03

    Gates decide

    Lint, build, tests, your own checks. Nothing moves until everything passes, and nobody has to ask whether it did.

  4. 04

    It lands and ships

    A merge agent resolves conflicts, the change merges, the release tags, the signed binary builds, and the room is told.

What you get

Intent before code

Every change starts as a card someone else can read. No more code without a stated need, from a person or an agent.

A pack, not a wolf

Coders work in parallel in isolated worktrees, on every machine on your network: the laptop, the box in the garage, the old desktop. One merge agent serialises what lands, so nothing collides on main.

Ships, not just merges

Release trains, tags, signed binaries, container images, upgrades across your machines. The pipeline ends at running software.

Cheap where it counts

The expensive model defines the work and pins the cause. The cheap model types. Cards carry file and line, so the cheap model never rereads your codebase.

Nobody has to ask

The feed, the board and the bot in your Slack answer "what is everyone doing" without a standup. Blocked, merged, tagged: you hear it when it happens.

You're the musher

You set direction and judge what matters. The dogs do the running, and every change is traceable from the request to the release.

Three ways to run it

The free tier is the whole product. What you pay for is time: first the time you spend running servers, then the time you spend waiting for builds.

Free & open source

Your machines

Your hardware, your Claude login, the full product, no account needed. Cards, gates, parallel worktrees, releases, signed artefacts, the board, the bot. Join the other machines on your network with one token and the work spreads across them. When you want chat across the internet, huskies.dev relays your Slack for nothing.

Install and docs →
Paid per org

Hosted leader

Same board, same rules, nobody on your team runs a server or thinks about NAT. Move your leader to us with one command, and move it back the same way.

Sign up →
By the minute

Build machines

When you want it faster, buy throughput. Builds, tests and coders run on machines we start when the queue grows and stop when it empties.

Sign up →

Put the team in harness.

One line to install on your own machine, or sign up and we run it. Huskies is built by Crash Labs. Questions: hello@huskies.dev.