EdgeInteract requires EdgeStream as its communication foundation. This guide walks you from installation through setting context, publishing messages, and controlling your first UI component.
EdgeStream is the required communication foundation. Install it first, then add the EdgeInteract packages you need.
If you are using React, add the hooks and UI packages. The vanilla JS chat window works without React.
The EdgeInteractClientService is the single facade for the entire system. Pass it an EdgeStream instance and it wires up ContextManager, CommManager, and PlayerManager automatically.
Set context once after login. Every subsequent message published via client.comm automatically carries this context — you never pass it manually again.
user.userId, user.permissions, session.sessionId, session.timezone, and session.locale — automatically. Your validation and routing hooks can access all of this without any additional lookup.
Before sending chat messages, set the active conversation. EdgeInteract uses this to isolate messages between users — User A's messages never reach User B's subscriber.
Register the built-in chat plugin, then use PlayerManager to display it. Every message sent or received carries the full context envelope.
Subscribe to a topic with an optional context filter. The filter ensures you only receive messages for the current conversation — context isolation built in.
Context enhancers run as a middleware pipeline on every message. Use them to add business data (customer tier, permissions, language) without changing any other code.
context.variables.customerTier available — in validation hooks, routing hooks, bot handlers, and UI components. No boilerplate in each subscriber.
Wrap your app in EdgeInteractProvider once. Then use hooks anywhere in the component tree to access state, players, and subscriptions.
Ask in the EdgeInteract community or book a session with the BizFirstAi team.