Chat
Cloudflare-native collaboration application for channels, DMs, meetings, guests, and remote assist.
Documentation Map
What It Is
Cloudflare-native collaboration application for channels, DMs, meetings, guests, and remote assist.
Canonical documentation for Topolo Chat lives in `PlatformApplications/TopoloDocs`.
Use this repository for implementation only. Local product and operational docs have been retired in favor of the docs application.
Architecture
Owners: collaboration
Source repos: PlatformApplications/TopoloChat
Dependencies: topolo-auth, applications-packages
Repo shape
- PlatformApplications/TopoloChat/AGENTS.md
- PlatformApplications/TopoloChat/README.md
- PlatformApplications/TopoloChat/cloudcontrol-deployment-report-topolo-chat.json
- PlatformApplications/TopoloChat/index.html
- PlatformApplications/TopoloChat/migration.config.ts
- PlatformApplications/TopoloChat/migrations/
- PlatformApplications/TopoloChat/mobile/
- PlatformApplications/TopoloChat/package-lock.json
- PlatformApplications/TopoloChat/package.json
- PlatformApplications/TopoloChat/public/
- PlatformApplications/TopoloChat/scripts/
- PlatformApplications/TopoloChat/src/
- PlatformApplications/TopoloChat/src-tauri/
- PlatformApplications/TopoloChat/test/
- PlatformApplications/TopoloChat/topolo.cloudcontrol.json
- PlatformApplications/TopoloChat/tsconfig.json
- PlatformApplications/TopoloChat/vite.config.ts
- PlatformApplications/TopoloChat/vitest.config.mts
- PlatformApplications/TopoloChat/worker-configuration.d.ts
- PlatformApplications/TopoloChat/wrangler.jsonc
Runtime Surfaces
Hosts:
https://chat.topolo.app https://topolo-chat.topolo.workers.dev No wrangler surface was discovered under the registered repo paths.
API Reference
Coverage: curated
Source: PlatformApplications/TopoloDocs/src/content/public/applications/chat.mdx
Source exists in repo: yes
Canonical Chat coverage now lives in the docs application. Chat mobile resolves `topolo_auth_flutter` from the canonical Auth repo git package path. The Chat web shell serves first-party /login through the branded shared LoginPage resolved from the `srv_topolo_chat_web` UI Kit registry entry, delegates third-party/provider handoff, returning-user cookie hydration, embedded password-login token persistence, and fallback callback restoration to the shared Topolo auth client, while Chat-owned app state completes successful password login by navigating to /app and the HTML document pre-consumes fresh one-time sso_code callbacks before React bootstraps. The authenticated workspace renders through `TopoloAppShell`, inheriting the shared Improve Topolo and TopoloNotify chrome while keeping Chat's channel, DM, and meeting rail product-owned. The Worker owns the same-origin /api/auth/* Auth data gateway, schedules organization-directory reconciliation after bootstrap, binds CHAT_UPLOADS to production and preview R2 upload buckets, exposes `GET /api/widget` with the shared `@topolo/sdk` widget response contract for TopoloOne live workspace, and accepts Calendar's token-authenticated `POST /api/internal/calendar/meetings` bridge to create Chat meetings plus guest invite URLs for `chat_meeting` bookings.
App API page: /reference/apps/topolo-chat
This system currently relies on a curated or README-derived contract surface instead of a source-controlled OpenAPI spec.
Auth and Permissions
Depends on Topolo Auth: yes
Service IDs:
srv_topolo_chat_web API key scopes
Manage Chat machine credentials
Resource pattern: none
View workspace audit events
Resource pattern: none
View channels and channel state
Resource pattern: none
Create or update channels
Resource pattern: none
View direct conversations
Resource pattern: none
Manage direct conversations
Resource pattern: none
View meetings, transcripts, and polls
Resource pattern: none
Create or manage meetings and participation
Resource pattern: none
Read channel and direct messages
Resource pattern: none
Create or update messages
Resource pattern: none
View operational threads
Resource pattern: none
Manage operational threads and comments
Resource pattern: none
Search workspace messages and files
Resource pattern: none
Manage notification and workspace settings
Resource pattern: none
Create and complete upload drafts
Resource pattern: none
Load workspace bootstrap and search data
Resource pattern: none
Manage workspace policies and preferences
Resource pattern: none
Service permissions
api_keys:write, audit:read, channels:read, channels:write, direct_messages:read, direct_messages:write, meetings:read, meetings:write, messages:read, messages:write, operational_threads:read, operational_threads:write, search:read, settings:write, uploads:write, workspace:read, workspace:write
Data Ownership
No storage bindings were derived from wrangler configuration.
Queues / Cron / Workflows
Queue bindings:
No queue bindings were detected.
Cron triggers
No cron triggers were detected.
Workflow signals
No explicit queue/workflow script or cron signal was discovered.
Environment Variables and Bindings
Environment variables:
No environment variables were derived from wrangler configuration.
All wrangler bindings
No bindings were derived from wrangler configuration.
Deployments
Deployment environments: default only or not declared
Routes: workers.dev or Pages-only delivery
Observability enabled: no explicit setting found
Build and deploy commands
-
build— PlatformApplications/TopoloChat/package.json :: vite build -
deploy— PlatformApplications/TopoloChat/package.json :: wrangler deploy -
desktop:build— PlatformApplications/TopoloChat/package.json :: tauri build
Failure Modes
- No wrangler.toml surface was discovered under the registered repo paths.
Debugging Runbooks
Start with these entrypoints:
- PlatformApplications/TopoloDocs/src/content/public/applications/chat.mdx
- PlatformApplications/TopoloChat/README.md
- PlatformApplications/TopoloChat/package.json
Change Log / Verification
Lifecycle: active
Last verified: 2026-04-27
Any code change to this system is expected to update the canonical docs in PlatformApplications/TopoloDocs and refresh the verification date.