public active Last verified 2026-04-28

Topolo Chat

Public overview of the collaboration surface for channels, direct messages, meetings, guests, and remote-assist workflows.

Owners
collaboration
Source Repos
PlatformApplications/TopoloChat, PlatformApplications/TopoloDocs
Systems
Topolo Auth, Chat
Tags
chat, meetings, collaboration

What It Is

Topolo Chat is the collaboration application for channels, direct messages, meetings, guest access, transcripts, and future remote-assist workflows.

Architecture

Chat combines a Cloudflare-native backend, a web client, realtime and meeting bindings, and optional desktop and mobile shells.

Runtime Surfaces

The primary public surfaces are https://chat.topolo.app and the direct worker host documented in /systems/topolo-chat.

API Reference

The current contract is curated in the docs platform and centers on channels, DMs, uploads, meetings, guests, notifications, notes, audit events, and remote-assist transport.

Auth and Permissions

Topolo Chat uses Topolo Auth for workspace access. Protected workspace bearer-token requests validate through Auth and do not accept locally decoded JWT claims from a Worker secret. Browser login handoff, SSO callback-code redemption, and returning-user cookie hydration delegate to the shared Topolo Auth client, while guest meeting entry remains intentionally separate from normal workspace membership. Workspace-admin paths such as API key management now require explicit Chat service permissions instead of relying on local role-name heuristics. For first-party Topolo users, /login renders Chat’s branded shared LoginPage directly in the Chat shell. Hosted Auth login pages are reserved for third-party/provider handoff, not the default credential form.

Data Ownership

Chat owns workspace, membership, channel, DM, message, upload, meeting, guest, transcript, audit, and remote-assist session state.

Deployments

Chat deploys as a Cloudflare-backed collaboration app with optional desktop and mobile client shells.

Failure Modes

  • meeting join token flow drifts from guest or mobile launch flows
  • realtime or Durable Object bindings are unavailable
  • guest entry is mistakenly treated as normal workspace auth

Debugging

Start with /systems/topolo-chat, then separate workspace-auth issues from guest and meeting-launch issues before debugging deeper.

Change Log / Verification

  • Removed Chat’s hosted Auth redirect from /login on 2026-04-20 so first-party users sign in through the branded embedded shared LoginPage.
  • Removed the Chat worker’s residual local TOPOLO_JWT_SECRET handoff on 2026-04-18 so protected workspace bearer-token requests validate through Auth.
  • Delegated Chat web login handoff and callback-code redemption to the shared Topolo Auth client on 2026-04-18.
  • Added service-scoped Auth cookie hydration to Chat startup on 2026-04-18 so returning users can enter without a full hosted login redirect.
  • Standardized Chat admin permission checks on 2026-04-10 so API key management now follows the shared Auth permission model instead of local role checks
  • Standardized the public product label to Chat across the web shell, workspace bootstrap text, and meeting handoff flows on 2026-04-04
  • Added canonical Topolo Chat coverage and retired repo-local collaboration docs on 2026-03-30