AI-native team messaging

Team chat with an agent built into the work.

Zergchat brings channels, DMs, threads, search, huddles, files, admin controls, and a scoped Zerg agent into one durable workspace.

Private-room awarePostgres and Redis readyWeb, desktop, mobile shells
# launch-room
# launch-room83 messages, 11 files, 3 open decisions
Ada

The release checklist is ready. Zerg found one blocker in the huddle notes.

thread open - 3 replies - launch-plan.pdf
Mina

Can we pull the owner list from the customer-zero thread before the update goes out?

mentioned you - due today
ZZergScoped to 5 visible rooms

Found 3 owners, 2 unresolved launch tasks, and drafted a customer-ready release note with source links.

S1 #launch-roomS2 #engineeringS3 Ada DM
Ask Zerg or message #launch-room
40+API routes for chat, admin, files, notifications, and workflows
22normalized Postgres tables behind workspace state
12+realtime event types for live rooms and activity
1Nuxt app staged for web, desktop, and mobile pilots

Product

The collaboration surface teams expect, with context the agent can actually use.

The workspace behaves like a real team chat product: public and private channels, DMs, threads, reactions, read state, message formatting, saved items, pins, files, activity inbox, command palette, and Slack-style search.

Messaging

Rooms, threads, and searchable decisions

Channels, direct messages, replies, reactions, drafts, permalinks, saved items, pins, and filters like from:, in:, has:file, and is:pinned.

Files and huddles

The work stays attached to the conversation

Access-controlled attachments, room-bound downloads, LiveKit huddle wiring, transcript primitives, canvases, lists, and media permission hooks.

Activity

Inbox, reminders, and notifications

Mentions, DMs, reactions, thread replies, unread channels, Zerg replies, scheduled messages, personal reminders, DND, and email fallback plumbing.

Zerg agent

AI help without dumping the whole company into a prompt.

Zerg works from a scoped chat snapshot. Private rooms the member cannot access never enter context, and every answer can show the source rooms that shaped it.

01Visible workspace context

Channels, DMs, files, and threads are filtered by membership before the agent sees them.

02Useful actions

Summaries, action items, search, launch updates, and reply drafts happen where the work lives.

03Traceable output

Source labels make it clear which rooms and messages contributed to each run.

Operations

Pilot controls are first-class, not an afterthought.

Workspace owners can manage users, invites, domain rules, channel settings, audit activity, sessions, retention, files, API tokens, webhooks, bots, and Slack bridges.

Admin and security

  • Member lifecycle, invite revoke, domain join rules
  • Private-room membership enforcement
  • Audit export, sessions, retention, file tools

Production foundation

  • Postgres persistence with row-level mutations
  • Redis fanout for multi-instance SSE
  • Health checks, structured logs, metrics endpoint

Extension path

  • Incoming and outgoing webhooks
  • OAuth app and bot primitives
  • Workflow triggers for messages, reactions, schedules

Deploy

Runs on the web today. Native shells are ready for serious pilots.

WebNuxt server on Fly with health checks and hosted downloads.
DesktopTauri notification, deep-link, updater, and huddle permission wiring.
MobileiOS and Android scaffolds with universal link endpoints ready for signing.

Launch workspace

Bring your team into the room where the agent can help.