Accounts & claiming

Anonymous deploys expire after 14 days. Deploys made through an authenticated account are owned and have no expiry.

Connect the CLI

flypod login

The command prints a short confirmation code and opens flypod in your browser. Sign in, verify that the displayed code matches, and approve the device. The CLI stores the resulting session in your user config directory, outside the repo.

Every later deploy from that CLI is attributed to the account:

flypod ./dist

Log out by deleting only the local CLI session:

flypod logout

Keep sites you already deployed

Login automatically attaches anonymous sites this CLI remembers on the same host. Each local folder link already contains the site's manage_token, so the CLI can prove control without asking you to copy a secret:

$ flypod login
Logged in.
Found 3 anonymous sites on this machine.
  Attaching to your account…
  Attached 3 sites.

Deleted, expired, and already-owned sites are skipped. Sites deployed from a different machine are not in this CLI's registry.

Claim a site from another machine

If you saved the original anonymous deploy's claim_token, attach it explicitly:

flypod login
flypod claim <site_id> <claim_token>

Agents and CI

Agents running on a connected machine automatically use its saved session. A stateless job can receive an existing session token through its secret store:

FLYPOD_TOKEN="$FLYPOD_SESSION" flypod ./dist --json

Treat the value as an account credential. The legacy FLYPOD_API_KEY variable is still read for compatibility, but new integrations should use FLYPOD_TOKEN.

Where local state lives

session.json and the folder-to-site registry projects.json live in the platform-specific flypod config directory with mode 0600. Override the directory with FLYPOD_CONFIG_DIR. Neither file belongs in your repo.