Docs

How to update, and how to uninstall

Updated 6 Nov 2026# Link

To update, replace the bridge folder and start it again. To uninstall, remove the shortcuts, the panel and the folder. At the end: what stays behind.

Update (the zip from this website)

1. Download the new zip from the home page. Right-click it and choose Extract All.

2. Close the bridge window: the black window titled Premiere Agent Bridge.

3. Replace your old ppro-agent-bridge folder with the ppro-agent-bridge folder from the new zip. Put it in the same place, so your shortcuts keep working.

4. Double-click the Premiere Agent Bridge shortcut (or 2 Start Premiere Agent Bridge.bat from the zip). It loads the new panel into Premiere by itself.

5. Check: the panel says Connected to broker, and when your helper checks the bridge it reports "compatible": true.

Uninstall

1. Close the bridge window, and close the Agent Bridge panel in Premiere.

2. If the bridge starts with Windows, turn that off: double-click setup_bridge.bat in the bridge folder and switch off Start with Windows. Or delete the Premiere Agent Bridge shortcut in your Startup folder.

3. Delete the Premiere Agent Bridge shortcuts on your desktop and in the Start menu.

4. In UXP Developer Tool, unload the Agent Bridge panel. If you once added it there by hand with Add Plugin, remove it from the list too.

5. Delete the ppro-agent-bridge folder.

6. If you want, delete the folder %USERPROFILE%\.ppro-agent-bridge as well. It holds the pairing token and the request log (see What we keep on your PC).

If you installed the panel as a .ccx package

1. Close Premiere.

2. Run Creative Cloud’s plugin installer with /remove "Agent Bridge". It is UnifiedPluginInstallerAgent.exe, in Common Files\Adobe\Adobe Desktop Common\RemoteComponents\UPI\UnifiedPluginInstallerAgent\.

3. To update instead of uninstalling: remove it as above, then run the installer with /install and the new .ccx file, still with Premiere closed. Installing over the old version does not reload it.

The panel says “not connected”

Updated 6 Nov 2026# Link

Go through these checks in order. Most of the time the first one fixes it.

1. Is the bridge window open? The panel’s status line says the following (in a Chinese Premiere: 未连接：桥没有在运行？):

   Disconnected — broker not running?

   Click Start bridge on the panel, or double-click the Premiere Agent Bridge shortcut, and leave the black bridge window open while you edit. The first time you click Start bridge, you are asked whether the panel may start it: allow it. The panel connects within about 20 seconds: its icon turns from faded to full colour and the status says Connected to broker.

2. Did the bridge window close at once, or show an error about port 8017? Another program already uses the bridge’s port. The window says, for example:

   Cannot listen on 127.0.0.1:8017 (…). It is held by PID 1234 (python.exe). Is another broker running? Close that program, then start the broker again.

   Usually it is a second bridge window that is already running: use that one, or close it and start again. If the message names another program, close that program. (On [::1]:8017 the message is a little longer and says the same.) The bridge refuses to share its port on purpose: otherwise the panel would reach the other program instead of the bridge.

3. Does your helper report AUTH_FAILED? The bridge turned down its pairing token. The message begins:

   This broker (0.6.0) needs the pairing token and got no pairing token. …

   It means your helper runs another copy or version of the bridge than the bridge window does (a command line older than 0.5 sends no token), runs as another Windows user, or has a PPRO_BRIDGE_TOKEN setting the bridge does not have. Have it use the bridge folder the panel names in its first message, the folder the bridge window runs from. Never paste, copy or send the token itself.

4. Is the panel out of date? When your helper checks the bridge, it reports "compatible": false with a warning such as:

   Panel is ppro-agent-bridge 0.5.1, CLI is 0.6.0: reload the Agent Bridge panel in UXP Developer Tool.The panel is stale — its code differs from this checkout's plugin folder: Reload it in UXP Developer Tool.

   Close the bridge window and start it again: it loads the current panel into Premiere by itself. Or click Reload on the Agent Bridge panel in UXP Developer Tool (which must be running). If the panel says it is stuck, save your project first, then reload it.

5. Was the panel turned away because another one is connected? The status line says:

   Refused: A live Agent Bridge panel is already connected — retrying in 30 s

   Only one panel at a time can use the bridge. Another Premiere window (Premiere Pro Beta, say) or a second copy of the panel holds it. Quit the other Premiere, or unload that panel in UXP Developer Tool: closing it is not enough, because a closed panel stays connected. This panel takes over within 30 seconds, or at once when you click Reconnect.

6. Still not connected? Double-click setup_bridge.bat in the bridge folder: the setup window checks Python, Premiere, UXP Developer Tool and developer mode again. Then tell me on GitHub. From 0.7 your helper can make a problem report to paste there; it never contains your token.

What we keep on your PC, where, and for how long

Updated 6 Nov 2026# Link

Everything the bridge writes outside its own folder, where to find it and when it goes away. There is no account and no tracking, and the bridge uploads none of it.

1. The pairing token: %USERPROFILE%\.ppro-agent-bridge\token. A random secret the bridge makes the first time it starts. Your helper’s command line sends it with every request, so other programs cannot control the bridge. It stays until you delete it; the bridge then makes a new one at its next start. Never share it.

2. The request log: %USERPROFILE%\.ppro-agent-bridge\audit\audit-YYYY-MM-DD.jsonl, one file a day. One line per request: what was asked (long values such as file paths cut short), the sequence it worked on, how it ended and how long it took. Kept 30 days: older files are deleted when the bridge starts. Your helper reads it to find out what happened earlier. To turn it off, set the environment variable PPRO_AUDIT_DIR=off.

3. Shortcuts: Premiere Agent Bridge on your desktop and in the Start menu, and in your Startup folder if you switched on Start with Windows. They stay until you delete them; the setup window can switch Start with Windows off again.

4. The panel in Premiere: the bridge loads it through UXP Developer Tool each time Premiere starts, the same as clicking Load there. UXP Developer Tool and developer mode stay installed and switched on. If you installed the panel as a .ccx, Creative Cloud keeps it until you remove it (see How to uninstall).

5. WAV copies of music (from 0.7): Premiere cannot read FLAC, Opus or Vorbis. When such a file is imported, a 48 kHz 24-bit WAV is written next to it (song.wav, or song (48k).wav when a different song.wav is already there) and the WAV is imported instead. A WAV of the same length already there is reused. It stays, because your project now uses it.

6. Render leftovers: while Premiere renders an H.264 video, it first writes temporary files next to the target (the file name plus a long code, ending in .m4v and .aac) and writes the .mp4 at the end. These are Premiere’s own files; the bridge does not delete them. If a render stopped half-way, you can delete them.

7. Update-check settings (from 0.7): %USERPROFILE%\.ppro-agent-bridge\settings.json. Once a day the bridge asks GitHub for the number of the latest version, so the panel can tell you when a new one is out. It sends no account, machine or user ID. The check is on by default and can be turned off; versions you choose to skip are remembered in this file.

8. What your helper makes: transcripts, exported frames, edit plans and audio for the listening check go into the folder you opened Claude Code or Codex in. In your project, restore points are extra sequences named “… [restore YYYY-MM-DD HH:MM]”; the newest 5 of each sequence are kept. Delete them when you no longer need them.

9. Whisper models, if you transcribe on your PC: the first run downloads the model files. faster-whisper keeps them in its own download folder; the bridge does not choose that place.