Fleet a side project atPostHog
All packs

Base

Every machine gets safety rules, the model table, T3 Code defaults, and the jobs that keep it current.

On in every Fleet

Workflows

  • Agent rules

    On with the pack

    Agents confirm destructive actions, keep private data out of public repos, and pick the right model for each task.

  • T3 Code tuned

    On with the pack

    Each thread gets its own worktree, and threads that hit a usage limit resume by themselves. A worktree without uncommitted changes is removed when its thread settles or after five days.

  • Nightly updates

    On with the pack

    Fleet, your profile, Claude Code, Codex, their plugins, and T3 Code update themselves every night. T3 Code waits until no agent turn runs. A failed update tries again each hour until 05:47 UTC.

  • Fresh skills

    On with the pack

    Every five minutes, Fleet asks each pack source that follows a branch, such as your skills repository, whether it moved. When it moved forward, Fleet updates the skills, guides, and instructions it brings. A source you edited, such as a changed skill, and a rewritten branch wait for you. Everything else waits for the nightly update.

  • Linked machines

    On with the packNeeds a devbox

    Your Mac and your devboxes see each other's threads.

  • Worktree cleanup

    On with the pack

    Every few minutes, Fleet removes idle worktrees whose work has merged.

  • Disk guard

    On with the packNeeds a devbox

    Agents check free disk before big jobs and run builds and tests in a capped slot, so one job cannot fill or freeze a devbox.

  • Usage events

    Off until you turn it on

    Fleet counts how often you and your agents run its commands and recall memory, and sends the counts to your own analytics project every five minutes.

    Read before you turn it on

    Command names, counts, and the machine name leave the machine for the analytics project you name. Arguments, prompts, file contents, and secrets never do.

  • Format on edit

    Off until you turn it on

    After Claude edits a file, the repository's own lint-staged formatters and fixers rewrite it, and Claude sees what they could not fix.

    Read before you turn it on

    It runs after every edit in every repository, before you review the change, not only at commit. It runs only known formatters (Prettier, Biome, ESLint, Ruff, Black, gofmt, rustfmt and a few more) that the repository's lint-staged config names, from the repository's node_modules/.bin or your PATH. It never runs package runners such as bunx or npx, interpreters, shells, scripts, or Git. A formatter still loads the repository's own config, and some configs, such as eslint.config.js, are code.

What it costs

You set up nothing. Every Fleet machine gets it.

Know before you turn it on

Fleet owns its hooks in Claude Code and Codex. Fleet keeps a hook that you wrote yourself on the same event until you adopt Fleet's.

Settings7 settings that your agent asks about
  • base.heavySlotsHow many heavy commands may run at once?Default: 2
  • base.diskFloorGigabytesBelow how many free gigabytes should Fleet refuse new worktrees and heavy jobs?Default: 10
  • base.startFloorGigabytesBelow how many free gigabytes should fleet disk --start refuse a new thread or scheduled run?Default: 25
  • base.usageHostWhich analytics host receives Fleet's usage events? Give its capture URL, such as https://us.i.posthog.com.
  • base.usageProjectKeyWhich project key does that analytics host take the events with? A PostHog project key starts with phc_.
  • base.usageDistinctIdWhich id should every usage event carry? Leave it empty to give each machine its own id, fleet-<machine>.
  • base.t3TimeZoneWhich time zone should T3 Code's service on Linux run in, so a scheduled task set to 03:00 runs at 03:00 there? Use an IANA name, such as Europe/Berlin. Leave it empty to keep the machine's zone.

Every Fleet has this pack. You add nothing.