Skip to content

Settings Tab

The Settings tab is where you manage your fal.ai API key, verify your connection, send feedback, and control what data is stored locally.

Paste your fal.ai API key into the key field. The key is validated immediately — you do not need to click a separate “test” button.

  1. Go to fal.ai/dashboard/keys
  2. Click Create Key
  3. Name it (e.g., “modelBridge”)
  4. Copy the key — it is shown only once

See the API Key Setup guide for full instructions.

The Settings tab shows a real-time connection status badge:

StatusIndicatorMeaning
Bridge ConnectedGreen dot with pulseKey is valid and fal.ai is reachable
Invalid API keyRed dotThe API key was rejected by fal.ai — check for typos or generate a new key
Not connectedAmber dotNo API key has been provided yet

When you enter or change the API key, the plugin validates it by making a test request to fal.ai. If the key is valid, all previously gated models are automatically rechecked — models that were blocked due to access restrictions may become available with the new key.

The Settings tab includes a built-in form for sharing feature requests and reporting bugs directly from the plugin.

  1. Click Feature Request & Bug Report to expand the form.
  2. Select Idea (a feature request) or Bug.
  3. Write your message, and optionally attach up to 3 screenshots (5 MB each).
  4. Click Send.

Your report includes some system context automatically so we can diagnose issues, and — when your license is active — your license ID and email so we can reply. For the complete, honest list of exactly what a report contains, see Reporting a Bug or Feature Request.

The Subscription section shows your current license status and provides account management actions.

A status badge at the top of the section shows your current subscription state:

StatusMeaning
ActiveSubscription is valid and all features are available
Trial — N days leftFree trial is active — full access until the trial end date. The last day reads Trial — last day
Renewal needed — Nd leftPayment failed and LemonSqueezy is retrying — full access continues while it does
Payment failedLemonSqueezy is still retrying the charge. Your license stays active, so generation continues
UnconfirmedThe license check is overdue — paste your key again to verify. Your subscription may well still be active; the plugin simply hasn’t been able to confirm it
Trial expiredThe free trial ended without a subscription — read-only mode
ExpiredSubscription has ended — read-only mode
Disabled / RevokedLicense was disabled or revoked — read-only mode, with a message to contact support

Below the status badge, the section shows your plan (monthly or annual) and when the license was last validated. The number of registered devices out of 2 lives in the Devices card below, alongside the name this machine is registered under and the control to release it.

The device count and the “last validated” time both refresh when your license is checked, which happens when you enter your key — so both can be up to a week old. The Devices card prints how long ago that was.

Manage subscription opens the LemonSqueezy customer portal where you can update your payment method, switch plans, download invoices, or cancel.

Release this device — in the Devices card — frees up one of your 2 activation slots. Use this when moving to a new machine: release on the old device, then activate on the new one. Releasing asks you to paste your license key to confirm; it’s in your LemonSqueezy receipt email.

When developer mode is enabled (developerMode: true in user-settings.json), an additional diagnostics section appears with license validation details, cache state, and debug information. This is not visible in normal use.

To use Agent Mode, paste your Anthropic API key in the dedicated field below the fal.ai key section.

  1. Create an account at console.anthropic.com
  2. Generate an API key
  3. Paste it in the Anthropic API key field in Settings

The Agent tab is always available in the tab bar. What it shows depends on what is set up: you need an active modelBridge license and an Anthropic API key saved in Settings to use Agent Mode. When both are in place, the tab opens on the agent. Its status dot reflects the Anthropic key status: green when confirmed, or amber when the key still needs attention.

The key is stored locally — it is never sent to modelBridge servers. You pay Anthropic directly at their published rates.

Toggle the audio chime that plays when a background generation completes. Useful when you’re working on other tasks and want to know when a result is ready.

Controls whether contextual Academy links and learning tips appear throughout the plugin — on model cards, in the Generate tab, and alongside parameters. When enabled, you’ll see “Learn about X” links that connect to relevant Academy articles based on the specific model you’re using.

Turn this off if you’re comfortable with generative AI concepts and prefer a cleaner interface. The setting is offered during onboarding and can be changed here at any time. All Academy articles remain accessible at docs.modelbridge.app/academy regardless of this setting.

The checks behind the Health Monitor each have their own switch here. They cover both what modelBridge reads from your timeline and what it reads from the source media those clips point at.

Turning a check off stops modelBridge flagging that kind of finding anywhere — the Health Monitor bar, its list, and the agent’s own scan. Turn off what does not apply to how you work: a check that cries wolf is worse than no check, because you learn to skim past the ones that matter. Each row names the check and what it is for, so you can decide per check rather than for the feature as a whole.

Reset to defaults turns everything back on in one press, via the Turn all on button at the bottom of the section.

If your settings data cannot be read, the section says so and behaves conservatively: every check stays on, and the switches are disabled until the settings file is rebuilt. Resetting to defaults is the way out — it writes a fresh file. This is deliberate: a check that silently switched itself off would leave you trusting a monitor that had stopped looking.

Your API key is stored in two places on your machine:

  • localStorage — for fast access during the session
  • Local settings file — managed by the plugin’s data directory for persistence across sessions
  • Your API key is never transmitted to modelBridge or any third party
  • It is used exclusively for direct communication between your machine and fal.ai’s API
  • No usage data, prompts, or generation history leaves your machine (except to fal.ai for generation)

To remove your stored API key:

  1. Click the edit icon on the masked key row
  2. Use the remove option and confirm

The key is removed from both localStorage and the settings file. You will need to re-enter it to generate content.

modelBridge communicates with these services:

ServicePurposeData Sent
fal.aiAI generation, schema fetching, pricingYour API key, prompts, uploaded media
AnthropicAgent Mode, on your own keyYour messages, project metadata, and — while a clip is selected — sampled frames of it
modelBridge licence serviceActivating and validating your subscriptionYour licence key and a device identifier. It validates them against LemonSqueezy; the plugin never contacts LemonSqueezy directly
modelBridge catalog & newsThe model catalog, news banner, model insightsYour plugin version and platform
modelBridge preview serviceMobile Preview, only when you use itA link to your fal.ai-hosted result, the model name, an anonymous install ID

Optional error telemetry and behavioral analytics are available but off by default. See Privacy Controls for details on what’s sent and how to opt in.

If you use Agent Mode, conversations are sent to Anthropic via your own API key — not through modelBridge servers.

All of your work — settings, generation history, installed models, cost logs, learned constraints — is stored locally on your machine and is never sent anywhere. What modelBridge’s own services hold is your subscription record; see the Privacy Policy for what that contains, how long it is kept, and how to have it deleted.

The Settings tab includes a reset option to clear all locally stored data. This removes:

  • Installed models and their schemas
  • Generation history and cost logs
  • Learned constraints
  • User settings and preferences

The reset requires typing “DELETE” as confirmation to prevent accidental data loss. Your API key must be re-entered after a reset.

See Updating modelBridge for what persists through plugin updates (everything — reset is only for a full clean start).