Key Takeaways
- Grok Bot is a personal squad of agents on your own machine. xAI announced it on 2026-08-11 as "AI teammates you can give real work to", in early beta, downloadable for macOS and available on iOS, with enterprise access behind a waitlist (x.ai).
- Viktor is one AI employee inside the chat your team already uses. Slack and Microsoft Teams, in channels and threads, connected to 3,200+ integrations with real read and write access.
- They genuinely win at different things. Grok Bot's Bots have a computer of their own in the cloud and sign into tools even where there is no clean API or MCP, per xAI's own launch post. That covers software an integration list will never reach.
- The split that matters is where the work lives. A desktop app makes each person's agents theirs. A channel makes one AI employee's work visible to everyone who depends on it.
- Ask who reviews the output. xAI's page quotes early users trusting Bots to run workflows unsupervised. Viktor's default is a draft for your approval on anything customer-facing.
- Pick by shape of team, not by demo. Solo operators and heavy multitaskers will like a parallel squad. Teams where three people touch the same account want shared context and one accountable thread.
Your head of sales asks a question in the deal channel on Thursday: did we ever send Meridian the security doc? Somebody knows. Or somebody's agent knows, on their laptop, in a thread nobody else can open.
That is the real fork in the AI-employee market right now, and it got much sharper on 2026-08-11 when xAI launched Grok Bot. Two credible answers to the same problem, built on opposite assumptions about where work belongs.
This is a fair look at both. Grok Bot facts here come from xAI's own launch post and product page, read on 2026-08-13, and nothing about it is guessed.
What is Grok Bot?
Grok Bot is xAI's team of always-on agents that have their own computer, sign into the tools you use, and keep working while you are away. xAI describes them as AI teammates you message like a colleague and hand off work to, and says Bots come back when something needs your approval (x.ai).
Four things stand out from the launch, all in xAI's words:
- Bots have a computer of their own in the cloud, so they can work across apps, tools, and websites, including platforms with no clean API or MCP.
- You can run many Bots at once, including one that manages the others, and they can pass work between themselves in a shared thread.
- You can show a Bot how a job is done by asking it to follow along while you do it once. It saves the workflow as a routine and runs it next time.
- It ships as a macOS download and on iOS, in early beta, with an enterprise waitlist.
That is a real product with a real thesis: give one person a small squad, on their own machine, that can drive any interface a human can drive.
What is Viktor?
Viktor is an AI employee that lives in Slack and Microsoft Teams, where he reads the channel context and does the work in your actual tools. You @mention him the way you would message a colleague, he connects to 3,200+ integrations with genuine read and write access, and he runs on a persistent cloud computer with a shell, a file system, and the ability to produce real deliverables: PDFs, spreadsheets, decks, dashboards, code PRs.
There is no separate app to open and no per-person install. The pull request he opened, the invoice chase he ran, the report he built are all in the channel where the team was already talking about them, with the request that triggered them sitting right above.
How do Viktor and Grok Bot compare on real work?
Same jobs, different shape of answer.
| Actual job | Grok Bot | Viktor |
|---|---|---|
| Update the CRM after a call and draft the follow-up | xAI describes exactly this internally: a sales Bot writing transcript notes into the CRM and drafting follow-ups | Same job, run in the deal channel, so the AE and the CSM both see the note and the draft |
| Work in software with no API or MCP | Strong fit, and xAI names it directly: Bots sign in and drive the interface | Handled by connecting one of 3,200+ integrations, or by scripting against the tool's own API |
| Answer "what did we tell this customer in June" | Lives with whoever owns that Bot | Answered from the channel history the whole team can see |
| Give the team one recurring report every Monday | A routine on one person's Bot | A recurring task posting into the channel, editable by anyone on the team |
| Approve something customer-facing before it sends | xAI says Bots come back when approval is needed | Review-first by default: a draft in the thread you approve or edit |
| Onboard a fifth person into the same workflow | They set up their own Bots and routines | They join the channel |
Notice the pattern. On single-operator throughput, xAI's design is genuinely ambitious. On "three people share one job", a channel wins by construction, because the work and the record of the work are the same object.
Where does Grok Bot win?
Honestly, in three places.
1. Interfaces nobody integrates with. A Bot signing into a tool and clicking through it can reach the ancient inventory system, the regional bank portal, the vendor dashboard with no API. xAI states this plainly in the launch post, and it is the strongest argument for their approach. Integration breadth is wide but never infinite.
2. Parallelism as the default mental model. Grok Bot is built around running several Bots at once with one coordinating the rest. If your day is genuinely eight parallel lanes, that framing fits how you already think.
3. Learning by watching. Asking an agent to follow along while you do a job once, then having it saved as a routine, is a lower-effort way to transfer a messy process than writing instructions for it.
If you are a solo operator, a founder before the first ops hire, or someone whose work sits in interfaces nobody has integrated, take Grok Bot seriously.
Where does Viktor win?
Shared context, and everything downstream of it. Team knowledge does not live in one person's app. The reason someone paused that campaign, the number quoted to that customer, the exception made last quarter: those sit in channels. An AI employee reading that context answers questions a fresh agent cannot, and his answer lands where the rest of the team can check it.
Three specifics that follow from being in the chat:
- Nothing to install per person. Adding Viktor to a workspace is one action, not one action per laptop. Fifteen people get the same teammate with the same memory instead of fifteen private setups.
- Handoffs stay intact. When work moves between two people, the AI employee is already in the thread. Nobody re-explains an account to a new agent. See how a team shares one AI employee without chaos.
- The audit trail is the conversation. Who asked, what was returned, who approved: readable months later without an export. That matters for security due diligence, where Viktor maintains SOC 2 Type I and is hosted by default.
Then there is review posture. xAI's page quotes an early user saying they trust a Bot to run a workflow "forever" without verifying or reviewing. That is their user's experience, honestly reported, and for some internal jobs it is the right setting. Our default is the opposite: customer-facing, financial, and public work stays a draft until a person approves it, and internal reversible work graduates over time. The framework we use is in when to let your AI employee act without review.
How should you choose between them?
Four questions, answered in order. The first one usually settles it.
- How many people need the output? One person, a desktop squad is fine. Three or more touching the same accounts, put the AI employee where they already talk.
- Where does the work actually happen? If your critical systems have no API, browser-driving matters a lot. If they are Stripe, HubSpot, Linear, Notion, Google Ads, an integration with real write access is steadier than clicking through a UI.
- What breaks if the output is wrong? Customer-facing and financial work needs review-first as a default, not as a setting you remember to switch on.
- Who owns the process a year from now? Routines saved on one laptop leave when that person does. Procedures saved in the team's workspace do not. That is the argument for turning a recurring task into a shared skill.
A useful test before committing to either: give both the same two-request trial. One request that needs context from a conversation you had last week, and one that has to write into a real system. That tells you more than any demo.
Pull every open deal in HubSpot with no activity in 14 days, cross-check what we last promised each one in this channel, and post a table with the owner, the last promise, and a suggested next step. Draft the three follow-up emails, do not send them.Getting the category question right
There is a broader framing worth keeping. The market is splitting into agents that follow one person around, and teammates that sit where a team works. Both will exist for years. Kris's own framing on it is in how to judge an AI teammate that works everywhere, and the closest comparison to today's post is Viktor vs Claude Cowork.
What xAI got right, and stated better than most, is that the gap between 90% done and 100% done is the whole game: work has to land in the real tool. We agree completely. Our answer is that it should land there in front of the people who depend on it.
Frequently Asked Questions
What is Grok Bot?
Grok Bot is xAI's agent product, announced on 2026-08-11. Bots have a computer of their own in the cloud, sign into your tools, work across apps and websites, and come back when they need your approval. It is in early beta, downloadable for macOS and available on iOS, with a waitlist for enterprise access (x.ai).
How is Viktor different from Grok Bot?
Viktor works inside Slack and Microsoft Teams instead of a separate desktop app, so his work and the conversation that triggered it live in the same place. Grok Bot gives each person their own squad of Bots on their own machine. Shared team context versus personal parallel throughput.
Can Grok Bot work in tools that have no API?
Yes, and xAI names it as a core capability: Bots sign in and use apps and websites the way a person does, including platforms with no clean API or MCP. If that describes your critical systems, it is a genuine advantage.
Does Viktor need a separate app?
No. Viktor lives in Slack and Microsoft Teams. You add him to a workspace once and the whole team messages him in channels, threads, or DMs, with no per-person install.
Which one is better for a team of ten?
For ten people sharing accounts, projects, and handoffs, an AI employee in the team chat usually fits better, because everyone can see the request, the output, and the approval. A per-person desktop squad suits ten independent operators more than ten collaborators.
Do both keep a human in the loop?
Both support approvals. The difference is the default. xAI describes Bots that finish jobs and return when approval is needed, and quotes users who let them run unsupervised. Viktor's default is review-first on anything customer-facing, financial, or public, which you can loosen deliberately.
Can I try both at once?
Yes, and you should. Run the same two requests through each: one that needs last week's conversation as context, one that has to write into a live system. Compare what came back and how easy it was for a colleague to check.
Where do I read the source facts about Grok Bot?
xAI's launch post at x.ai/news/introducing-grok-bot and its product page. Every Grok Bot claim in this post comes from those pages, read on 2026-08-13.
