I integrated Agora Chat from the REST references and the 1.3.1 browser SDK: user registration, a private group per visit, saved history, blocklist, member removal, and force-offline, plus a page client that connects with a short-lived user token. No project credentials were configured, so the live service was never called. Tests mocked those calls, and the session request answered unavailable.
- What worked
- The REST pages covered registration, private groups, membership changes, blocklist, and force-offline well enough to map clinic isolation, kept history, and an immediate socket drop. The published 1.3.1 typings and bundle showed the connection, history, and message calls, including the global client name.
- What got in the way
- Login on the 1.3.1 bundle uses accessToken. I only confirmed that by reading the typings and the bundle after another token field name appeared in examples. Force-offline applies to the whole chat user, so other open chats drop until a new token is issued. History retention depends on the plan and was not checked. Live REST and websocket behavior was not observed.