Health Monitor

modelBridge watches the sequence you have open and the source media its clips point at, and tells you what it observed. Findings appear in the Health Monitor: a bar in the Agent tab, docked above the message box. It stays quiet when there is nothing to say and carries a count when there is.

It runs on its own while you work. Think of it as an assistant that spots technical surprises early — not as a system that certifies an edit is correct, or ready to deliver.

Health Monitor is available in the Agent tab when Agent Mode is ready to use. This requires an active modelBridge license and an Anthropic API key saved in Settings. Until then, the Agent tab shows the setup steps that are still needed.

What it checks

When a sequence is open in Premiere, Health Monitor looks at three things:

The active sequence — its own settings, chiefly frame rate and frame size
The clips on the timeline — where they sit, whether they are enabled, how they are interpreted
The unique source files those clips point at

That puts two kinds of observation in one list:

	Where it comes from	Example
Timeline signals	The sequence and the clips in it	A clip Premiere cannot find; a clip interpreted at a different rate than the sequence
Source-media observations	The files those clips reference	Colour or audio metadata that differs from the rest of the media in this sequence

There is no separate media check to run and no second panel to open. Both kinds of finding sort into the same list, and where they describe the same thing you see it once — an offline clip is reported by the timeline, not twice over. Related findings sit together: everything about rate and timing appears under Frame rate and timing, whether it came from the timeline or from a file’s own metadata.

Understanding findings

Findings arrive at one of three levels.

Critical. A concrete problem that can block work. Media Premiere cannot find is the clearest case: nothing renders where those clips sit.

Warning. Something that differs from the sequence or from the rest of your media, and may be worth a look before it costs you time later.

Heads up. Its own section at the bottom of the panel, collapsed until you open it, carrying the line “Nothing to fix — no edit in Premiere clears these.” These are observations worth knowing about. They are not a lesser grade of problem, which is why they are kept out of the count on the bar.

Fact, possible impact, and action

Every finding keeps three things apart, and so should you when you read one:

What was observed — the measurement itself, with no consequence attached
What it may lead to — always conditional, never stated as a fact about your edit
Whether anything can be done about it from here — which varies by finding

The distinction is not decoration. For example: media living on an external or cloud-synced volume is a relink risk, and Health Monitor will say so. It does not say that clip is offline — it says that only when Premiere reports it as offline.

The same discipline applies to the rest. Media that is heavy to decode is described as may be more demanding to edit at full resolution, because what was read is the file’s own properties, not your playback. A file that reports two different frame rates is flagged as reporting two different frame rates — confirming variable frame timing takes more than reading a file’s header, and the finding does not pretend otherwise.

Two baselines

An “issue” here is usually a difference, not a verdict that one value is wrong. Health Monitor compares against two things:

The active sequence’s own settings — a clip’s rate against the sequence rate, for instance
The rest of the media in this sequence — where a common value across your material acts as a practical baseline

If most clips in the current sequence report Rec.709 and one or two are tagged HLG, Health Monitor can flag the difference so you can review it before it becomes a surprise later in the edit or at export.

These are technical differences, not editorial ones. A clip that differs from the rest of your material may be exactly the clip you meant to use — a baseline drawn from your own media can tell you that something stands out, never whether it belongs in the story.

What it can show

Examples, not a complete or guaranteed list. What appears depends on your sequence, your media, and which checks you have left on.

Finding	What Health Monitor observed	What you can do
Offline media	Premiere reports the source media as unavailable	Relink it — take the action on the row when one is offered
Proxy that is not there	A clip is set to use a proxy file that is not at the recorded location	Re-attach or rebuild the proxy in Premiere
No proxy attached	A clip could take a proxy and has none	Nothing, unless a proxy workflow would help you on this material
Frame-rate interpretation	A clip’s interpreted or source rate differs from the sequence	Review the interpretation, and use the available action when one applies
Media in a risky location	A clip is linked to media on an external or cloud-synced volume	Consider where the media lives before the next time you reopen the project
Repeated file names	One file name is used by more than one file in this scope	Review before relinking — same-named files are a relinking hazard
Mixed colour metadata	Clips are tagged with colour metadata that differs from the rest of the set	Review the intended colour workflow for this edit
Two reported frame rates	A file reports different nominal and average rates in its own metadata	Review before sync-sensitive editing or handoff
Different audio shape	A clip’s sample rate or channel layout differs from the common shape in the set	Review before handoff or delivery
Demanding source media	Properties that may be more demanding to edit at full resolution	Consider your proxy workflow if editing this material feels heavy

When results are incomplete

Health Monitor separates what it measured from what it could not reach. When coverage is incomplete, the bar says Partly checked rather than presenting a clean result it cannot stand behind.

Open the panel and the first line says which kind of shortfall it was — that only the first part of the sequence was read, that part of it could not be read, or that some checks could not run at all. Findings that were measured fully are still shown, and a group that was only partly measured keeps its own marker rather than borrowing confidence from the ones beside it.

Results may be incomplete when you see this. Health Monitor avoids presenting a full-health result when it could not verify the full scope — the clips it never reached are exactly where an unreported finding would be.

The bar has a few other states worth recognising:

Bar reads	What it means
Checking sequence	A scan is running. Results can arrive in stages
Partly checked	Some of the scope or some of the checks could not be verified
Some checks unavailable	A check could not run at all
Premiere isn’t responding	Premiere has not answered, so what is shown is the last thing modelBridge knew. It usually picks up on its own; the refresh icon in the bar asks again now
No sequence open	Nothing to check — this is not a claim about your project
Just the sequence name	Nothing to report

Analysis runs in the background and is designed to stay out of your way: modelBridge would rather take a second pass than hold Premiere up for a single complete one. Material that has been analysed before can reappear faster.

Ask about this

Open any finding and it offers Ask about this.

The button prepares a question in the Agent message box, filled in from that finding: what was observed, what it may lead to, what the reading was based on, what the scan covered, how many clips are affected, and whether an action exists for it.

It does not send anything. No message goes out, no tools run, and nothing in your project changes. The draft sits in the message box as if you had typed it, and you decide whether to send it, edit it first, or clear it.

Use it when you want modelBridge to explain what an observation may mean for your edit. Review the prepared question and send it only if you want help.

Actions and limits

Some findings have a route through modelBridge; many do not, and the panel is explicit about which is which.

When an action is available, Health Monitor makes that clear. The button at the bottom of the panel names what it will act on — Fix 3 clips, or Fix 2 selected once you have ticked rows. An ellipsis (Fix 3 clips…) means a question comes first, because something in the selection has a decision the row did not show you. Where the whole selection is about how footage is interpreted, the verb changes to Review, since the goal there is a decision rather than a repair.

Nothing changes until you press that button. The monitor looks; it does not edit.

Findings without an action are not defects in the panel — they are observations that modelBridge can help you understand but cannot act on for you. Many source-media observations are in this group.

What Health Monitor does not do. It does not transcode, generate proxies, consolidate or move media, relink material on its own, remap audio channels, or change colour interpretation. It is not a delivery preflight: it does not verify durations against a delivery spec, check safe areas or legal copy, measure loudness or true peak, or inspect an exported file. Where a check like that matters to you, it still belongs in your own QC pass.

It also has no opinion about your edit. Pacing, shot choice, whether the ending lands — those are your call, and the monitor stays out of them. Ask the agent directly if you want a view on the edit itself.

Turning checks off

Every check has its own switch in Settings → Sequence Health. Turning one off stops modelBridge flagging that kind of finding anywhere — the bar, the list, and the agent’s own scan. See the Settings Tab for the controls.

Turn off what does not apply to how you work. A motion-graphics timeline full of deliberate two-frame clips has no use for flash-frame warnings, and a check that cries wolf is worse than no check, because you learn to skim past the ones that matter.

You can also dismiss a single row with the × on it without switching the whole check off — useful when one clip is deliberate and the rest are not. Hide puts the panel away for now; the toggle in the message-box toolbar turns the Health Monitor off entirely.

Questions

Why does it say Partly checked? Because something in the scope could not be verified: only part of a long or busy sequence was read, some source files could not be analysed, or a check could not run. Open the panel and the first line names which. The findings you can see are still real — the concern is what has not been looked at.

Why are some findings information rather than warnings? Because nothing you do in Premiere clears them, or because there is no verified route to act on them. Those are collected under Heads up so the count on the bar stays a count of things you might act on.

Why is one clip flagged when it looks fine? Usually because it differs from the sequence or from the rest of your media — a different colour tag, a different audio shape, a different rate. That is a difference, not a defect. If the clip is meant to be different, dismiss the row.

Does it change my project automatically? No. It reads and reports. Changes happen only when you press the action button in the panel and approve what follows, and Ask about this prepares a message without sending it.

Why did a finding appear a moment after I opened the panel? Source-media analysis runs in the background, so results can arrive in stages rather than all at once. Files analysed earlier tend to come back faster.