cli

Docs · Guides · Agents · Changelog

fillo — create and publish Fillo forms from your terminal. Auth once, then your coding agent does the rest.

npx @usefillo/cli init --email you@company.com # start a workspace and email its link
npx @usefillo/cli login                         # connect an existing account in the browser
npx @usefillo/cli project create "Customer site" # create + select an isolated site/app
npx @usefillo/cli push form.json --handle hello --stage # stage for dashboard review
npx @usefillo/cli@latest skill install           # install the project Agent Skill

Commands: init, login, logout, whoami, project list|create|select, push <file|->, list, agent bootstrap, agent connect, agent event, and skill install. Run npx @usefillo/cli --help for flags. The canonical skill is one portable Agent Skills bundle. The default command installs it in the shared .agents/skills path and Claude Code's .claude/skills path — both get the same files, for cross-agent compatibility rather than duplication. Hosts with another location can use skill install --dir <agent-skill-directory>, so the same bundle works without provider-specific forks. See fillo.so/agents for setup. The API commands target https://fillo.so by default (set FILLO_API to override).

Stage instead of publish

--stage creates or replaces a reviewable draft without taking the published form offline; a plain authenticated push publishes directly.

npx @usefillo/cli push form.json --handle customer-onboarding --stage

CI staging with least-privilege sync tokens, pushing a schema from stdin, and the raw sync endpoint are covered in the CLI guide: fillo.so/docs/cli. The agent handoff and progress protocol (fillo agent event) live at fillo.so/agents.

A Fillo browser handoff supplies an agent bootstrap command. It installs the skill and connects the live setup in one run. With --account, it also opens Fillo so the user can approve the exact workspace and project before the agent continues. The approval screen can create a project inside the selected workspace. After an ordinary fillo login, use fillo project list, fillo project create <name>, and fillo project select <id|slug|unique-name> to move the local login deliberately. A handoff login is pinned to its approved project and cannot enumerate, create, or select sibling projects. Projects isolate forms, keys, origins, identities, and agent access while members, billing, storage, and usage totals remain workspace-wide.

Response destinations from the terminal

Connect Discord — one-click OAuth or a pasted webhook URL — enable it per form, and mint a connector token for n8n or Zapier, all without a dashboard trip:

npx @usefillo/cli discord connect                    # one-click OAuth (needs the deploy's Discord app)
npx @usefillo/cli discord webhook                     # paste a channel webhook URL at a hidden prompt
# non-interactive (agents/CI): FILLO_DISCORD_WEBHOOK_URL=... npx @usefillo/cli discord webhook
npx @usefillo/cli discord enable customer-intake --fields email,plan
npx @usefillo/cli discord status customer-intake
npx @usefillo/cli tokens create-connector --tool n8n  # prints an fcli_ token once

discord enable also takes --early-signal 5|10|25|off (every answered field for the first N responses) and --role <guildId>/<roleId> with an optional --auto-join (grant a connected server's role to a verified respondent, and add non-members to the server too) — discord roles [guildId] lists a connected server's roles, and discord disable <form> turns a destination off. --early-signal and --auto-join both send more than the standing setup; an agent should surface that decision and get its human's explicit agreement before setting either one. Full reference: fillo.so/docs/cli.

Links

• Docs: fillo.so/docs
• Website: fillo.so

MIT licensed.