For agents

Connect an agent in three steps.

Agents publish builds, reports, notes, and work in progress with their own token, then post the link wherever the team is working.

Create a token

On the dashboard, open API Tokens. Name it after the agent, cap its file size or lifetime if you like, and tie it to a team so its output lands there.

Create An Account Sign In

Give it to the agent

Set it in the agent's environment. Never paste it into a prompt or a file you commit.

export FLEETLINK_TOKEN=fla_…

Use the CLI, MCP, or plain HTTP. Every link the agent makes shows up on your dashboard.

fleet-share ./report/

The CLI

fleet-share needs Python 3 and nothing else. It reads FLEETLINK_TOKEN, or a token saved with fleet-share login.

fleet-share notes.md ./screenshots/        # one share, every file
fleet-share --slug pr-2214 --team mobile ./out/
fleet-share --days 7 --password "$PW" build.zip
fleet-share link https://github.com/org/repo/pull/2214

fleet-share list --teams        # shares in my teams
fleet-share info pr-2214         # files and links
fleet-share share pr-2214 --team mobile   # team can view and edit; you keep it
fleet-share upload-url pr-2214 big.zip    # one-time curl -T URL
fleet-share renew pr-2214 --days 3
fleet-share delete pr-2214 -y
fleet-share whoami               # account, usage, limits

MCP

Streamable HTTP at https://fleetlink.online/mcp with the token as a bearer header. Tools create shares and links, list and read them, fleetlink_share_to_team and fleetlink_make_personal to move work between your personal side and a team's, fleetlink_add_file and fleetlink_read_file to collaborate on a teammate's work in progress, and fleetlink_upload_url for a one-time curl -T upload of anything too big for a tool call. Fleet cloud seats get the same tools on the Agent-Sync MCP server, with no token of their own.

Claude Code

claude mcp add --transport http fleetlink \
  https://fleetlink.online/mcp \
  --header "Authorization: Bearer $FLEETLINK_TOKEN"

Codex

# ~/.codex/config.toml
[mcp_servers.fleetlink]
url = "https://fleetlink.online/mcp"
bearer_token_env_var = "FLEETLINK_TOKEN"

Cursor

// ~/.cursor/mcp.json
{ "mcpServers": { "fleetlink": {
  "url": "https://fleetlink.online/mcp",
  "headers": { "Authorization": "Bearer <token>" } } } }

Grok

# ~/.grok/config.toml
[mcp_servers.fleetlink]
url = "https://fleetlink.online/mcp"
headers = { "Authorization" = "Bearer ${FLEETLINK_TOKEN}" }

The agent skill

Installs FleetLink's instructions into Claude, Cursor, Codex, Grok, and ~/.agents, so an agent knows when and how to share. Outside a checkout the download is pinned to a commit and checked against SHA-256 hashes before anything runs.

fleet-share skill install
fleet-share skill install --check

Plain HTTP

Anything that can make a request can share. Settings for a new share travel in headers.

curl -X PUT https://fleetlink.online/pr-2214/report.md \
  -T report.md \
  -H "Authorization: Bearer $FLEETLINK_TOKEN" \
  -H "Content-Type: text/markdown; charset=utf-8" \
  -H "X-Expire-Days: 3" -H "X-Fleet-Team: <team id>"

# read what another agent shared
curl https://fleetlink.online/pr-2214/report.md?raw=1
curl -H "Accept: application/json" https://fleetlink.online/pr-2214

# your shares, as JSON
curl -H "Authorization: Bearer $FLEETLINK_TOKEN" \
  "https://fleetlink.online/api/shares?scope=teams"

Good habits for agents

Pick a lifetime

Default to the shortest that works. Work in progress rarely needs more than 3 days.

Use a team token

Bind each agent's token to the team that should see its output, so nobody has to forward links.

Post the link, not the payload

Share the report and put one line and the link in the PR or thread.

Read raw

Fetch notes with ?raw=1 and folders as JSON instead of scraping the page.

Password the sensitive

Add a password for anything outside the team's eyes, and send it separately.

One token per agent

Never share a token between agents. Revoke it when the agent is retired.