Promptbook versus Grok Bot
When to choose Promptbook
When the operation should run on your own host. For example, agents can review invoices from a shared folder using the same working project and task history.
When to choose Grok Bot
When you want bots with a ready-made cloud computer. They can run routines, and you can talk to them in Slack or X Chat.
| Feature | Promptbook | Grok Bot |
|---|---|---|
| Self-hosting | YesYour computer or server | NoxAI cloud, desktop access |
| Runs with your computer off | ConditionalWhen hosted elsewhere | YesCloud routines |
| Where your data lives | On your host: project files with Git change history. | Files and sessions in xAI cloud |
| AI models | Claude, GPT, Gemini, Qwen, … including local. Automatic choice from available models for the task. | Grok |
| Scheduled tasks | YesRecurring agent tasks | YesBot routines |
| Integrations | Universal browser. Web apps even without a connector. | Browser, connected apps and desktop commands |
| Passwords and credentials | Local encrypted Wallet; passwords outside the agent’s context. | Account bots share sign-ins on the cloud computer |
| Trust model | Zero Trust: E2E App–engine. The relay cannot read working content. | Trust in xAI cloud; isolated computer and permissions |
| Mobile and remote control | YesApp over E2E to your own engine | YesGrok Bot app, Slack or X Chat |
| AI tools and selection | Codex, Claude Code, Gemini CLI, Qwen Code, OpenCode, … Automatic choice by task and availability. | Built-in Grok Bot |
E2E protects the App–engine connection. External AI and services receive authorized inputs. Git keeps file history; it does not encrypt files or undo external actions. Wallet stays outside Git. Data and security ↗ Connection architecture ↗
Feature details
Self-hosting
PromptbookThe engine that runs and schedules agent work lives on your computer, company server or VPS under your control.
Grok BotBots run on the service’s persistent cloud computer. With permission, they can run individual commands on your desktop.
Runs with your computer off
PromptbookClosing the controls leaves work running. Shutting down the engine host stops it. An engine on a running server can continue.
Grok BotCloud work and routines continue. A desktop command needs the desktop to be available.
Where your data lives
PromptbookAgents, tasks and conversations stay in project files on your host, with an auditable Git change history. Git does not encrypt files or undo actions in external services; Wallet stays outside it.
Grok BotFiles and sessions in xAI cloud
AI models
PromptbookClaude, GPT, Gemini, Qwen and other models through supported tools and extensible integrations, including local models depending on the adapter and task. You are not tied to one vendor. External models receive the inputs they need.
Grok BotGrok
Scheduled tasks
PromptbookGive a team of agents an ongoing responsibility, goal and rules. The engine runs one-off and recurring tasks.
Grok BotBots can collaborate, work in the background and run routines on a schedule.
Integrations
PromptbookA universal browser operates web apps much like a person, including services without a ready-made connector or API. Capabilities depend on access, permissions and each service’s restrictions.
Grok BotBrowser, connected apps and desktop commands
Passwords and credentials
PromptbookWallet is an encrypted credential vault on your host, separate from Git. A protected integration fills verified sign-in forms without putting passwords in the agent’s context. Protection requires keeping Wallet isolated from agent tools.
Grok BotAccount bots share sign-ins on the cloud computer
Trust model
PromptbookZero Trust for the App–engine connection: working content is encrypted between endpoints, and neither the relay nor central backend decrypts it. External AI and tools receive authorized inputs; account and operational metadata remain separate.
Grok BotTrust in xAI cloud; isolated computer and permissions
Mobile and remote control
PromptbookUse the control App to assign work, follow chats and manage the project over an authenticated E2E connection to your own engine. The local Console has separate access on the engine host. Closing the App does not stop the operation.
Grok BotGrok Bot app, Slack or X Chat
AI tools and selection
PromptbookCodex, Claude Code, Gemini CLI, Qwen Code, OpenCode, GitHub Copilot, … A shared interface supports further integrations. Promptbook automatically chooses a suitable available tool and model for the task, capabilities and configured accounts, respecting your choices and limits.
Grok BotBuilt-in Grok Bot
Core features reviewed 10 November 2026. Integrations, models and access reviewed 11 November 2026.