Skip to content
promptbook
Promptbook versus

Promptbook versus Claude Code

When to choose Promptbook

When Claude Code is part of ongoing website maintenance. Give it a coding role in Promptbook and coordinate recurring checks and handoffs in the same project.

When to choose Claude Code

When you want to work on a repository from the terminal or add Claude to your own script or CI.

Promptbook versus Claude Code
FeaturePromptbookClaude Code
Tasks and chats in project GitYes.book files in one repositoryPartialGit for code, separate tasks and sessions
Self-hostingYesYour computer or serverYesLocal CLI, optional cloud
Runs with your computer offConditionalWhen hosted elsewhereConditionalRemote sessions
Where your data livesOn your host: project files with Git change history.Local project and sessions; context sent to the model. Optional cloud.
AI modelsClaude, GPT, Gemini, Qwen, … including local. Automatic choice from available models for the task.Claude; connections by configuration
Scheduled tasksYesRecurring agent tasksYesSession, Desktop and cloud
IntegrationsUniversal browser. Web apps even without a connector.MCP, terminal and Chrome through a supported extension
Passwords and credentialsLocal encrypted Wallet; passwords outside the agent’s context.Native sign-in/API keys; MCP credentials depend on server
Trust modelZero Trust: E2E App–engine. The relay cannot read working content.Local execution; Remote Control over TLS, transcripts on Anthropic servers.
Mobile and remote controlYesApp over E2E to your own engineYesRemote Control on web and mobile; host must stay on
AI tools and selectionCodex, Claude Code, Gemini CLI, Qwen Code, OpenCode, … Automatic choice by task and availability.Claude Code; Anthropic or supported cloud connections

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.

Claude CodeRun the CLI in your terminal or CI. Anthropic also offers a separate web environment.

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.

Claude CodeLocal work requires the host machine to stay on. Remote work depends on its own host.

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.

Claude CodeLocal project and sessions; context sent to the model. Optional 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.

Claude CodeClaude; connections by configuration

Scheduled tasks

PromptbookGive a team of agents an ongoing responsibility, goal and rules. The engine runs one-off and recurring tasks.

Claude CodeSchedule tasks in a session, on Desktop or in the cloud. Claude Code can also run from scripts or CI.

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.

Claude CodeMCP, terminal and Chrome through a supported extension

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.

Claude CodeNative sign-in/API keys; MCP credentials depend on server

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.

Claude CodeLocal execution; Remote Control over TLS, transcripts on Anthropic servers.

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.

Claude CodeRemote Control on web and mobile; host must stay on

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.

Claude CodeClaude Code; Anthropic or supported cloud connections

Core features reviewed 10 November 2026. Integrations, models and access reviewed 11 November 2026.