Fleet

Set up your
coding agents
once.

Fleet gives every machine the same rules, skills, and workflows. One prompt sets it up.

Get startedBrowse the packs

The problem

Good agents need a good setup.

  • Every machine needs its own setup

    You add rules, skills, hooks, and sign-ins by hand.

  • Your machines stop matching

    Your laptop knows a rule that your devbox does not.

  • Agents stop when your Mac sleeps

    Work overnight needs a machine that stays on.

What Fleet does

One prompt sets up all of it.

  • It installs T3 Code, Claude Code, and Codex, with rules and skills.
  • You pick the workflows as packs.
  • It saves your answers in your private profile repo, so every machine matches.

Get started

Where should your agents run?

Choose a setup, and switch packs on or off. The prompt below changes as you choose.

Agents run on your Mac. They stop when it sleeps.

  • Pull requestsEvery fix ends as a reviewed draft pull request.
  • OrchestrationA conductor thread splits big work into tickets.
  • CommunicationAgents write in your voice and share plans as links.
  • HubAdd a hub later, when you want one.

Two cloud devboxes stay on while your Mac sleeps.

  • Pull requestsEvery fix ends as a reviewed draft pull request.
  • OrchestrationA conductor thread splits big work into tickets.
  • CommunicationAgents write in your voice and share plans as links.
  • HubOne always-on devbox links and watches the others.Always on

Your Getting started prompt

  1. Download T3 Code
  2. Sign in with T3 Connect
  3. Paste this prompt
Set up Fleet on this Mac with me. Read https://raw.githubusercontent.com/Silthus/fleet-engine/main/SETUP.md and follow it step by step.

My picks from the Fleet page:
- Where Fleet runs: Mac only
- Packs on the first setup: pull-requests, orchestration, communication
Open in T3 Code