Grok Bot for Law Firms
xAI's Grok Bot can sign into your apps and work around the clock. Here is where it helps a law firm, and what to check before it touches client work.
Grok Bot is a capable always-on assistant for a person's own work at a law firm: research, inbox and calendar, follow-ups, and one-off tasks the person checks. For repeated client work like matter intake, conflicts, filing, and billing, it plans each run fresh and keeps records per user, so most law firms will want a verifiable agent for that work and keep Grok Bot for the rest.
This fall, three AI companies shipped the same idea within weeks: an agent with its own computer that works for you around the clock. xAI launched Grok Bot in August, Meta launched Muse in September, and OpenAI answered with dots at the end of the month. Operations teams at law firms are already asking whether one of them can take work off their plate.
This guide is for that question. It covers what xAI's Grok Bot is, where it fits at a law firm, and the five things the firm has to answer before an always-on agent touches repeated client work. Every product fact comes from xAI and Cursor's own pages as of October 1, 2026, and these products are changing fast.
What is Grok Bot?
Grok Bot is xAI's always-on agent, launched in beta on August 11, 2026 and built and run with Cursor. Each user gets a persistent cloud computer with a browser, a filesystem, and a terminal. You create named Bots, give each one a job, connect them to apps like Gmail, Slack, and Notion, and they work on a schedule or when an event fires, coming back to you when they need approval.
Bots can message each other, hand work off, and run as a team, with a chief-of-staff Bot managing specialists. Since September, Grok Bot for Enterprise adds access, network, and audit controls, and Team Bots let a group share Bots.
Grok Bot is good at the work around a person: watching an inbox, prepping for meetings, researching a company, pulling numbers from a dashboard, and handing tasks between Bots without anyone writing code.
- Plans. Included with SuperGrok, Cursor Pro, and Cursor Teams. x.ai lists $20 a month (Cursor Pro), $30 (SuperGrok), and $40 per seat (Standard Teams), with Bot usage metered separately. Enterprise is through sales.
- Model. Cursor manages model selection. There is no customer-facing model picker.
- Saved work. "Teach a task" turns a recorded demonstration of up to 10 minutes into a draft skill, a reusable set of instructions. Routines run a skill on a schedule or after an event.
- Approvals. Allow once, Always allow, or Deny, plus Auto Review, a separate model that checks risky actions before they run.
- Records. Audit logs and Action Recording are Enterprise features. Action Recording is off by default and keeps 90 days.
- Certifications. ISO/IEC 27001 and ISO/IEC 42001 (Anysphere), with Grok Bot in scope.
Product details as of October 1, 2026, from the vendor's own announcement, help, and security pages.
Where law firms want to use Grok Bot
Nobody at a law firm needs an agent to do the professional judgment. They want back the hours their teams spend on repeated, system-to-system work:
- Matter intake and conflicts. Reading the intake form, running the conflict search in Intapp, and opening the matter.
- Document filing. Profiling and filing email and documents into iManage or NetDocuments by the firm's conventions.
- Time and prebill review. Chasing missing time, applying outside counsel guidelines, and preparing prebills in Aderant or Elite 3E.
- Docketing. Pulling dates out of orders and emails and getting them onto the right calendars.
- Inbox triage. Sorting shared mailboxes into new matters, client questions, and court notices, and routing each one.
Picture an intake coordinator teaching a Bot the new-matter process: record ten minutes of reading the intake email, searching Intapp for the parties, and opening the matter. Grok Bot turns that into a draft skill and a routine that fires on each new intake email. On a quiet week it may handle every one correctly.
The question for the firm is what happens on the email that does not look like the demo: a second client entity, a party spelled two ways, a related matter already open. The skill is guidance the model applies on that run, so the Bot decides how to handle the edge case then and there, and the record of that decision lives in the coordinator's conversation unless the firm is on Enterprise with Action Recording turned on.
Five questions before Grok Bot touches client work
None of these are reasons to avoid Grok Bot. They are the questions any law firm has to answer for any agent that acts on a client's behalf.
Will Grok Bot do the work the same way every time?
Grok Bot's skills are the closest any of the new always-on agents comes to a saved workflow, and they are a real step. But a skill is a set of instructions the model carries out on each run, not fixed steps. xAI's own docs say to re-test a skill after a website, plugin, or source format changes, and make no claim that two runs take the same path.
For matter intake, conflicts, filing, and billing, that matters. You cannot test a procedure on last month's cases and rely on the result if the next run is planned again from scratch.
Who supervises Grok Bot at a law firm?
Grok Bot acts as the signed-in member, so every action traces to a named person. That is the right foundation. Approvals are Allow once, Always allow, or Deny, and Auto Review checks risky actions first. The docs are candid that Auto Review does not cover every side effect, naming memory writes and most settings changes. Below Enterprise, each member sets their own rules.
ABA Model Rule 5.3 requires lawyers with supervisory authority to make reasonable efforts to ensure that nonlawyer assistance is compatible with their professional obligations, and ABA Formal Opinion 512 (July 2024) applies the supervision rules to generative AI tools. A supervising partner needs something to supervise: a procedure they can review and a record of how it ran.
Can the firm show what Grok Bot did?
The firm-level record lives on Enterprise: audit logs of admin and control-plane events that can stream to a SIEM, and Action Recording of what Bots actually did, which is off by default and kept for 90 days. Self-serve Teams do not get the audit log.
When a client, an auditor, or opposing counsel asks how a document was filed or why a matter opened without a flagged conflict, the firm needs an answer tied to the specific transaction, not a reconstruction from an agent's chat history.
What happens to client data?
With Privacy Mode on, customer data is not used for training, and Cursor's zero-retention provider terms apply, though flagged data may be stored for investigation. Bot computers run in the United States, there is no per-organization retention policy yet, and all of one user's Bots share the same files and app logins.
Rule 1.6(c) asks lawyers to make reasonable efforts to prevent unauthorized disclosure of client information. An agent with a user's email, files, and app logins is inside that duty.
Cursor's security docs say its controls "reduce, but don't eliminate" risk from malicious content.
Does Grok Bot reach the systems law firms run on?
Named plugins include Gmail, Slack, Notion, Salesforce, and GitHub. For everything else, Bots use computer use, clicking through web apps the way a person would.
Most law firm operations run through Intapp, iManage or NetDocuments, Aderant or Elite 3E, and Outlook, often with portals and desktop software that do not have friendly APIs. Reaching a system is only half of it; the other half is doing the same thing in it every time.
| Grok Bot | Caddi | |
|---|---|---|
| How the work is defined | A skill: instructions the model follows each run | Tested code you can read and change |
| Same input, same path? | Not claimed by the vendor | Yes, for the coded steps |
| Role of AI in a run | Plans and performs each step | Named judgment steps, scoped and logged |
| Human control | Allow once / Always allow / Deny, plus Auto Review | Review the procedure; exceptions go to a named person |
| Record of each run | Enterprise audit log; Action Recording off by default, 90 days | Every run logged, tied to its source documents |
| Built for | A person's own varied work | Law firms' repeated back-office workflows |
What a verifiable agent does differently
The fix is not a better prompt or a stricter approval setting. It is moving the procedure out of the model. A hybrid agent runs the workflow as code, which can be read, tested, and versioned, and calls AI only for the steps that need judgment, each one scoped and logged.
For matter intake, that means the code reads the intake email, runs the conflict search, opens the matter, and files the engagement letter the same way every time, while AI handles the judgment inside it: is this email a new matter, which party name on the form is the client, does this hit look like a real conflict. Uncertain calls go to the intake team, logged.
That split is what makes an agent verifiable: a reviewer can read the procedure before it runs, every judgment call is on the record, and changes are made on purpose.
More on the idea in what are verifiable AI agents and what are hybrid agents.
Connect Intapp to Caddi
Allow1Sign in to your tools
One click each for Intapp, iManage and Microsoft Outlook. No API keys.
Automate matter intake.
ScreenshareType it2Show or tell it
Screenshare the job, or type it in chat. Change it any time.
- Running
14 done1 for review
3Watch it run
Caddi does the work and flags anything unsure for review.
How law firms can use both
Grok Bot and a verifiable agent are not competing for the same job. Let people use Grok Bot for the work around them, where every task is different and the person who asked checks the result.
Put the repeated client work, matter intake, conflicts, filing, and billing, on an agent the firm can verify. That is what Caddi builds: an ops person shows Caddi the workflow on a screen share or describes it in chat, Caddi runs it as code across the firm's tools with the judgment steps logged, and the team changes it in plain English as the work changes. Across Caddi customers, 99% of agent runs complete successfully.
Keep reading
- What are verifiable AI agents?
- Grok Bot vs. Muse vs. Dots for professional services firms
- Grok Bot for RIAs
- Grok Bot for professional services
- Meta Muse for law firms
- OpenAI Dots for law firms
- Caddi for law firms
- Client intake automation
- Conflict check automation
- Caddi + iManage
- AI for the law firm COO
- What are hybrid agents?
Caddi
See how Caddi AI Agents can run your firm's back office the same way every time and log every run for review
Frequently asked questions
Is Grok Bot safe for law firms?
Grok Bot has real safeguards: allow once / Always allow / Deny, plus Auto Review. For a person's own work, those are sensible. For repeated client work, a law firm also has to answer for supervision, records, and confidentiality, and Grok Bot plans each run fresh with records kept per user. Most firms will keep it for personal work and use a verifiable agent for client workflows.
Can Grok Bot run matter intake, conflicts, filing, and billing unattended?
It can attempt it: Grok Bot works in the background and can reach many apps. But it decides how to handle each case on that run, and the vendor does not claim repeatable runs, so the firm cannot test the procedure once and rely on it. For unattended client work, a verifiable agent that runs the steps as code is the safer fit.
Does Grok Bot keep an audit trail?
The firm-level record lives on Enterprise: audit logs of admin and control-plane events that can stream to a SIEM, and Action Recording of what Bots actually did, which is off by default and kept for 90 days. Self-serve Teams do not get the audit log. For law firms, check whether that record can be exported, retained, and reviewed at the firm level before relying on it.
Does Grok Bot train on our data?
With Privacy Mode on, customer data is not used for training, and Cursor's zero-retention provider terms apply, though flagged data may be stored for investigation. Bot computers run in the United States, there is no per-organization retention policy yet, and all of one user's Bots share the same files and app logins.
What should a law firm use for repeated client work?
A verifiable agent: one whose procedure you can read, whose judgment steps are logged, and whose every run leaves a record. Caddi builds these for law firms. Your team shows the workflow on a screen share or describes it in chat, and Caddi runs it as code across your tools, with exceptions routed to a named person.