Grok Bot gives each person Bots that share one cloud computer, can run commands on your own computer when your policy allows, and adds SCIM and SIEM export on Enterprise. Tulsk is a team workspace of named agents, and Tulsk for Mac lets chat work in the folders you share, with every command sandboxed.
you want named agents with their own grants inside a shared workspace, and chat that works on your Mac only in the folders you share, with sandboxed commands and a card for every change.
Pick Grok Bot if
you need SCIM, SIEM audit export and enforced admin policy today, or apps for Windows, Linux and Android as well as the Mac.
They differ most on
Grok Bot leads on enterprise controls and platforms; Tulsk leads on per-agent boundaries and on containing what runs on your Mac.
At a glance
The most differentiating dimensions first. Honest where they win, honest where we win.
Dimension
Tulsk
Grok Bot
Boundary between agents
Each named agent has its own tools and connection grants
A person’s Bots share one cloud computer; xAI says not to treat Bots as a security boundary
Commands on your computer
In folders you share: no internet, no reach outside the folder, no git writes, nothing left running
When the local execution policy allows; containment not documented
Local reach
Shared folders only: list, read, search, edit, write and run
Commands on your computer; file, app and screen access not documented
Approvals
A card with the exact change or full command: Allow once, Always in this folder, or Deny
Ask every time by default; Always allow, Allow once, Never, or Deny once
After reading outside content
"Always" switches off: every later change in that conversation asks first
Projects, tasks, approvals, and Slack, Telegram and WhatsApp channels, shared by members and agents
Team Rules, connector policy and shared templates on Teams and Enterprise
Cloud computer
One durable computer per workspace, shared by its agents and chat
One persistent cloud computer per person, shared by their Bots
Platforms
Mac app (macOS 13+) and the web; no Windows app
macOS, Windows, Linux, iOS/iPadOS and Android
Pricing
One plan per workspace, one shared work budget, no seats
Included with SuperGrok and Cursor plans, with its own usage; Enterprise through sales
Where they actually diverge
The differences that matter once you start using either tool.
Named agents, each with its own grants
Tulsk
In Tulsk every agent is named and configured on its own: tools, skills, schedules and connection grants. Writes to connected apps wait for approval unless the grant allows them, and approvals are workspace records you can resolve in chat.
All agents share one durable workspace computer for files and code, so the boundary between agents is their grants, not separate machines.
Grok Bot
Grok Bot gives each person Bots that share one persistent cloud computer. xAI’s own documentation says: "Do not use separate Bots as a security boundary." Teams and Enterprise add Team Rules, connector policy and shared templates.
Commands on your Mac, sandboxed
Tulsk
Tulsk runs commands on your Mac only in folders you share from the menu bar, and always in a sandbox: no internet, no reach outside the folder, no writes to git’s own files, and nothing left running after the command ends. If the sandbox cannot start, the command does not run.
Each change or command shows a card with the exact edit or the full command. "Always in this folder" switches off once a conversation has read the web, email or another agent’s reply, and ⌃⌥⌘. stops everything at once.
Grok Bot
Grok Bot runs commands on your own computer only when the Execution on Local Computer policy allows it. The default is Ask every time, the first request offers Always allow, Allow once, Never or Deny once, and a model-driven Auto-review layer can approve or hold actions under rules.
xAI’s documentation describes shell execution only; it does not describe a sandbox for those commands, or file, app and screen access on the local computer.
Where Grok Bot leads: enterprise controls
Tulsk
Tulsk Enterprise includes SSO/SAML and audit logs. Tulsk does not offer SCIM provisioning or SIEM export, and Mac actions have no admin policy settings yet.
Grok Bot
Grok Bot for Enterprise, launched 2026-09-03, adds SCIM 2.0, audit logs streamed to SIEM, OpenTelemetry export, sanitized Action Recording, network allowlists, enforced Auto-review and bulk terminate of member computers. If those are procurement requirements today, Grok Bot meets them and Tulsk does not.
Where Grok Bot leads: platforms
Tulsk
Tulsk for Mac runs on macOS 13 or later only. On any other computer, Tulsk works in the browser, without Mac actions or quick chat.
Grok Bot
Grok Bot lists macOS, Windows, Linux, iOS/iPadOS and Android. For a team split across platforms, that reach is a real advantage.
A workspace plan vs per-person plans
Tulsk
Tulsk is billed per workspace, with no seats. Chat, agent runs and the workspace computer draw on one shared work budget: Free with $2 of work once, Starter at $39/mo with $50 of work, Pro at $99/mo with $120. The Mac app costs nothing extra.
Grok Bot
Grok Bot is included with SuperGrok, SuperGrok Plus and Heavy, and Cursor Pro, Pro+, Ultra and Teams plans, with usage separate from those plans. Enterprise is priced through sales.
The fit test
Which one are you?
Pick Tulsk if you…
You want each agent to have its own tools and grants, not one shared computer as the boundary
Commands on your Mac should run sandboxed, only in folders you share, with a card for every change
Work should live in projects, tasks and approvals your team shares, with Slack, Telegram and WhatsApp
You want one workspace plan with one shared work budget and no seats
Both products' published plans. Last verified May 2026.
Tulsk
Cloud only
Free$0
$2 of work once per account, no card
Starter$39 / mo
$50 of agent work, up to 6 agents
Pro$99 / mo
$120 of agent work
EnterpriseCustom
Contact sales
Grok Bot
Local + Cloud
Included plansIncluded
SuperGrok, SuperGrok Plus and Heavy, and Cursor Pro, Pro+, Ultra and Teams; its own usage
EnterpriseCustom
Through sales
Working with both
Tulsk exposes a scoped MCP server for its projects and tasks. Check xAI’s documentation for whether Grok Bot can connect to it before planning a joint setup.
