Configuration

A flow has a draft and published revisions. The widget loads published config with a publishable key. Publishing stores that JSON on Bootstrapware. It does not grant live entitlement by itself.

What lives in config

• Items. Up to 32 steps: key, title, description, optional, dependsOn, progressScope (user or workspace), eligibility.
• Eligibility. Optional roles, plans, and flags (max 16 flags, match all or any). Evaluation stays in the widget from host context. Never send host context through MCP.
• Toggles. requireAuthorToken, empty-state copy, snooze days (default 1 and 7), allowed origins.
• Branding. Optional logo URL and accent. Cream + lime by default; light only.

Local mode can pass items as props and skip hosted fetch. Hosted and BYO typically load items from the published flow so agents can update the checklist without a code deploy. Path C (adapter + flowId + publishableKey) still fetches config; the adapter only owns progress.

How to change it

• Dashboard flow editor (preview, publish, restore). Delete stays dashboard-only.
• MCP: create_flow, update_draft (does not publish), publish_flow, list_revisions, restore_revision, get_published_config.
• Secret HTTP: create, PATCH draft, POST publish. See API.

Live fetch still needs a plan

Live bsw_live_pub_ config fetch needs BYO ($9.99) or Hosted ($19.99). Live Hosted progress writes need Hosted ($19.99). Test keys work unpaid. Local adapters never call Bootstrapware.

Related: Revisions · Eligibility · Preview and rollback · API · Environments