Agent-readable docs index: /llms.txt. Full docs in one file: /llms-full.txt. Download /docs.zip to grep all markdown files locally.

Build and inspect apps with your coding agent

Fleet works with any coding agent that can edit local files and run terminal commands. No Fleet-specific plugin, account, or hosted assistant is required.

Give your agent the contract

Open the app folder and point your agent at the generated AGENTS.md. A good first prompt looks like:
Read AGENTS.md. Add a search bar to this notes app. Keep the existing data format, use Fleet queries and mutations, and check fleet logs notes after editing. Do not start a separate dev server.
Your agent edits client/index.tsx, client/style.css, and server/index.ts. Fleet takes care of bundling, reloading browsers, HTTPS, and sign-in.

Inspect before editing

Your agent can check the live state of an app at any time:
fleet list --json fleet inspect notes fleet logs notes
  • fleet list --json lists every registered app and its build status in machine-readable JSON.
  • fleet inspect notes shows the current build revision, exported queries/mutations/jobs, and scheduled job state.
  • fleet logs notes prints recent build output, server ctx.log lines, and uncaught browser errors.
Ask your agent to inspect the current data shape before changing it — a build that compiles can still break old documents stored in ctx.db.

Test server operations from the CLI

Your agent can call queries, mutations, and jobs directly from the terminal on the computer that owns the checkout:
fleet call notes queries notes fleet call notes mutations addNote '{"text":"A note from my agent"}' fleet call notes jobs dailyCheck
Mutations and jobs run as you and write to real app data. Back up the database first before testing risky changes.

Verify changes cleanly

After an edit, have your agent verify four things:
  1. Run fleet inspect notes and fleet logs notes to confirm the build succeeded (remember: a failed build falls back to the previous working bundle, which can look like an edit didn't apply).
  2. Exercise changed queries or mutations with fleet call.
  3. Open the app in a browser and check fleet logs notes for any client errors.
  4. Confirm existing data still loads cleanly.

Back up before risky edits

Before changing how an app stores data, take a consistent SQLite snapshot:
fleet backup notes --output notes-before-change.sqlite
Keep backups outside the app host when the data matters. Git history and last-good builds protect your source code, not your database. See data and jobs.
Keep server credentials in .env.fleet.server (accessed via ctx.env), never in client code or logs. And let Fleet handle auth and serving — don't add a second login screen or start Vite inside a Fleet app.