fimo projects, --project-id, and .fimo/project.json are unchanged. Use the commands below exactly as written.
Run a one-off command with the latest CLI release without installing it globally:
- npm
- Bun
- pnpm
- Yarn
- npm
- Bun
- pnpm
- Yarn
fimo <command> for brevity. Run fimo --help for the full surface and fimo <command> --help for every argument and flag.
Site-scoped commands target the current Git Branch. Use --branch <name> to override it for one command; the removed --env <name> selector is rejected. Other global options include --json, --no-color, and --ascii. Some commands add their own output flags.
Paginated lists
Paginated list commands share three flags:--limit sets the page size. When more results exist, the command returns a nextCursor or prints an exact continuation command using --cursor. Use --all-pages when you intentionally need every remaining result. The older --before, --offset, and schedule --all spellings remain accepted as compatibility aliases, but new scripts should use the shared flags.
Sites & onboarding
Migration
fimo migrate init only sets the target up: it creates or links the site, scaffolds it, and pushes the first commit. It never reads the source site. Your coding agent reads the source and does the rebuild.
Migration flags
Account & organizations
Support
Content
See Content and schemas for the content workflow.
Forms
Media
Labels
Locales
Deploy & publish
See Deploy and publish for the workflow.
Branches
Environments
Environments group Branches for deployment. They are a different concept from a Branch: Production and Preview are built in, and a custom Environment claims Branches by name or pattern.Site variables & secrets
Variables are public by design and may use browser-safe prefixes such as
VITE_, PUBLIC_, or NEXT_PUBLIC_. Secrets are hidden after they are written, never reach the browser bundle or generated files, and cannot use those prefixes. There is no private-variable mode: if leaking a value would be a problem, use fimo secrets.
fimo vars writes into a managed block in .env.local so local development picks the value up immediately, and fimo vars pull refreshes it later. See Secrets for the Studio side, and use --help before changing stored values.
Integrations
Firecrawl and Fal are built into Fimo. Fimo owns the provider account and bills the site in Fimo credits, so
fimo integrations enable <key> is their whole setup and connect is refused for them. To use your own provider
account instead, add that provider’s MCP server with fimo mcp add.
Provider-defined tools and inputs can change. Run fimo integrations info <key> before invoking one.
Remote MCP servers
Use
fimo mcp <command> --help for the connection and input flags. See MCP servers for the setup workflow.