Multi-Instance Coordination — Run More Than One Widget Without Collisions

The widget loader already supports multiple instances, but production-grade multi-instance coordination requires more than just unique IDs. Once multiple agents live on the same page, they need rules for focus, event scoping, layout behavior, and programmatic control so they do not compete with each other.

Why this matters

Multi-widget pages are increasingly realistic in complex products. Examples include:

• Separate sales and support agents on the same site
• Different agents for different product areas or tenants
• Internal applications that embed multiple specialist agents side by side
• Documentation pages with one docs agent and one product agent

Without coordination, widgets can overlap, steal attention, and produce hard-to-debug event behavior.

The next maturity step

The current registry model is a strong technical base. This feature turns that technical capability into a fully supported product pattern. That means clearly scoped APIs, instance-specific events, optional focus rules, and predictable behavior when several widgets are active at once.

Product expectations

Hosts should be able to decide whether opening one widget minimizes another, whether multiple expanded widgets are allowed, and how z-index and screen space should be managed. Developers should also be able to target specific instances reliably for opening, closing, sending messages, and listening to events.

Business value

A strong multi-instance story makes the platform more flexible for enterprise customers, multi-brand deployments, and advanced integration partners. It also reduces support burden because integrators get a documented, stable pattern instead of relying on global references and trial-and-error behavior.

What success looks like

Multiple widgets can coexist on one page without confusing users or developers, and advanced customers can build more sophisticated agent layouts with confidence.