1. Bots2. Chat and collaboration3. Files and results4. Computer and apps5. Skills and routines6. Approvals, security, privacy7. Settings, notifications, platforms8. Teams and enterprise9. Where Buddy Bots wins (summary)10. Where they will stay ahead (honest)11. Unknowns to verify12. Build status โ€” v0.3 (20 Sep 2026)

Buddy Bots โ€” Grok Bot Parity Spec

Source: x.ai/bot, x.ai/news/introducing-grok-bot, docs.x.ai/grok-bot/* (read 20 Sep 2026). Grok Bot is in beta (launched 11 Aug 2026); features marked "rollout" are not available to all their users yet.

Rule: every row in "Grok Bot" must exist in Buddy Bots (parity). "Better" column is where we beat it. Phase: P1 = MVP on localhost, P2 = multi-bot + automation, P3 = apps/teams.

1. Bots

IDGrok BotBuddy Bots โ€” betterPhase
B1Bot = durable teammate: name, label, description (permanent rules), avatarSame + structured role fields (goal, tools allowed, approval boundary) instead of one free-text descriptionP1
B2Create via New / Cmd+N; auto-generate bot from a nameSame + generate from a one-line job descriptionP1
B38 templates: Sales Outbound, Talent Scout, Paid Media, Expense Manager, Product Performance, Bug Reproduction, Account Health, Chief of StaffSame 8 roles + template galleryP2
B4Edit profile, pin, hide/unhide (hidden bots keep running)SameP1
B5Duplicate (copies profile, settings, skills, routines, avatar; not history/memory/attachments)Same + optional "copy memory"P2
B6Share as template: public link or team-only; recipient gets a copy, never your computer/logins/historySame + export/import as JSON fileP3
B7Delete: removes profile, conversation, routines; shared files and logins remainSame + optional wipe of that bot's filesP1
B8No model picker โ€” xAI model onlyPer-bot model choice (Claude, GPT, DeepSeek, Gemini, Grok, local via Ollama) + per-bot cost capP1
B9Memory: stable preferences, role context, work summaries; per-bot; corrected by telling the botSame + visible, editable memory page per botP1

2. Chat and collaboration

IDGrok BotBuddy Bots โ€” betterPhase
C11:1 conversation per bot; paste text/links/images; attach filesSameP1
C2/ references a skill; @ mentions bots, groups, routines, connectorsSameP1
C3Reply in threads, emoji reactionsSameP2
C4Message while work is in progress; user messages pre-empt background work; "Stop now" halts (no undo)Same + per-task cancel buttonP1
C5Group chats of 2โ€“6 bots; editable name/members; bots decide who responds; @BotName, @everyoneSame, no hard cap of 6P2
C5a(not documented)Group speaking rule: a bot may post anything a good teammate would โ€” result, question, handoff, approval request, suggestion, warning, risk, advantage/disadvantage, disagreement, correction โ€” provided it adds new information or moves the work forward. Blocked: echo/agreement-only, restating another bot, social filler. Jev gates each candidate message ("adds value? yes/no"); plus turn cap, claim lock, per-conversation cost budget. Warnings and risks bypass the turn cap.P2
C6Async bot-to-bot handoff messages (text-only)Same + handoffs can carry filesP2
C7Hierarchies (chief-of-staff bot managing specialists)SameP2
C8Proactive pickup / follow-up on stalled workSameP2
C9Search across messages, bots, groups, files, links, routines; command paletteSameP2
C10Attention states: "Needs attention", "Unread activity", manual read/unreadSameP1
C11Draft auto-save per conversationSameP1

3. Files and results

IDGrok BotBuddy Bots โ€” betterPhase
F1Up to 6 attachments; 25 MB docs/images/audio, 200 MB videoSame limits or higher (local = no upload cost)P1
F2Types: images, audio, video, PDF, text, Word/Excel/PowerPoint, CSV, JSON, YAML, code, HTML, email files, JupyterSameP1โ€“P2
F3Outputs on request: documents, spreadsheets with formulas, slide decks with notes, folders of screenshots/logs, unsent draft messagesSameP2
F4Result cards for files, images, links, tool results; save / open source / give feedbackSameP1
F5Structured result: facts / assumptions / completed actions / pending approvals / open questionsSame, on by default for consequential tasksP2
F6Shared /workspace folder across botsSameP1

4. Computer and apps

IDGrok BotBuddy Bots โ€” betterPhase
K1One persistent cloud computer per account: browser, filesystem, terminal; keeps working when devices are offSame (Docker container on localhost first, cloud VM later)P1
K2All bots share one computer โ€” cookies, files, credentials; docs state bots are not a security boundaryOptional isolated browser profile per bot (a finance bot's logins are invisible to a sales bot)P2
K3Parallel bots, each with its own screen; one computer-use task per bot at a timeSameP2
K4"Agent Computer" live view: clicks, typing, navigation, statusSame + step timeline with screenshotsP1
K5Takeover for password/passkey, 2FA, CAPTCHA, payment, identity checkSameP1
K6Secure secret input (masked, kept out of transcript)Same + encrypted local vaultP1
K7Persistent logged-in browser sessionsSameP1
K8Connectors/plugins from a Marketplace, account-wide, enable/disableMCP-native: any MCP server works as a connectorP2
K9Computer use for sites with no connectorJev-first navigation (cheap/fast), vision-model fallback on BLOCKED/canvas/iframes; per-task cost and success loggedP1
K10Maintenance: Recover from snapshot, Update, ResetSame (volume snapshots)P2
K11Optional execution on the user's local computer: ask every time / always / neverSameP3
K12"Route egress through this desktop" (bot traffic exits from the user's own IP โ€” their answer to anti-bot blocking)Free on localhost; needed once cloud-hostedP3
K13Hardware security key (YubiKey) passthroughSameP3

5. Skills and routines

IDGrok BotBuddy Bots โ€” betterPhase
S1Skill = reusable instructions; shared private library across bots; "save this as a skill" after a taskSame; skills stored as plain markdown files (portable, versionable)P2
S2Teach a task: record one browser workflow (max 10 min, no audio) โ†’ draft skill to review (rollout)Same + recorded Jev action trace replays deterministically, LLM only when the page differsP2
S3Routine = one bot + workflow + schedule (timezone) or event triggerSameP2
S4Event triggers (Slack message, GitHub notification) with narrow match rulesSame + generic webhook + email triggerP2
S5Enable/pause, test run (does real work), edit, run history, deleteSame + dry-run mode (no write actions)P2
S6Limits: 50 routines per bot, 20 run records per routineNo cap; full historyP2
S7Auto-pause routines after long user absenceSameP2

6. Approvals, security, privacy

IDGrok BotBuddy Bots โ€” betterPhase
A1Approval card: Allow once / Deny / Always allowSameP1
A2Auto-review rules: "Ask first" and "Allow automatically"; Ask first wins on conflictSame; Jev classifies action risk in millisecondsP1
A3Default-gated actions: send, publish, pay, delete, permission changes, production changes, accepting legal termsSameP1
A4Bot pauses and notifies instead of bypassing security checksSameP1
A5Encryption in transit and at rest; training opt-outSelf-hosted option: data never leaves your machine; bring-your-own API keysP1
A6Cloud storage mandatory (no privacy mode)Local-only modeP1
A7Full activity/action log as evidenceSame + exportable audit logP1

7. Settings, notifications, platforms

IDGrok BotBuddy Bots โ€” betterPhase
N1Appearance: system/light/dark; timezoneSameP1
N2Per-bot notification toggle; OS and mobile push; suppressed while app is focusedBrowser push first, then mobileP2
N3Usage display: weekly included + on-demandReal cost per bot, per task, per modelP1
N4Error banners, copy request IDSameP1
N5Desktop apps: macOS, Windows, LinuxResponsive web app first; Electron wrapper laterP3
N6Mobile apps iOS 18+/Android 9+: chat, voice dictation, photo capture, approvals, screen view, routines, searchPWA first; React Native laterP3
N7Sync across devicesSame (server-side state)P1

8. Teams and enterprise

IDGrok BotBuddy Bots โ€” betterPhase
T1Team seats; team-only bot templatesSameP3
T2Admin-enforced (locked) auto-review rules; restrict local execution; managed computer setup; plugin restrictionsSameP3
T3DLP, proxies, network restrictionsProxy + domain allowlist per botP3

9. Where Buddy Bots wins (summary)

  1. Any LLM per bot (they have no model picker).
  2. Jev-first browser control โ€” large cost and speed advantage if success rate holds; measured from day one.
  3. Per-bot isolated logins (their bots all share one credential pool).
  4. Self-hosted / local-only, bring-your-own keys.
  5. MCP-native connectors instead of a closed marketplace.
  6. Transparent cost per bot and task.
  7. Deterministic replay of taught tasks; dry-run routines; editable memory.
  8. No caps on group size, routines or run history.

10. Where they will stay ahead (honest)

11. Unknowns to verify

12. Build status โ€” v0.3 (20 Sep 2026)

P1 and P2 are built and were tested with real keys: Jev through OpenRouter (/api/alpha/decisions, ~typesafe/jev-latest) and OpenAI models. Code: buddybots-app.zip (see its README).

Measured: SkyBench flight search 5/5 correct, ~9 s and ~$0.001 per task; 26 Jev decisions at 100% step success, median 238 ms, ~$0.00003 each. Also passed with real models: Wikipedia lookup, approval allow/deny, canvas page via vision fallback, 3-bot room with the redundancy gate, handoff, memory, PDF+XLSX reconciliation with structured report. 16 integration tests in simulator mode. Sample is small โ€” one test site, one real site.

Closed since v0.2: B7 wipe files, C6 file handoffs, C8 proactive follow-ups, C10 mark unread, F2 PDF/Word/Excel/PowerPoint parsing, F5 structured results, K10 snapshot/recover/reset, S4 Slack + GitHub webhook events with match rules, N4 request IDs.

Added after v0.3: real desktop computer (K1/K3/K4 โ€” X display, window manager, real Chromium window + terminal, whole-desktop live view, takeover with real mouse/keyboard; own desktop per bot when profiles are isolated), look tool (bots review their work visually), navigator hardening for live sites, access token + docker-compose for an always-on box.

Added 20 Sep (later): template library with share code / file / public link and Grok Bot template import (B6), reply streaming, audio/video transcription (F2), email trigger (S4), whole-screen desktop tool.

Still open inside P1/P2:

IDGap
F3Office-format outputs depend on Python libraries on the host.
S4Email trigger is built but untested against a live mailbox; Slack/GitHub need the webhook URL reachable from the internet.
B6Grok template *links* import only their public fields (name, author, description); x.ai does not publish skills/routines. Full-fidelity path: the owner asks their own Grok bot to export itself (Import โ†’ My Grok bot) and pastes the reply.
K9Whole-screen clicking needs a computer-use-trained model; general models miss small targets.
โ€”One shared access token, no user accounts. Anthropic, DeepSeek, Gemini, xAI, Ollama adapters are untested.

Tuning knobs found in testing: room speak thresholds 0.5 (owner) / 0.7 (others) / 0.65 (bot-to-bot); redundancy gate holds at โ‰ฅ 0.4; navigator stops at goal_done > 0.8; vision capped at 8 steps per run.

ยฉ 2026 BuddyBots ยท TermsPrivacySecurityStatusContact