The command-line interface for floo - manage and observe web apps. Deploys are git-driven: push to main and floo builds and deploys it. This CLI handles everything else.
curl -fsSL https://getfloo.com/install.sh | bashOr download a binary directly from Releases.
# Install a specific release tag
curl -fsSL https://getfloo.com/install.sh | FLOO_INSTALL_VERSION=v0.1.0 bash
# Install to a custom directory
curl -fsSL https://getfloo.com/install.sh | FLOO_INSTALL_DIR="$HOME/.local/bin" bash| Platform | Architecture | Binary |
|---|---|---|
| macOS | Intel (x86_64) | floo-x86_64-apple-darwin |
| macOS | Apple Silicon (arm64) | floo-aarch64-apple-darwin |
| Linux | x86_64 | floo-x86_64-unknown-linux-musl |
| Linux | arm64 | floo-aarch64-unknown-linux-musl |
| Windows | x86_64 | floo-x86_64-pc-windows-msvc.exe |
Windows: Download floo-x86_64-pc-windows-msvc.exe from Releases and add it to your PATH.
# Check for updates and show the installed version
floo version
# Update to latest release
floo update
# Update to a specific release tag
floo update --version v0.1.0Updates retain bundled public CAs and also use native certificate trust.
SSL_CERT_FILE selects a PEM CA bundle instead of native store discovery.
If an older CLI cannot update behind your proxy, rerun the curl installer above
with your organization’s trusted CA configured for curl. The installer verifies
both the release checksum and signature.
From a local git repository with a floo.app.toml (create one with floo init <app-name>):
floo deployfloo asks the API where the code deploys from, then creates the app named
after [app] name, pushes the current commit, and waits until the dev URL is
live. A folder whose remote is on github.com deploys from that repository.
With no remote, pick --github (a private repo in your account, made with
gh) or --hosted (floo keeps a copy). Any branch other than the default
gets a preview URL. Every stop creates nothing and prints the fix. Commit your
changes first; floo deploy --preflight shows the plan. A hosted app moves to
your own GitHub repo, history included, with floo connect owner/repo.
For the HTTP-only path, read the agent guide.
floo commands --json # command tree
floo <command> --help # syntax for the installed CLI
floo docs --json # documentation topics and URLs
floo docs golden-path --json # quickstart URLfloo docs returns links to current web documentation. It does not bundle
articles or pin them to your CLI version. Command help is version-matched to
the installed binary.
For agent setup and the JSON output contract, read the agent guide.
The floo plugin gives Claude Code the floo skill and the floo MCP server
(https://api.getfloo.com/mcp, signed in with OAuth) in one install. Run this
in Claude Code:
/plugin install floo --marketplace getfloo/floo-cli
On Claude Code older than 2.1.275, add the marketplace first:
/plugin marketplace add getfloo/floo-cli
/plugin install floo@floo
The plugin lives in plugin/. Privacy policy.
The same plugin works in Cursor and Grok Bot, which install plugins from the
Cursor Marketplace. Install floo from the
Cursor Marketplace, then connect the floo
MCP server and approve the sign-in in your browser. In Grok Bot, open
Connect apps in the sidebar.
To try it from a local checkout, copy plugin/ to
~/.cursor/plugins/local/floo and run Developer: Reload Window. The
Cursor manifest is plugin/.cursor-plugin/plugin.json.
Use the current stable Rust toolchain, matching CI.
git clone https://github.com/getfloo/floo-cli.git
cd floo-cli
cargo build --bin floo-local
# Binary at target/debug/floo-localThe package builds floo, floo-local, and floo-dev. Use floo-local for
local CLI development: it stores credentials in ~/.floo-local/, separate from
installed floo (~/.floo/). Both default to the production API. floo-dev
uses the dev API and ~/.floo-dev/.
cd floo-cli
cargo build --bin floo-local
./target/debug/floo-local --help
# Or symlink: ln -sf $(pwd)/target/debug/floo-local /usr/local/bin/floo-localContributions are welcome. Please:
- Fork the repository
- Install the git hooks once (a pre-push gate runs
./scripts/teston Rust changes):./scripts/install-hooks.sh
- Create a feature branch (
git checkout -b feat/my-feature) - Run tests and lint before committing:
./scripts/test
- Use Conventional Commits (
feat:,fix:,docs:, etc.) - Open a pull request
The pre-push hook blocks a push whose Rust changes fail ./scripts/test; bypass an individual push with git push --no-verify when you're deferring to CI.
- Run
floo docsfor the web documentation index (floo docs --jsonfor agents). - Getting Started
- CLI Reference
- Configuration Reference
- Host an internal tool or admin dashboard built with AI
- Deploy a customer-facing app built with AI
- Deploy an app without a GitHub repository
- Build an app from Claude or ChatGPT
- A safe backend for an app built with AI
- App sign-in
- Move from Vercel to floo
- Move from Heroku to floo
- Leave floo anytime
- The best platforms to host an internal tool built with Claude Code
- How to build and deploy an internal tool with AI, step by step
- Where should I host an app I built with Claude Code?
- How to add a backend to an app your agent built
- Your app is a container: take it anywhere
MIT. See LICENSE for details.