Fleet

Every machine you own
becomes a coworker.

Pair a Mac, a Linux box or a cloud server with one command. Queue an issue and AgentTask places it where it starts soonest, with your agents and your logins, on your hardware.

$curl -fsSL https://app.agenttask.io/install | sh -s -- K7Q-4MX
Your pairing code comes from the app. macOS · Linux · WSL.
Pair

One command. Then it's on the team.

The installer drops one signed binary on the machine, pairs it with your organisation and hands it to launchd or systemd. No agent to configure, no dashboard to babysit.

  • Runs on macOS, Linux and WSL. One binary, written in Go.
  • It finds the agent CLIs already on the machine: Claude Code, Codex and Grok.
  • It reads their liveness, trust, quota and usage.
macOSLinuxWSLlaunchdsystemd
mac-minizshpairing
Team and private

Share the big box. Keep your laptop yours.

Every machine is either a team machine or a private one. Team machines serve everyone in the organisation. Private machines take your work only, and their activity syncs only to you and the members you add.

  • Slots per machine. A slot is one agent at work, so a big server carries more than a laptop.
  • Placement never fills more slots than a machine has.
  • See every machine, its slots and what is running in them, live.
Fleet· Nextlab5/11 slots busy
MachineAccessSlots
Example data
Placement

The shortest wait wins. Every time.

Queue an issue and the queue ranks it, then places it on the machine where it starts soonest. You never pick a box by hand.

  • Order comes from skip-queue, rank, train position, priority and time in the queue.
  • Private machines only ever take their owner's work.
  • The server is the clock. A machine never decides on its own to start something.
Queue· placing1st in line
AGT-150Usage page shows quota per subscriptionplacing
skip-queueranktrain positionpriorityqueued time
Example data
On your machines

Your keys stay home. Always.

AgentTask stores no agent credentials. Ever. Claude Code, Codex and Grok run with the logins already on the machine, inside tmux, where you can watch them or take over.

  • Each run lives in its own tmux session on the machine. Stream it to any screen. Terminals →
  • The daemon updates itself: sha256 and an ed25519 signature checked, then an atomic swap and a restart by launchd or systemd.
  • Check any binary yourself with agenttask verify-signature.
hetzner-01agenttask daemonsystemd

Runs in tmux

A real terminal session per run, on your hardware. Close the browser, the agent keeps going.

Logins never leave

Your agent subscriptions are used where they are signed in. AgentTask stores none of those credentials.

Signed updates

Every new binary is checked against its sha256 and an ed25519 signature before it replaces the old one.

What the daemon and relay are built with: the stack →

← PreviousPlanning Next →Release trains

Pair a machine in under a minute.

Bring the agents you already pay for. Free while we're in beta.

Start buildingSee the integrations