Dockerfile that serves on 0.0.0.0:$PORT; floo init offers to write one for a detected runtime.
Set up your agent
Install the CLI and sign in from your own terminal, before starting Codex:AGENTS.md at the agent guide:
https://api.getfloo.com. When Codex runs in its workspace-write sandbox, allow network access in ~/.codex/config.toml:
~/.codex/config.toml
Agent prompt
Paste into Codex. Replacemy-app with your app name.
floo.app.toml
The smallest configfloo init writes for one web service:
floo.app.toml
[managed.default] with type = "postgres" for a database, access_mode = "accounts" under [app] for App sign-in, and [cron.<name>] for scheduled jobs. Patterns: Configuring an app.
CLI commands
The same deploy by hand. Replaceowner/my-app with your repository.
floo apps github setup needs the floo GitHub App installed on the repository’s owner first. See Quickstart steps 2 and 3.
Verify
deploys status reports the live URL once the deploy is live. Load the URL, then read logs query --error for anything the app raised while serving it.
Every push to main deploys to dev. To publish to prod, run gh release create v1 --repo <owner>/<repo>. See Environments.
Start without GitHub
floo can host the repository.floo projects create makes a Next.js app with App sign-in and managed Postgres, deploys it, and returns its URL, with no GitHub steps:
floo releases promote --app my-app publishes to prod. See projects.
Next steps
Build with your stack
End-to-end guides for Next.js, Rails, FastAPI, Django, and Express.
Agent setup
JSON output, verification, and credential rules for agents.
Logs and debugging
Runtime logs, build logs, and a debug loop for a failed deploy.
Agent webhooks
Send failed deploys and repeated errors to your agent.