Settings
Configure your workspace, API keys, and workflow-level settings.
Workspace Settings
Go to Settings in the sidebar to manage workspace-wide configuration.
Workspace Context
You can set key-value pairs that are injected into every compilation in your workspace. This is useful for:
- Default API base URLs
- Environment identifiers (staging vs. production)
- Shared configuration that multiple workflows reference
These values appear in the AI compiler's context, helping it generate more accurate plans.
Recovery Settings
Configure how workflows recover when a step fails. Go to Settings → Recovery (or set via API: PUT /v1/settings/:key).
| Setting | Values | What it does |
|---|---|---|
recovery.mode | agent, server, off | agent: failed steps open a needs_agent gate — your AI agent polls an inbox and submits fixes. server: external A2A or MCP server handles recovery synchronously. off: built-in AI recovery only. |
recovery.agent_timeout | 30–3600 (seconds, default 300) | How long to wait for an agent to submit a fix before falling through to built-in recovery. Only applies when recovery.mode = "agent". |
recovery.mcp_server_id | MCP server ID | Which workspace MCP server handles recovery (must exist in your workspace). Used when recovery.mode = "server". |
recovery.timeout_ms | 1000–60000 (ms) | Timeout for MCP/A2A recovery calls. |
recovery.a2a_agent_url | HTTPS URL | External A2A agent endpoint. Must be HTTPS. Agent card auto-discovered at /.well-known/agent-card.json. Takes priority over MCP when both configured. |
recovery.a2a_auth_token | String | Bearer token for A2A agent auth. Encrypted at rest (AES-256-GCM). Redacted as [configured] in GET responses. |
See BYOA Recovery for the full setup guide.
Agent Approval
| Setting | Values | What it does |
|---|---|---|
allow_agent_approval | true, false (default: false) | When enabled, AI agents can approve or reject human_approval gates via the approve_step MCP tool. This is an explicit opt-in — by default, only humans can approve gates. |
API Keys
Manage API keys under Settings → API Keys.
Creating a Key
- Click Create Key
- Give it a descriptive name (e.g., "CI/CD Pipeline", "Slack Bot")
- Copy the generated
wfk_key immediately — it's shown only once
Key Restrictions
- API keys are scoped to your workspace
- Keys can only trigger published workflows (403 on drafts)
- Each key works with the webhook trigger endpoint and the BYOA MCP server
Revoking a Key
Click the delete icon next to any key. The key stops working immediately. Any integrations using it will start receiving 401 errors.
Workflow Settings
Each workflow has its own settings page. Go to a workflow → Settings tab.
Publish / Unpublish
- Published workflows can be triggered via API keys, cron schedules, and webhooks
- Draft workflows can only be run from the dashboard
- Unpublishing a workflow does not stop in-flight runs
Share Link
Generate a public read-only link for your workflow:
- Click Generate Share Link
- Copy the URL
- Anyone with the link can view the workflow's DAG and latest run output
Revoke sharing by deleting the share token.
Cron Schedule
Set a recurring execution schedule. See Triggers & Scheduling for details.
Organizations
CFFBRW uses Clerk organizations for multi-tenant workspaces:
- Switch between organizations using the switcher in the sidebar
- Each organization has its own workflows, runs, MCP servers, API keys, and billing
- Invite team members through Clerk's organization management
All data is scoped to the active organization. Switching organizations changes what you see across the entire dashboard.