cricket

channels are the rooms your team talks in. one per job, location, or department — whatever matches how the team actually works.

the basic move. type, send, the team gets a notification. unread badges keep you honest about what you've seen.

the team mentioned something three weeks ago and now you need it. cricket loads older messages on demand and the active channels stay near the top.

channels are for context. dms are for one-offs. the wrong choice clutters everyone's notifications or buries something the team needs.

you don't invite people to cricket directly — they join automatically when you add them in cypress. one place to manage the team, no separate sign-up.

cricket's three-pane layout puts channels on the left, the active conversation in the middle. click any channel to switch — your spot in each one is remembered separately.

every channel with new messages shows a badge with the count. cricket tracks per-user lastRead per channel, so the badges reflect what you specifically haven't seen.

the message box sits at the bottom of the active channel. type, send, the team gets it within ~4 seconds (cricket polls the server, no websockets yet).

cricket's phase 1 is text-only and polled. real-time delivery (websockets / sse), @mentions, threaded replies, file uploads, and emoji reactions are roadmapped, not yet shipped.

channels can't be deleted or archived from the ui yet — once you create one, it sticks around. ships in the next cricket drop.