Invisible UXP for Bridge & Automations

Premiere Pro
,
1

I’m working on a Premiere Pro plugin for a client where most of the heavy lifting happens in an external companion application. The Premiere side currently uses a custom CEP extension as a bridge between the external app and Premiere.

The goal was for the Premiere-side bridge to be silent/background behavior, so the user does not need to keep a visible plugin panel open for the companion app to trigger Premiere-side actions. The intended workflow is similar to a custom action wheel/controller for Premiere: the external app handles the interface and logic, while the Premiere extension executes the host-side actions.

After the most recent Premiere update, this CEP bridge appears to have silently broken. The main symptoms are:

  • Premiere-side actions are no longer applying reliably
  • The external companion app no longer communicates with Premiere consistently
  • The issue started immediately after Premiere auto-updated
  • Rolling Premiere back to an older version restores the plugin behavior
  • Another tester confirmed the same issue on their machine

I have not found any official note saying Premiere killed or blocked custom CEP panels, invisible CEP panels, or background CEP behavior. But given Adobe’s move toward UXP, I wanted to ask here before making a larger architecture decision.

My questions are:

  1. Did something change recently in Premiere 26.3 that affects hidden, invisible, or non-user-facing CEP panels?
  2. Is using a CEP panel as a silent communication bridge still supported in current Premiere versions?
  3. If this kind of CEP bridge is no longer reliable, is there a recommended UXP equivalent?
  4. Can a UXP plugin run silent/background behavior without requiring the user to keep a visible panel open?
  5. Can UXP support communication from an external companion application into Premiere, similar to how CEP/ExtendScript has been used for host-side automation?
  6. If this is not currently possible in UXP, is there a recommended architecture for plugins that need automation without adding a persistent visible panel to the user’s workspace?

This matters because a lot of workflow plugins rely on automation that should not require an always-open panel. I’m trying to understand whether this is a bug, an intentional platform change, or a sign that this architecture needs to move away from CEP to UXP.

Any clarification from Adobe or other plugin developers would be appreciated.

2
  • Premiere-side actions are no longer applying reliably
  • The external companion app no longer communicates with Premiere consistently

Your report is the first we’ve heard, of anything like this behavior. Lots more specifics, please…? Which calls behave unreliably?

  1. Did something change recently in Premiere 26.3 that affects hidden, invisible, or non-user-facing CEP panels?

No.

  1. Is using a CEP panel as a silent communication bridge still supported in current Premiere versions?

Yes.

  1. Can a UXP plugin run silent/background behavior without requiring the user to keep a visible panel open?

No. Support for invisible UXP plugins won’t be available until next year.

  1. Can UXP support communication from an external companion application into Premiere, similar to how CEP/ExtendScript has been used for host-side automation?

Yes, using a Hybrid UXP plugin.

1 Like