boundsj/t3-fleet-gateway

Ask your bot to get something done. Let T3 Code do the coding on your machines.
T3 Fleet Gateway connects Grok Bot, Notion and other MCP clients to your T3 servers through one connection. Your agent can find projects, start work, answer worker questions and bring back the result. Each new job gets a T3 thread you can open in T3 whenever you want: a named project's job gets its own git worktree and branch, and work with no named project can run in a machine's T3 scratch workspace.
One connection for the fleet. Add machines behind the gateway without adding an MCP connection to every bot.
Work you can follow. Jobs have stable IDs, readable replies and a feed of changes that survives restarts.
Access you choose. Give an agent Read or Operate access to all machines or selected ones. Project rules decide what its workers may do.
Updates when work changes. Webhooks wake your bot when a turn finishes or a job needs attention.
## Get going with prompts
You need an always-on machine with Node.js 24.22.1+ on 24.x or 26.12.1+ (older releases do not block the compromised eMudhra intermediates), a running T3 Code server and its t3 CLI. A coding agent on that machine can do the setup. The gateway runs from a Git checkout; it is not published to npm.
### 1. Ask your coding agent to set up the gateway
text
Set up https://github.com/boundsj/t3-fleet-gateway on this machine.
Follow docs/setup.md and docs/operations.md. Use a dedicated service
checkout, enroll this machine's T3 server, and add these project
aliases: .
Use for the public MCP connection. Enable the
dashboard on a private tailnet URL, separate from the public MCP
listener. Keep discovery off and project approval settings at their
defaults. Run doctor, then give me the MCP URL and dashboard URL.
> What this does: gives your cloud agent a secure way to reach T3 while keeping the operator dashboard private. The gateway handles T3 credential renewal after enrollment.
Prefer doing it yourself? The same steps are in the manual setup guide.
### 2. Connect your bot
Add the returned /mcp URL as a remote MCP connection in Grok Bot or your chosen client. For OAuth clients, ask the setup agent to mint a one-time approval code. Enter it on the gateway's approval page, choose Read or Operate, and select the machines.
> Pick the right access: Read follows work; Operate also starts and steers it. All machines includes hosts you add later. Selected machines stays limited to those you approve.
If your client only accepts a bearer token, as Notion's custom MCP connections do, ask the setup agent:
text
Create a gateway bearer token for , with
access to and a 90-day expiry. Help me enter it privately in
the client's connection settings. Do not put the token in chat.
Once connected, tell your bot:
text
Call fleetstatus and tell me which machines and projects you can use.
When I give you work, use the gateway to start or continue the right
job. Follow its status, read the worker's replies, and tell me when it
is ready for review or needs my help. Keep the job ID and T3 link.
### 3. Give it a small job
text
In project , check the README for broken local links and propose
the smallest fix. Run the relevant checks and bring me the result for