Cloudflare vs E2B (2026)

Agents act in outside systems through several routes. The MCP client connects an agent to remote MCP servers with OAuth, elicitation and reconnection after restarts, and Code Mode turns MCP servers and OpenAPI services into typed connectors that model written code calls while authentication stays in the host Worker. Agents also send and receive email, answer Slack and voice, receive webhooks, and can pay for HTTP services or MCP tools over x402 and the Machine Payments Protocol. Custom tools are ordinary functions handed to the model through the AI SDK, TanStack AI or a harness.

Sourcedevelopers.cloudflare.com/agents/tools/mcpread 2026-11-05

An agent in a sandbox reaches other systems through a built in MCP gateway that runs inside the sandbox and exposes more than 200 tools from the Docker MCP Catalog (Airtable, GitHub, Browserbase, Exa and others) or custom MCP servers through one interface. Credentials are passed as secrets that resolve at egress instead of living in the sandbox.

Sourcedocs.e2b.dev/mcp-gatewayread 2026-11-03

Multistep and multi agent work has its own runtimes. Workflows run durable steps with automatic retries and can wait months for an event or an approval, and the Agents SDK comes with patterns for prompt chaining, routing, parallelization and orchestrator and worker setups. Sub agents run as child Durable Objects with isolated storage and typed RPC, or as streaming tools of a parent agent, and a durable job queue and fibers keep long work alive through eviction and crashes.

Sourcedevelopers.cloudflare.com/agents/concepts/workflowsread 2026-11-05

There is no workflow logic in E2B itself. The customer brings its own orchestration framework, and E2B provides the machine an agent's steps run on (commands, background processes, code contexts), not a runtime that sequences, branches, retries or routes those steps. Forking a sandbox copies its state, which is compute, not workflow logic.

Sourcee2b.dev/llms.txtread 2026-11-03

Work reaches an agent from schedules, messages and events. The scheduler runs callbacks after a delay, at a date, on a cron expression or on an interval, and Think adds timezone aware recurring tasks. Agents receive email, Slack messages and mentions, voice over WebSocket, Chat SDK messenger webhooks such as Telegram, and webhook events routed to a dedicated agent instance, while a built in queue works through background tasks in order.

Sourcedevelopers.cloudflare.com/agents/agent-class/schedule-tasksread 2026-11-05

A sandbox can start without the customer's code calling it. With auto resume set, a paused sandbox resumes when activity arrives, so an agent served from a sandbox starts on an inbound request, and E2B's guides deploy agent gateways this way, for example OpenClaw answering Telegram. Sandbox lifecycle events are also pushed to the customer's webhook, signed. There is no scheduler.

Sourcedocs.e2b.dev/sandbox/auto-resumeread 2026-11-03

Retrieval runs on maintained indexes. AI Search builds and manages indexes over R2 buckets, websites and uploaded files and returns relevant chunks, or a generated answer, to the agent, and Vectorize stores embeddings for custom retrieval. A searchable context block also gives each agent a full text index in its own Durable Object storage that it can query and add entries to.

Sourcedevelopers.cloudflare.com/agents/tools/ai-searchread 2026-11-05

There is no retrieval structure over the customer's content, since E2B runs the agent's code. Files uploaded to a sandbox or volume are storage the agent's code can read, not an index a query returns, and the MCP gateway's tools reach outside knowledge sources owned by others.

Sourcee2b.dev/llms.txtread 2026-11-03

The Session API is a memory layer kept in each agent's own Durable Object SQLite database. Conversation history persists as a branching message tree with full text search and compaction that summarizes older messages without deleting them, and chosen messages or a whole session can be deleted.

Writable memory blocks, such as learned facts or a task list, are injected into every turn and updated by the agent itself through a set_context tool within a token budget. Memory belongs to the agent instance, usually one per user or conversation, and survives hibernation and eviction. These memory APIs are still marked experimental.

Sourcedevelopers.cloudflare.com/agents/concepts/conversation-state-and-memoryread 2026-11-05

An agent's working state carries across sessions. A paused sandbox resumes exactly as it was, with filesystem and memory, running processes and loaded variables, and is kept until it is killed. Snapshots and forks copy that state, volumes, in private beta, keep files across sandboxes, and code contexts keep interpreter variables between executions, which the agent's code reads to continue its task. This is machine state the developer manages, with no memory layer of stated types or scope that can be reviewed, edited or deleted as memory.

Sourcedocs.e2b.dev/sandbox/persistenceread 2026-11-03

Approvals are part of the runtime. A Workflow can wait with waitForApproval() for minutes or months and resumes when the agent's approve or reject method is called, and durable Code Mode marks chosen connector calls with requiresApproval, so model written code pauses before the tool runs and replays once someone approves. MCP elicitation asks the user for input or an out of band step in the middle of a call, and a browser run can pause while a person logs in or solves a captcha through a Live View link.

Sourcedevelopers.cloudflare.com/agents/concepts/agentic-patterns/human-in-the-loopread 2026-11-05

There is no approval step, consent checkpoint or escalation to a person for work inside an E2B sandbox. Egress control (allow and deny lists for each sandbox, a proxy the customer runs that fails closed, and access tokens on public URLs) limits what an agent's code can reach, but that is isolation the developer configures, not a point where a person reviews the agent's action.

Sourcee2b.dev/enterpriseread 2026-11-03

Cloudflare provides SOC 2, ISO and PCI reports to an account's Super Administrators and operates FedRAMP Moderate data centers. Access to the developer platform runs through account, domain and resource scoped roles, including Workers Platform Admin and its read only counterpart, Audit Logs Viewer and the Secrets Store roles, with dashboard single sign on, SCIM provisioning and audit logs. Agents check callers in the Worker before routing a request to them, and MCP servers built on Cloudflare can require OAuth 2.1 with scopes.

Sourcedevelopers.cloudflare.com/fundamentals/manage-members/rolesread 2026-11-05

E2B holds SOC 2 Type II, with the report under NDA in its trust center at trust.e2b.dev, and signs HIPAA Business Associate Agreements on Enterprise plans. Its controls protect the sandbox. Every sandbox is its own Firecracker microVM with its own kernel, egress can be allowed or denied for each sandbox, secrets are injected at the egress proxy so no sandbox holds them, and public sandbox URLs can require an access token. Who inside a customer's organization can do what has no published control yet, since E2B lists single sign on, SCIM and role based access as planned.

Sourcee2b.dev/securityread 2026-11-03

Agent activity is traced turn by turn. The Agents tab lists each agent's model, sessions, runs and token use, session replay shows messages, reasoning, tool calls and sub agent activity, and each trace is a waterfall of model calls, tool runs and approvals that exports through OpenTelemetry. Diagnostics channels emit structured events for schedules, jobs, workflows and MCP connections, and account audit logs record who changed what. Traces are kept for seven days, and recording message and tool payloads is opt in.

Sourcedevelopers.cloudflare.com/agents/runtime/observability/tracingread 2026-11-05

The record covers the sandbox, not the agent. Every lifecycle event is available through an events API and delivered as a signed webhook, sandbox metrics report CPU and memory use, template builds keep logs, and on Enterprise OpenTelemetry metrics and logs export to the customer's OTLP endpoint. Prompts, tool calls, retrieved knowledge and outputs cannot be inspected step by step in E2B, since the agent's reasoning runs outside the sandbox, and there is no audit log of user actions apart from the runtime.

Sourcee2b.dev/enterpriseread 2026-11-03

Agent state can be pinned to a jurisdiction. Durable Objects created in the EU, US or FedRAMP jurisdiction run and store data only there, location hints place new objects near one of eleven regions from western North America to Oceania, and Regional Services control where requests are answered. Agents run on Cloudflare's global network, and the routing helper passes jurisdiction and location hints straight to the agent's Durable Object.

Sourcedevelopers.cloudflare.com/durable-objects/reference/data-locationread 2026-11-05

Three deployment modes share the same SDK, CLI and API. E2B Cloud defaults to Google Cloud us-west1, and AWS us-west-2 and us-east-1 and Google Cloud europe-west1 and asia-southeast1 are available on request on every plan. With BYOC on AWS, Google Cloud or Azure on Enterprise, the data plane runs in the customer's own cloud account. E2B Embed packages the Apache-2.0 runtime for a single node self hosted install, and a private cloud option is in development.

Sourcedocs.e2b.dev/faq/egress-ip-rangesread 2026-11-03

Starting points come as harnesses, examples and skills. Think is an opinionated chat agent framework with built in tools, memory, messengers and scheduled tasks, Pi and OpenCode harnesses run inside a Durable Object, examples cover browser, chat, email, Slack and voice agents, and the agents starter template ships ready to deploy, alongside Agent Skills for coding agents. These are frameworks and examples a developer builds on, not finished agents a business adopts as they are.

Sourcedevelopers.cloudflare.com/agents/harnessesread 2026-11-05

Starting points ship with the platform, including sandbox templates for Claude Code, a desktop, Docker and web app stacks, a cookbook of examples ready to run, setup guides for more than thirty agents and frameworks, and open source reference apps, Surf, a computer use agent, and Fragments, a builder that turns a prompt into an app. These are environments and examples a developer builds from, not a browsable catalog of agents a customer adopts.

Sourcedocs.e2b.dev/llms.txtread 2026-11-03

The developer chooses the model for each call. One createAI provider reaches Workers AI models hosted on Cloudflare, AI Gateway catalog models, dynamic routes and vendor SDK models from the AI SDK or Pi AI, with AI Gateway in front of outside providers, and harnesses such as OpenCode and Pi accept the same choices.

Sourcedevelopers.cloudflare.com/agents/modelsread 2026-11-05

Compute is what E2B provides for agents, with the customer bringing its own model and orchestration framework. Sandboxes connect to any LLM and to agents and frameworks such as Claude Code, Codex, the OpenAI Agents SDK, the Vercel AI SDK, LangChain, CrewAI, Mastra and Google ADK. E2B imposes no model, so model choice stays with the customer.

Sourcee2b.dev/llms.txtread 2026-11-03

Developers drive the platform through the Cloudflare REST API, Wrangler and SDKs, and each agent exposes its own methods to browsers and servers through callable methods, a typed client SDK and HTTP or WebSocket routes. Cloudflare's managed remote MCP servers let an assistant read configuration and manage services across an account, and the Agents SDK builds stateless remote MCP servers on Workers.

Sourcedevelopers.cloudflare.com/agents/agent-class/callable-methodsread 2026-11-05

Outside systems can call E2B through Python and JavaScript/TypeScript SDKs, a CLI, a REST API described by a published OpenAPI 3.1 specification, and custom sandbox templates the customer builds, tags and versions. A public MCP server serves E2B's documentation to agents.

Sourcee2b.dev/llms.txtread 2026-11-03

Agents can be tested before release. The Workers Vitest integration runs tests against an agent in the real runtime, checking its responses, methods and state, the agents starter template ships with it configured, and wrangler dev runs the agent locally. Nothing scores model output or compares an agent's behavior across versions.

Sourcedevelopers.cloudflare.com/agents/getting-started/testing-your-agentread 2026-11-05

There are no fixtures, scoring, quality gates or comparison of agent runs. E2B is where evaluations and reinforcement learning run, not how they are scored. It lists reinforcement learning among its workloads and runs NVIDIA NeMo Gym environments in sandboxes, but the datasets, reward functions and scoring belong to the customer's framework.

Sourcee2b.dev/llms.txtread 2026-11-03

Agents drive a real Chrome through Browser Run, which runs on the Workers Free and Paid plans. Model written code sends any Chrome DevTools Protocol command to a live session to navigate, run JavaScript, read the DOM and capture screenshots, and the agent can return to the same browser on later turns with its tabs, cookies and login intact while the session stays alive, up to 10 minutes idle by default. Quick actions return a page as Markdown, extracted data, its links or scraped elements. Live View and session recording, which let a person watch or replay a session, are in beta.

Sourcedevelopers.cloudflare.com/agents/tools/browserread 2026-11-05

Agents control real desktops hosted by E2B. E2B Desktop sandboxes are Ubuntu machines with an XFCE desktop and preinstalled applications, and the Desktop SDK gives the agent screenshots, mouse, keyboard and scroll, with a live VNC stream so a person can watch. A cloud browser can also run in a sandbox, and Surf is E2B's open source computer use agent built on it.

Sourcedocs.e2b.dev/use-cases/computer-useread 2026-11-03