Integrations
Claude Code and Codex get the official GitHub, Context7, and Convex plugins, and Claude can hand work to Codex.

Workflows
GitHub
On with the packAgents read and change issues and pull requests through GitHub's official plugin.
Context7
On with the packAgents look up current library documentation through Context7.
Convex
Off until you turn it onAgents get Convex guidance and inspect the deployment of the project they work in.
Codex from Claude
On with the packClaude Code hands a task, a diagnosis, or a review to Codex through OpenAI's Codex plugin.
What it costs
Each plugin signs in once on each machine, and fleet doctor says how: a GitHub token for Claude, Context7 through its own sign-in or an API key, and Convex through its CLI. Codex's GitHub and Convex plugins use your ChatGPT sign-in. Convex starts off.
Know before you turn it on
The plugins act with the accounts you sign in with. Fleet removes only plugins that it installed, and keeps a plugin you turn off in your settings off.
Add Integrations to your Fleet
Paste this prompt into a T3 Code thread on a machine that runs Fleet.
Your install prompt
Add this Fleet pack to my setup with me: Integrations. Fleet already runs on this machine. Ask me each choice with your question tool, and run every command yourself. 1. Run `fleet update`, so this machine has the newest engine and packs. Then run `fleet packs`, and leave out each pack that is already on. 2. Turn the packs on with one command: fleet packs --add integrations 3. Run `fleet doctor`, and explain each line. Do each `To do:` line with me, and say what a sign-in is for before it opens. 4. My other machines take the change at their next `fleet update`. To give it to one now, run `fleet update` there.