CEDX Chat · Workplace
Seventy-seven channels, 1,084 unread, and a daily recap that tells you what moved, what was decided and what is still open — per channel, with the thread id attached.
The recap does not summarise activity, it closes loops: cert rollback decided for one cohort, owner needed for the audit-trail backfill, runbook rewrite pinned. What moved, what was decided, what is open.
Runs on demo data. Channel names and people on screen belong to the demo workspace.
What it is
Every channel lists members, messages per day and unread — the deploy firehose runs 340 messages a day with 96 unread, and the list says so. Public, private invite-only and shared external channels are distinct kinds, and archived channels stop pretending they are alive.
120 conversations — 82 one-to-one, 38 group — with 52 waiting on a reply from your side. Previews, unread counts and message totals per row, so the direct messages stop being where requests go to be forgotten.
320 threads with a status each: open, following, resolved, stale. The unanswered-question tab sits at 90 — questions someone asked that nobody answered, collected in one place instead of scrolling away.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/chat.
01 — Overview
“Today in your channels” reads like a colleague who was paying attention: the SSO loop after the identity-provider rotation, the invoice export stuck at 92%, the on-call runbook that needs rewriting, quiet hours piloted on the deploy firehose. Each with its open question and thread id.
02 — Channels
77 live channels ranked by the numbers that matter: the random channel at 210 messages a day and a noise score of 61, the infra-wins channel at 184 with 85 unread. You can see which channels are conversation and which are weather.
03 — DMs
Direct messages hold half the company's actual requests — “Still blocked on our side”, “Link in thread please”, “Can we pin this?”. The list gives them the same needs-reply discipline as any ticket queue.
04 — Threads
TR-1509 has 38 replies and is still open; TR-1506 has 24 and has gone stale; TR-1502 was resolved in 2. The table makes thread state a thing you can filter, not a thing you infer.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Works from the recap during an incident: what moved, what was decided, who owns the backfill. The audit trail is the thread itself.
recap · per channel
Watches the knowledge gaps. Eighteen unanswered questions on mobile enrolment steps at an 11% answer rate is a docs task, and now it has an owner.
open gaps · 15
Lives in the shared support channels and the unanswered-question tab. Ninety open questions is the morning's list, not the quarter's surprise.
unanswered Q · 90The shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
Work starts in a channel or a DM. Channels carry their message rate and unread count with them from the first message.
Replies attach to roots — thread density sits at 99% — so a decision has one home instead of twelve fragments.
The daily recap reads the threads and writes down what moved, what was decided and what is open, per channel, every day.
Questions that nobody answered collect in the unanswered tab; stale threads show as stale. Loops close because the open ones are visible.
One record
Channels are not a parallel universe. They reference the same invoices, incidents, documents and meetings the rest of the estate holds.
Threads that start as email stay the same record when the conversation moves to a channel.
CEDX DocsThe runbook the recap says to rewrite lives in Docs — and Docs search cites team chat as a source.
CEDX MeetThe standup channel and the standup meeting share a record; decisions land in both.
CEDX CopilotAsk AI — ⌘J — sits on every one of these screens, grounded in the same record.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your channels, your history
Chat with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/chat. It runs on demo data — the channels, threads and people belong to a demo workspace, not to a customer.
A per-channel digest on the overview titled “Today in your channels”. It lists what moved, what was decided and what is still open — in the demo view: a cert rollback scoped to one cohort, an export stuck at 92%, a runbook rewrite — each with its thread id attached so you can check it.
A per-channel figure computed from message volume and threading. The noisiest channel in the demo workspace scores 61 at 210 messages a day with only 12% threaded; the fleet-wide figure is 36 against a target of 45, and zero channels sit above the 70 line.
As a tab on the threads view — 90 in the demo workspace — and as knowledge-gap alerts on the overview. The top gap right now is mobile enrolment steps: 18 unanswered questions, an 11% answer rate.
Yes. Shared channels are a distinct kind, flagged ext in the channels list, with their own member counts and message rates — the shared support channel runs 170 messages a day in the demo view.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Then count the unanswered questions in your own channels.