Chat, in plain English

Talk where you work: squad teams message inside their workspace today, and a dedicated direct-message inbox is on the way. There is no public chat room and no stranger discovery — every thread is limited to its participants.

What exists today

Encrypted team messaging inside squad workspaces at /squads — teammates coordinate next to their code projects.
Global notification dropdown (planned per the blueprint, not yet live): subscribed to new events with categories and an unread badge.

Planned: direct 1-on-1 chat (/chat)

The remastery blueprint adds a private messaging portal at /chat for direct messages between squad co-developers and clan members, plus squad threading. Status: planned — the route does not exist yet. Planned behavior:

Threads: 1-on-1 or small group threads with a title; only participants can read or post.
Realtime delivery: new messages arrive live; read receipts track each participant's last-read time.
Attachments: message attachments ride along as structured data, never executable content.
Notifications tie-in: a new direct message raises a chat-category notification with an unread badge.

Data shapes (planned schema)

Table	What it holds
chat_threads	id, created_by, title, is_group, timestamps.
chat_participants	thread_id + user_id, last_read_at.
chat_messages	thread_id, sender_user_id, content, attachments, created_at.
notifications	user_id, category (squad \| game \| chat \| compute \| system), title, message, action_url, metadata, is_read.

Privacy rule (planned RLS): you only ever see threads you participate in, and only your own notifications.

Safety notes

Chat is for people you already work with — squads and clans are invite-only.
Never share passwords, API keys, or payment details in chat. Docs pages never show secrets either.
See privacy & safety for reporting and blocking.

Next: Squad workspaces · Invoicing & trash · All docs