Topolo 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.
Topolo Chat is a Cloudflare-native collaboration app for channels, direct messages, meetings, guest access, and future remote assist.
Architecture
Owners: collaboration
Source repos: Applications/topolo-chat
Dependencies: topolo-auth
Repo shape
- Applications/topolo-chat/AGENTS.md
- Applications/topolo-chat/README.md
- Applications/topolo-chat/index.html
- Applications/topolo-chat/migrations/
- Applications/topolo-chat/mobile/
- Applications/topolo-chat/package-lock.json
- Applications/topolo-chat/package.json
- Applications/topolo-chat/public/
- Applications/topolo-chat/src/
- Applications/topolo-chat/src-tauri/
- Applications/topolo-chat/test/
- Applications/topolo-chat/tsconfig.json
- Applications/topolo-chat/vite.config.ts
- Applications/topolo-chat/vitest.config.mts
- Applications/topolo-chat/worker-configuration.d.ts
- Applications/topolo-chat/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: readme
Source: Applications/topolo-chat/README.md
Source exists in repo: yes
README documents the current worker API, web shell, durable objects, and live hostnames.
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
Load workspace bootstrap and search data
Resource pattern: none
Manage workspace policies and preferences
Resource pattern: none
View channels and channel state
Resource pattern: none
Create or update channels
Resource pattern: none
Read channel and direct messages
Resource pattern: none
Create or update messages
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
Create and complete upload drafts
Resource pattern: none
Search workspace messages and files
Resource pattern: none
View operational threads
Resource pattern: none
Manage operational threads and comments
Resource pattern: none
View workspace audit events
Resource pattern: none
Manage notification and workspace settings
Resource pattern: none
Service permissions
workspace:read, workspace:write, channels:read, channels:write, messages:read, messages:write, direct_messages:read, direct_messages:write, meetings:read, meetings:write, uploads:write, search:read, operational_threads:read, operational_threads:write, audit:read, settings: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— Applications/topolo-chat/package.json :: vite build -
deploy— Applications/topolo-chat/package.json :: wrangler deploy -
desktop:build— Applications/topolo-chat/package.json :: tauri build
Failure Modes
- No wrangler.toml surface was discovered under the registered repo paths.
Debugging Runbooks
Start with these entrypoints:
- Applications/topolo-chat/README.md
- Applications/topolo-chat/package.json
Linked runbooks
Change Log / Verification
Lifecycle: active
Last verified: 2026-03-29
Any code change to this system is expected to update the canonical docs in Websites/docs and refresh the verification date.