Agents Fleet

Agents Fleet

One private Git repo holds your Claude Code and Codex setup. Fleet tests it and applies it to each of your Mac and Linux devices.

You still work in Claude Code or Codex. Fleet manages their setup files. It does not contain a model list; models and reasoning options come from the clients.

What you get

After setup, you have:

- A private Fleet repo that you own. It holds your rules, settings, skills, commands, hooks, plugins, and MCP servers (tools your agents can call).
- Tested releases. You push main. GitHub Actions tests it on macOS and Linux and moves the passing commit to live. Devices with automatic updates enabled follow live.
- Backups and rollback. Each apply backs up the files it replaces. fleet rollback restores them.
- Account routing. A local router sends Claude Code and Codex requests through the accounts you choose. Fallback to another account is optional.
- Safe MCP secrets. Secret values stay in macOS Keychain or Linux systemd-creds, never in Git.
- Claude-Mem memory. Local memory on each device, or one shared database on your own Linux server.

Set up with an agent

Copy this prompt into Claude Code or Codex. You do not need to clone anything first.

The agent stops for a login, a secret, a paid service, or an action that can lose data. It does all other work itself. The full agent checklist is SETUP_WITH_AN_AGENT.md.

To make the repo yourself, click Use this template. Keep it private and leave Include all branches off. Then give the agent the prompt above with your repo URL. Do not fork for personal configuration. A fork of this public repo stays public.

What is the same, and what is yours

This template ships with empty rules, hooks, skills, MCP declarations, and device profiles. Nothing personal from the maintainer is in it. The…