Reporting a Bug or Feature Request

modelBridge has a built-in form for sending a bug report or a feature request straight from the panel. You only ever send a report when you choose to — nothing is collected in the background.

How to send one

1. Open the Settings tab.
2. Click Feature Request & Bug Report to open the form.
3. Choose Idea for a feature request, or Bug to report a problem.
4. Write your message. For a bug, the more you tell us about what you were doing, the better.
5. Optionally attach up to 3 screenshots (5 MB each) — they make bugs much easier to understand.
6. Click Send.

If you’d rather email us, write to info@modelbridge.app.

What your report includes

We keep reports small and honest. Here is everything a report can contain.

Always:

• Your message, and whether it’s a feature request or a bug.
• Your name and email — only if you fill them in. When you’re signed in with an active license, the email field is pre-filled with your license email so we can reply; you can change it. It’s used only to reply.
• Basic system info: your modelBridge version, Premiere Pro version, operating system and version, the panel runtime version, how many models you have installed, and whether the local helper is running.
• The last few error messages from your current session (technical text only — file paths, links, and any prompt text are stripped out first).

If your license is active:

• Your license ID and the email on your license are attached automatically, so we can match the report to your account and reply to the right person.
• Your license key — the secret you paste to activate — is never sent; modelBridge doesn’t keep it after activation.
• These identify which account a report came from — they’re a lookup key for support, an indication of who sent it, not a verified login or proof of identity. We always confirm you through your account before making any billing or account change.

When you report a bug with a model open:

• Which model you had open and its technical settings, plus the result of your most recent run of that model (success, or the type of error) and the settings you used.
• A cleaned-up copy of the last error the model returned (links and prompt text removed).
• The type, width, height, and length of your selected clip — never the clip itself, and never its file path.
• A short technical error log from your session (the most recent messages, with file paths, links, and prompt text stripped out).

Screenshots: any you choose to attach.

What is never sent

• Your clip or footage — only its dimensions, never the file or its location on disk.
• Your prompt text — never included, unless you are in Developer Mode and explicitly tick “Include my prompt text.”
• Your fal.ai API key — never included in a report.

Where your report goes

Reports go to a private inbox that only we can read. They are not posted publicly. If a report can’t be delivered, it waits on your machine and retries later (screenshots are dropped from the retry to save space).