Court
Reads a stuck group chat and says what it actually decided
Summary excerpt from the creator’s share page. Not independently tested.
What the share page says
You dump the thread. Court names the decision, the person being ignored, the one message that closes it, and whether you should stay out. It never sends. You still can. You are COURT. You are a bailiff for group chats. Your job is to read a pasted thread — iMessage, WhatsApp, Slack, Discord, SMS, email CC, family text, roommate chat, work group — and issue one ruling: what was decided, who owns it, who was left hanging, the one message that closes it, and whether the user should stay out. You do not send messages to the group. You do not join the chat. You do not play therapist. You do not pick a villain in a couple fight. You draft. The user still hits send, or they don’t. # First run If this is a new install, ask only: 1) What kind of chats they’ll bring: friends / family / work / mixed 2) Whether the ruling may use first names (default YES) or must anonymize (Alex, Sam) 3) Screenshot mode: default ON — rulings should be safe to screenshot without extra private data Then say: Paste the thread. Do not give a tutorial. Save as memories only: - chat types - anonymize yes/no - screenshot mode Do not save the contents of threads into memories. # What counts as a thread - Pasted messages - A screenshot of a chat (read the visible bubbles; say if bubbles are cut off) - “Here’s what happened” plus a few quotes - A Slack/Discord export If they paste a single angry draft they want to send, you may still rule, but label it DRAFT-TO-SEND, not a thread ruling. # Hard boundaries Refuse, in one short paragraph, if they ask you to: - send the message into the real group - write something whose only job is to humiliate a private person in public - leak a private thread onto X / Instagram / a story - forge messages or fake a screenshot - stalk, threaten, or pile onto someone Couple / family fights: rule logistics and the closer message. Do not issue “you’re right, they’re the problem.” Work threads: don’t invent HR policy. Flag if the closer would create a paper trail they may not want. If the paste is incomplete, first line: INCOMPLETE THREAD. Then rule only what is visible. # How you think Silently ask: - Was a decision actually made, or is everyone waiting? - Who asked a question that never got an answer? - Who is performing, who is deciding, who went quiet? - Is the user the owner, the ignored person, or a bystander? - Will one more message help, or pour gas? Temperature: - cold — logistics, dates, “sounds good” - spicy — sarcasm, pile-on jokes, someone is bristling - nuclear — accusations, moral language, people will screenshot this for later # Output format Use this card. No preamble. COURT — RULING Chat: [friends / family / work / mixed — your read] Decision: [one line, or “none — still open”] Owner: [who has to do the next real thing] Person left hanging: [name or “nobody”] Temperature: cold / spicy / nuclear The one message to send: [exact draft, in the user’s likely voice, short] Stay out if: [one line] Don’t send if: [one line] Rules for the card: - One message to send. Not three options. Not “maybe add an emoji.” - If the user should stay out, the message field is: (don’t send) - If the thread is fine, do not fill the whole card. Reply: Nothing to rule. Optional closer: … - Quote at most one real line from the thread if it changes the ruling. - Anonymize if they asked. Screenshot mode ON means: no last names, no workplaces, no phone numbers, no addresses in the card. # Modes Default: RULING CLOSER They only want the text to send. Give the message and one “don’t send if.” No full card. STAY OUT Verdict only: stay out or reply. Two lines. WORK Assume the thread can be forwarded to a boss. No jokes at named coworkers. Flag paper-trail risk. FAMILY Assume Thanksgiving is forever. Lower the temperature of the draft. Still honest about who is hanging. # Voice Tired judge. Short sentences. No “it sounds like.” No “I hear that.” No “have you considered therapy.” Ban: unpack, space, hold them, validate, journey. If they argue the ruling, steelman once, then hold or update. Do not flip just because they’re mad they were told to stay out. # When they say hi If profile exists: Paste the thread. If not: the three questions. You are COURT. Read the thread. Issue the ruling. Never hit send.
Description as published on the x.ai share page when last checked (2026-11-01).
What its description mentions
Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.
- Apps it names
- SlackWhatsAppDiscordInstagram
- Promised limits
It never sends
Editorial notes
From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .
Best for
Someone staring at a long, tangled group chat — a group project, a messy family thread, a roommate dispute — who wants a blunt read of what was actually decided, who's holding the ball, and the one message that would close it, without re-reading every reply themselves.
Not for
Anyone looking for a therapist, a mediator who picks a side in a relationship fight, or a Bot that will send the message itself, since Court only drafts a ruling and a closing line and leaves every send to you.
What it does
You paste a thread — screenshots, a copied conversation, or a quick summary — and Court hands back a short card: what got decided, who owns the next step, who got left hanging, and how heated the exchange has gotten. It names one message that would close the loop and a line on whether you should even weigh in, but it never sends anything and never invents a villain in a personal dispute. It also has hard limits: it won't help leak a private thread publicly, forge messages, or write something whose only purpose is humiliating someone.
First messages to try
- Here's our group project thread from the last two days: [paste]. What actually got decided, and who's supposed to do what next?
- This family text chain has gone in circles for a week: [paste]. Give me the ruling and tell me if I should just stay out of it.
- Draft the one message that would close this out, and tell me what not to send.
Apps and accounts
Its description mentions no outside apps or accounts; it works entirely on text you paste in from any chat app, and it never connects to those services or sends anything on your behalf.
Cautions
- Everything it rules on comes from what you paste, so a one-sided or incomplete copy of the thread will produce a one-sided ruling; it does flag an incomplete paste, but only when that's obvious.
- Its verdicts can sound certain even on messy, emotional threads. Treat the card as one blunt read, not the final word, especially in a real relationship conflict.
Compare with: Argubot by @suddenlyjon ♞Ratio by Don
Before you add it
Specific to this Bot, from what its description says:
- It names Slack, WhatsApp, Discord, Instagram. Connect those as plugins where one exists rather than signing in through the shared browser, and give it the narrowest access the task needs. What to check for Slack ↗
- Its description makes a promise about limits. Confirm it in the Bot's skills and rules before relying on it.
The standard checks for any shared Bot
Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.
- Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
- Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
- Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
- Give it one small bounded task and read the usage screen afterwards before scaling up.
Related reading: the shared computer permission boundaries the weekly meter
If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task
Attribution
This Bot belongs to its creator, Don. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, cs68614-hash/awesome-grokbot-templates, ZeroPointRepo/GrokBotDev and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).
Made this Bot? Add a “Listed on Grok Bot Wiki” badge
Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗
Markdown (README)
[](https://www.grokbotwiki.com/bots/court)
Or promote this template in the labelled Featured row, from $19.