# flypod

> Zero-auth deploy primitive. Point it at a directory of static files and get a
> live URL back in seconds: no account, no config, no build pipeline. Anonymous
> deploys are ephemeral (14-day TTL); sign in to make them
> permanent. Every deploy is an immutable, content-hashed version, so update and
> rollback are one command each.

## Instructions for AI agents

- Deploy with `npx flypod <dir>`. The live URL is printed to stdout; everything
  else goes to stderr. For structured output use `npx flypod <dir> --json` and
  parse stdout, or `--quiet` for just the URL.
- To ship a change to the SAME site, run `flypod update`. Do not deploy again.
  flypod links the working directory to its site automatically.
- Authenticate interactively with `flypod login`, which opens a browser and
  saves an account session. For headless automation, set `FLYPOD_TOKEN` to a
  session token or pass it to `flypod login --token`. Without either, the
  deploy is anonymous.
- flypod deploys STATIC sites only (HTML/CSS/JS, or a folder of Markdown). There
  is no server-side code, no functions, and no database.
- Treat anonymous deploys as temporary (they expire after 14 days) unless the
  site is owned by an authenticated account.
- Append `.md` to any docs page URL to fetch its raw Markdown. The full corpus
  is at /llms-full.txt.

# Docs

- [What is flypod](/docs): flypod is a zero-auth deploy primitive. POST a directory of static files, get a live URL back in seconds. No account, no config, no build pipeline.
- [Quickstart](/docs/quickstart): Deploy a folder of static files and get a live URL in under a minute, then ship a change and roll it back.
- Guides: Task-oriented walkthroughs
  - [Deploy a site](/docs/guides/deploy-a-site): Deploy a folder or a single file to a live URL, with auto-detection of common build directories and machine-readable output for scripts.
  - [Update & rollback](/docs/guides/update-and-rollback): Ship a new version to a site, list its history, and roll back. The day-to-day loop, with no IDs to remember.
  - [Render Markdown to a docs site](/docs/guides/render-markdown): Deploy a folder of Markdown files with no index.html and flypod renders them into a styled docs site with a sidebar and home page.
  - [Accounts & claiming](/docs/guides/accounts-and-claiming): Connect the CLI through browser device authorization, make deploys permanent, and attach an existing anonymous site.
  - [Use with agents & CI](/docs/guides/use-with-agents-and-ci): The canonical playbook for driving flypod from an agent or CI job. Covers non-interactive output, capturing the URL, exit codes, authentication, and idempotent re-deploys.
  - [Enable comments on a site](/docs/guides/enable-comments): Turn on the anchored comments widget for a deployed site, choose an access mode, and read the review feed.
- CLI reference: Every flypod command
  - [CLI reference](/docs/cli): The flypod CLI deploys a static directory or file to a public URL with one command, then manages versions, rollbacks, and account ownership.
  - [flypod \[path\]](/docs/cli/deploy): Deploy a directory or single file to a public flypod URL; owned and permanent when logged in, otherwise anonymous with a 14-day TTL.
  - [flypod update](/docs/cli/update): Ship a new version of a directory or file to the linked flypod site; the new version becomes live immediately.
  - [flypod versions](/docs/cli/versions): List a flypod site's versions, newest first, marking which one is currently live.
  - [flypod rollback](/docs/cli/rollback): Make a previous version of a flypod site live again, by version id, unambiguous prefix, or no argument for the previous version.
  - [Account commands](/docs/cli/accounts): Connect the flypod CLI to an account, list owned sites, attach anonymous deploys, and remove the local session.
  - [flypod install skill](/docs/cli/install-skill): Write flypod usage instructions into your repo's agent config files so coding agents (Claude Code, Codex, Cursor, and more) know how to deploy with flypod.
  - [flypod forget](/docs/cli/forget): Remove the local folder-to-site memory; the deployed site is unaffected.
- API & library: Programmatic deploys
  - [API & library](/docs/api): flypod exposes a JavaScript library and a raw HTTP API, both backed by the same bearer-token auth model.
  - [Library](/docs/api/library): The flypod npm package deploys a folder of static files to a live URL from Node or Bun. Reference for deploySite, collectDist, resolveDeployDir, and the DeployOptions / DeployResult types.
  - [TypeScript demo](/docs/api/demo): A runnable TypeScript example that deploys a folder to a live URL with the flypod library. Download it and run, or check it inline. Zero auth.
  - [HTTP API](/docs/api/http): The flypod REST API at https://flypod.dev deploys sites from a zip, redeploys new versions, rolls back, and manages accounts with bearer-token auth.
- Concepts: How flypod works
  - [How it works](/docs/concepts/how-it-works): flypod has two planes. A deploy pipeline ingests a zip into an immutable version, and a serve plane routes a subdomain to that version's files.
  - [Versioning](/docs/concepts/versioning): Every deploy is an immutable version identified by a hash of its content; a single live pointer selects which version a site serves, moved by update and rollback.
  - [Ephemerality & TTL](/docs/concepts/ephemerality): Anonymous deploys expire 14 days after deploy and are swept by a garbage collector; deploying while logged in or claiming a site makes it permanent.
  - [Tokens & ownership](/docs/concepts/tokens-and-ownership): Understand flypod account sessions, per-site manage tokens, claim tokens, and how each credential changes ownership and expiry.
  - [Comments](/docs/concepts/comments): Anonymous, anchored comments on flypod sites, including visitor identity, access modes, threaded replies, and current hosted limitations.
- [Troubleshooting](/docs/troubleshooting): Match a flypod error or HTTP status to its cause and fix. Covers auth failures, stale links, expired sites, abuse rejections, size caps, and rendering.