React Router state synchronization across multiple tabs during token expiration

When implementing least-privilege access via React Router and React Context, maintaining authentication state consistency across multiple browser tabs presents a challenge. If a JWT expires or a session is invalidated in one tab, the client-side state in other tabs remains active until a manual action or a page refresh occurs.

Since React state is volatile and local to the tab, a global logout triggered by an Axios interceptor does not automatically propagate to other open instances. Relying solely on 401 error handling can lead to a fragmented UI where the user appears authenticated in some views but unauthorized once the next data fetch fails.

What are the most efficient patterns for synchronizing session invalidation across concurrent browser contexts without introducing constant API polling? Can the Broadcast Channel API be integrated into a custom hook provider to ensure an immediate state reset when a token is revoked globally?