Skip to main content
floo is self-documenting. Install the skill, allow read-only commands, and your agent handles the rest.

​
Install the skill

floo skills install
Your agent now has the full floo command reference, config file shapes, and common workflows.

​
Allow read-only commands

Add floo to your agent’s allowed commands so it can run without prompting you for permission on safe operations. Claude Code (.claude/settings.json): 
{
  "permissions": {
    "allow": [
      "Bash(floo apps *)",
      "Bash(floo env list *)",
      "Bash(floo logs *)",
      "Bash(floo deploy list *)",
      "Bash(floo releases *)",
      "Bash(floo domains list *)",
      "Bash(floo services list *)",
      "Bash(floo analytics *)",
      "Bash(floo auth whoami *)"
    ]
  }
}
Cursor (.cursorrules): 
# floo deployment

This project deploys to floo. Use the `floo` CLI for all deployment operations.
Every command supports `--json` for structured output.

Key commands:
- floo deploy — deploy to production
- floo apps status <app> — check app status
- floo env set KEY=value --app <app> — set env var
- floo logs --app <app> — view logs
- floo deploy rollback <app> <deploy-id> — rollback
Other tools (Windsurf, GitHub Copilot):
ToolFile
Windsurf.windsurfrules
GitHub Copilot.github/copilot-instructions.md
Copy the Cursor rules content into whichever file your tool reads. The CLI is self-documenting via floo --help, floo <command> --help, and floo commands --json.

​
What your agent can do

Once the skill is installed, your agent can deploy, set env vars, add domains, view logs, roll back, and debug errors. All from the terminal. Every command supports --json for structured output. 
floo deploy --json 2>/dev/null | jq '.data.deploy.url'
Success: {"success": true, "data": {...}} Error: {"success": false, "error": {"code": "...", "message": "...", "suggestion": "..."}}