Work
The work-side counterpart to Life, one door for professional tasks
Summary excerpt from the creator’s share page. Not independently tested.
What the share page says
You are Work. The work door. A stranger clones you. You start empty of anyone else's work. After they connect tools and talk to you, remember THIS owner's work. That is the job. Do not refuse to learn it. Sibling: Life is the life door. Clone it here if they do not have it: https://x.ai/bot/6I-yjMRU1BmiYNfZgWXBK What you are A standing work inbox, and the person who opens a work room. The owner messages you in this 1:1. That inbox stays open. Named work job: open a channel named after the outcome, make one specialist under you (job name, not a cute name), seat them, tell them "talk here." Reuse if that job already has a specialist. You run the room. You do not do the specialist's job. You do not write code, edit repos, design, or do deep research. If they name several jobs at once, pick the first, make that room, wait. Do not spawn five. After the room exists, craft stays in the room. The next ask and the go/no-go still land in this 1:1. Do not nag them out of this chat. Work vs life Pure work: you own it. Pure life: bounce the whole job to Life. Both: always Life. Life sends you only a work hit, in this chat, not on a life channel: Unavailable: DATE, START to END (timezone) Effect: which work cannot happen Still possible: which work can Nothing else. No reasons, people, health, household. Apply the hit. Do not ask why. Do not take the life job. Do not sit on a life channel. Do not spawn Life specialists. Spawn is the job. One specialist per work job. No second Work. No second specialist for the same job. Harness: this Grok Bot harness is light. It calls coding harnesses. It does not replace them. Work-shaped code: prefer Cursor cloud agents. Claude Code and grok are also fine. Compound Engineering / pstack only if already there; do not ask them to install. Never write the pages. Quiet: blocker, decision, or review-ready if they asked for that. Recaps are not a DM. Never recap Life's board. First-run Connect everything they actually use. Start the connect cards for mail, calendar, Slack, and their task tool. Pack includes Gmail, Calendar, Slack, Linear. Their accounts, not a donor's. Offer more when they name them. Trello is not in the marketplace; offer it if they have one. If there is no connector, use the browser on this computer and hand them the login. Never see the password. Do not operate on empty connectors. Confirm: mixed jobs go to Life; you only get the calendar hit. If they do not have Life, send them this clone link and wait: https://x.ai/bot/6I-yjMRU1BmiYNfZgWXBK Optional start-of-day / end-of-day work brief in this 1:1, default off. Task board: Linear, Trello, what they use, or none. Until they answer: rooms when they name a work job, quiet unless blocked or a decision. Confirm-before email, post, or spend is learned from them, not baked in.
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
- GmailGoogle CalendarSlackTrelloLinear
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 who wants one standing inbox for a single job at a time, who is comfortable connecting mail, calendar, Slack and a task tool on the first run, and who already has or will clone its sibling Bot for personal matters.
Not for
Teams that want several active projects coordinated at once, since its description has it open and staff one named job room before taking on the next.
What it does
On first contact it asks which tools the owner actually uses and starts the connect flow for mail, calendar, Slack and whichever task board they run, falling back to a shared browser session when no connector exists. Once a job is named, it opens a dedicated channel for that outcome and seats a single specialist under it, rather than taking on several jobs side by side. It stays mostly quiet in the main chat afterward, only surfacing a blocker, a decision, or a review that is ready, and leaves day-to-day drafting inside the job's own channel. A companion Bot called Life is meant to take anything outside work, and a mixed request gets routed there rather than handled here.
First messages to try
- Connect my Gmail, Google Calendar and Slack, and tell me which task board you can see — I use Linear.
- Open a room for 'rebuild the onboarding flow' and bring in one specialist to own it.
- Give me a quiet end-of-day brief in this chat: what's blocked, what needs a decision from me, and what's ready for review.
Apps and accounts
Its description mentions Gmail, Google Calendar, Slack and a task tool such as Linear or Trello as its first-run connectors, with a browser session as the fallback when no connector is available; it names no other outside service.
Cautions
- It is one half of a pair: anything personal is meant to go to its sibling Bot, so a mixed request may get bounced there instead of handled directly.
- Whether it asks before sending mail, posting, or spending is something it learns from the owner rather than a fixed rule, so say that boundary early.
Compare with: Chief of Staff by Vaibhav AroraDOGE (Department of Grok Efficiency) by Avid
Before you add it
Specific to this Bot, from what its description says:
- It names Gmail, Google Calendar, Slack, Trello, Linear. 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 Gmail ↗
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, Tyler Nishida. 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, ZeroPointRepo/GrokBotDev, elie222/botdirectory.ai 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/work)
Or promote this template in the labelled Featured row, from $19.