{ "data": { "a": { "slug": "agentcore-code-interpreter", "name": "Amazon Bedrock AgentCore Code Interpreter", "vendor": "Amazon Web Services", "vendorUrl": "https://aws.amazon.com/bedrock/agentcore/", "kind": "http-api", "category": "code-sandboxes", "summary": "Amazon Bedrock AgentCore Code Interpreter is AWS's managed sandbox for running agent-written Python, JavaScript and TypeScript. Each session is a dedicated microVM, reached through the AWS API, the AgentCore SDKs or an MCP server.", "url": "https://www.anchorterminal.com/tools/agentcore-code-interpreter", "markdownUrl": "https://www.anchorterminal.com/tools/agentcore-code-interpreter.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/agentcore-code-interpreter.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/agentcore-code-interpreter.json", "repo": "https://github.com/aws/bedrock-agentcore-sdk-python", "license": "Proprietary service under the AWS Service Terms. The AgentCore SDKs for Python and TypeScript and the AgentCore MCP server are Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://bedrock-agentcore.{region}.amazonaws.com/code-interpreters/{id}/tools/invoke", "packages": [ { "registry": "pypi", "name": "bedrock-agentcore" }, { "registry": "npm", "name": "bedrock-agentcore" }, { "registry": "pypi", "name": "boto3" }, { "registry": "pypi", "name": "awslabs.amazon-bedrock-agentcore-mcp-server" } ], "auth": "api-key", "authNotes": "AWS Signature Version 4 with IAM access keys or a role, self-serve once an AWS account exists. A policy must allow `bedrock-agentcore:StartCodeInterpreterSession`, `bedrock-agentcore:InvokeCodeInterpreter` and `bedrock-agentcore:StopCodeInterpreterSession` on the interpreter's ARN. The managed interpreter `aws.codeinterpreter.v1` needs no resource of its own. A custom interpreter takes a network mode and an execution role, which bounds the AWS resources code in the sandbox can reach. No partner or sales approval.", "pricing": "usage", "pricingNotes": "$0.0895 a vCPU-hour and $0.00945 a GB-hour, billed per second on CPU used and peak memory, with a one-second minimum and 128 MB minimum memory. AWS says I/O wait and idle time are free when no background process is running. Network data transfer is extra at EC2 rates. No allowance specific to Code Interpreter. New AWS accounts get up to $200 in Free Tier credits, and AWS says most new customers sign up without a payment method, so an agent's owner can start without a contract (https://aws.amazon.com/bedrock/agentcore/pricing/, https://aws.amazon.com/free/free-tier-faqs/, checked 2026-10-08).", "priceSummary": "$0.0895 / vCPU-hr", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the Code Interpreter endpoints, in the API reference or on the pricing page. AgentCore Payments, a separate component, lets a customer's agents pay third parties over x402 and MPP and is not a way to pay AWS (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 776, "npmWeekly": 334717, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-tool.html", "llmsTxt": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/llms.txt", "capabilities": [ "sandbox.code", "sandbox.fs" ], "tags": [ "hosted", "usage-priced", "closed-source", "python", "typescript", "enterprise", "llms-txt", "mcp", "free-tier", "no-card", "status-page", "soc2" ], "lastRelease": "2026-10-07", "graded": true, "anchor": { "graded": true, "score": 73.1, "grade": "BB", "agentReady": true, "rank": 89, "ranked": true, "rankOf": 842, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 65, "payments": 30, "reliability": 85, "schema": 81, "security": 87, "transparency": 70 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Each session runs in its own microVM with 2 vCPU, 8 GB and a 10 GB disk for up to eight hours, and IAM can scope access to one interpreter. Sessions cannot be paused or resumed, and an AWS account with IAM set-up is needed before a first call.", "bestFor": "A team already on AWS that wants agent code to run under IAM, inside a VPC and beside S3 data, for sessions up to eight hours.", "strengths": [ "Each session runs in a dedicated microVM, which AWS says is terminated and has its memory sanitised when the session ends", "Billing is per second on CPU used and peak memory, at $0.0895 a vCPU-hour and $0.00945 a GB-hour, with I/O wait and idle time free", "IAM actions cover each of the nine operations, with separate ARNs for the system interpreter and custom ones", "Rate limits are published per API, 30 requests a second for `StartCodeInterpreterSession` and `InvokeCodeInterpreter`, and 1,000 concurrent sessions per account", "The managed interpreter `aws.codeinterpreter.v1` needs no resource set-up, and `code_session` in the Python SDK starts and stops a session in one block" ], "weaknesses": [ "No pause, resume or snapshot. Session files are removed when the session ends, and persistence needs a customer-owned S3 Files or EFS mount inside a VPC", "Every session is capped at 2 vCPU, 8 GB of memory and 10 GB of disk, and the cap is not adjustable", "`InvokeCodeInterpreter` takes one flat `arguments` object for nine operations, so the reference does not say which fields each operation requires", "The Bedrock SLA that AWS says applies to AgentCore dates from 4 October 2023 and names only the Bedrock APIs for models", "The troubleshooting page is three bullet points, and execution console logs are not sent to CloudWatch" ], "agentNotes": [ "Start a session with `StartCodeInterpreterSession`, then pass its id in the `x-amzn-code-interpreter-session-id` header on every `InvokeCodeInterpreter` call", "Set `sessionTimeoutSeconds` when starting. The default is 900 seconds and the maximum is eight hours, and the session ends itself at the timeout", "Stop sessions when done. Billing runs per second while code is busy, and a session left open counts against the 1,000 concurrent-session quota", "Use `startCommandExecution`, `getTask` and `stopTask` for work longer than the 15-minute synchronous request limit", "Retry `ThrottlingException` (429) and `InternalServerException` (500) with exponential backoff, and treat `ServiceQuotaExceededException`, returned as HTTP 402, as a quota to raise" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 73.1 } ], "editorialScores": { "ergonomics": 75, "maintenance": 65, "payments": 30, "reliability": 85, "schema": 81, "security": 87, "transparency": 51 }, "provenanceScore": 88 }, "connect": { "install": "pip install bedrock-agentcore # or: npm i bedrock-agentcore", "http": "awscurl -X POST \\\n \"https://bedrock-agentcore.us-west-2.amazonaws.com/code-interpreters/aws.codeinterpreter.v1/tools/invoke\" \\\n -H \"Content-Type: application/json\" \\\n -H \"x-amzn-code-interpreter-session-id: $SESSION_ID\" \\\n --service bedrock-agentcore --region us-west-2 \\\n -d '{\"name\":\"executeCode\",\"arguments\":{\"language\":\"python\",\"code\":\"print(\\\"Hello, world!\\\")\"}}'", "config": { "mcpServers": { "bedrock-agentcore-mcp-server": { "args": [ "awslabs.amazon-bedrock-agentcore-mcp-server@latest" ], "command": "uvx", "env": { "AGENTCORE_ENABLE_TOOLS": "code_interpreter", "FASTMCP_LOG_LEVEL": "ERROR" } } } } }, "letme": { "capability": "https://letme.dev/sandbox.code", "tool": "https://letme.dev/agentcore-code-interpreter" }, "sameCompany": [ "amazon-bedrock-customization", "amazon-textract", "aws-end-user-messaging", "amazon-sns", "amazon-s3" ], "area": "agent-runtime", "unitPrices": [ { "item": "CPU", "unit": "vcpu-hour", "usd": 0.0895, "note": "Billed per second on CPU used. Memory extra at $0.00945 a GB-hour on peak use" }, { "item": "Session at the 2 vCPU, 8 GB cap, fully busy", "unit": "session-hour", "usd": 0.2546, "note": "Our sum of 2 x $0.0895 and 8 x $0.00945. I/O wait and idle time are not billed" } ], "provenance": { "legalEntity": "Amazon Web Services, Inc.", "domain": "amazonaws.com", "domainRegistered": "2005-08-18", "endpointOnVendorDomain": true, "terms": "https://aws.amazon.com/service-terms/", "privacy": "https://aws.amazon.com/privacy/", "statusPage": "https://health.aws.amazon.com/health/status", "changelog": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/release-notes.html", "securityTxt": "expired", "checked": "2026-10-08", "notes": [ "The endpoints are `bedrock-agentcore.\u003cregion\u003e.amazonaws.com`. RDAP gives 2005-08-18 for amazonaws.com and 1994-11-01 for amazon.com, where the product, pricing and legal pages sit.", "The AWS Service Terms were last updated on 1 October 2026. Section 50 covers Amazon Bedrock. No clause naming Code Interpreter was found.", "The AWS Privacy Notice, last updated 18 May 2026, names Amazon Web Services, Inc. and says it does not apply to content customers process in AWS services, which the customer agreement governs.", "aws.amazon.com/.well-known/security.txt has Contact and Policy fields, and its Expires date of 2026-09-24 had passed on 8 October 2026.", "AgentCore release notes carry a month for each entry, not a day." ], "score": 88 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/agentcore-code-interpreter.json", "live": { "slug": "agentcore-code-interpreter", "probe": { "target": "https://bedrock-agentcore.{region}.amazonaws.com/code-interpreters/{id}/tools/invoke", "method": "get", "lastAt": "2026-10-09T09:26:41.522149204Z", "lastOk": false, "lastStatus": 0, "lastMs": 0, "lastNote": "invalid character \"{\" in host name", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 20, "samples30d": 20, "days": [ { "date": "2026-10-09", "probes": 20, "ok": 0 } ], "outages": [ { "start": "2026-10-09T07:40:18.24415355Z", "end": "0001-01-01T00:00:00Z", "note": "invalid character \"{\" in host name" } ] }, "vendorStatus": { "page": "https://health.aws.amazon.com/health/status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-09T07:57:35.17007236Z" }, "updatedAt": "2026-10-09T09:26:41.522149204Z" } }, "answer": "Microsoft Execution Containers scores 76.3 (BB) on agent readiness against Amazon Bedrock AgentCore Code Interpreter's 73.1 (BB), and leads in 3 of 7 scored categories. Amazon Bedrock AgentCore Code Interpreter leads on security \u0026 auth.", "b": { "slug": "microsoft-execution-containers", "name": "Microsoft Execution Containers", "vendor": "Microsoft", "vendorUrl": "https://github.com/microsoft/mxc", "kind": "sdk", "category": "code-sandboxes", "summary": "Microsoft Execution Containers (MXC) is an open-source SDK for running untrusted code in a local sandbox on Windows, Linux and macOS. An application embeds it through Node.js, .NET or Rust and sets filesystem, network and UI policy for each run.", "url": "https://www.anchorterminal.com/tools/microsoft-execution-containers", "markdownUrl": "https://www.anchorterminal.com/tools/microsoft-execution-containers.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/microsoft-execution-containers.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/microsoft-execution-containers.json", "repo": "https://github.com/microsoft/mxc", "license": "MIT", "transports": [], "packages": [ { "registry": "npm", "name": "@microsoft/mxc-sdk" }, { "registry": "nuget", "name": "Microsoft.Mxc.Sdk" } ], "auth": "none", "authNotes": "No account, key or sign-in. MXC is a library the host application loads in its own process, so it holds no credential of its own. The workload runs with whatever the request grants. Network egress, ingress and host loopback resolve to `deny` when omitted, and filesystem access is limited to the `readonlyPaths` and `readwritePaths` the caller lists. On Windows the `isolation_session` backend creates a separate agent user account for each container and returns its name and SID.", "pricing": "free", "pricingNotes": "Free. The SDKs and native runtime are MIT and install from npm, NuGet and crates.io with no account or card. There is no hosted service and nothing to buy. Compute is the owner's own machine. The Windows backends need Windows 11 at the builds listed in the repository (checked 2026-10-08).", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the README, the docs or the SDK source. Local open-source software with no paid endpoint (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 1506, "npmWeekly": 471674, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://github.com/microsoft/mxc/blob/main/docs/api-reference/README.md", "capabilities": [ "sandbox.code", "sandbox.fs", "sandbox.persist" ], "tags": [ "sdk", "open-source", "local", "free", "no-auth", "no-card", "typescript", "dotnet", "rust", "windows", "linux", "macos", "json-schema", "new-1.0" ], "lastRelease": "2026-10-06", "graded": true, "anchor": { "graded": true, "score": 76.3, "grade": "BB", "agentReady": true, "rank": 35, "ranked": true, "rankOf": 842, "categoryRank": 1, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 92, "payments": 60, "reliability": 81, "schema": 81, "security": 69, "transparency": 83 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "MXC puts nine operating-system sandbox backends behind one typed request, with network access denied by default and a JSON Schema for the stable 1.0.0 contract. Version 1.0.0 is two days old as of 8 October 2026. Enforcement varies by backend, and `isolation_session` cannot restrict networking at all.", "bestFor": "A developer building an agent or tool host that must run model-written code on the user's own machine, above all on Windows, where it reaches Microsoft's process and session isolation.", "strengths": [ "MIT licence, with SDKs for Node.js, .NET and Rust all at 1.0.0 and the native runtime bundled in the npm and NuGet packages", "Egress, ingress and host loopback default to `deny`, and filesystem access is limited to listed read-only and read-write paths", "A draft-07 JSON Schema for the stable 1.0.0 request, with descriptions on 135 of 150 properties", "Errors carry one of 12 typed codes plus an optional remediation, and `validate*` calls dry-run a request without creating a container", "Telemetry is opt-in, Windows-only and gated on user consent and an administrative policy that can only block it" ], "weaknesses": [ "1.0.0 shipped on 6 October 2026, and the Node changelog still lists the V1 changes under Unreleased", "Enforcement differs by backend. `isolation_session` cannot restrict networking, and proxy routing is cooperative on Seatbelt and WSLC", "Persistent containers exist only for `isolation_session` and `wslc`, both on Windows", "On Windows the Node SDK runs a PATH-resolved `whoami` at import, reported on 24 September 2026 and still open", "The npm package is 37.7 MB compressed, needs Node.js 24 or later, and carries no `repository` field or provenance attestation" ], "agentNotes": [ "Import from `@microsoft/mxc-sdk/v1`. The package root exports nothing.", "Call `getPlatformSupport()` first and stop if `isSupported` is false. `getAvailableBackends()` is advisory and launch-time validation still applies.", "Set `network.egress.default` to `allow` only when the task needs it. Omitted network policy resolves to deny in every direction.", "Never pass `--audit` to an executor for untrusted code. It turns off all sandbox security for the workload.", "Read `ExecutionResult.warnings` after each run. Security warnings arrive there and are not written to stdout or stderr." ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 76.3 } ], "editorialScores": { "ergonomics": 74, "maintenance": 92, "payments": 60, "reliability": 81, "schema": 81, "security": 69, "transparency": 86 }, "provenanceScore": 79 }, "connect": { "install": "npm install @microsoft/mxc-sdk" }, "letme": { "capability": "https://letme.dev/sandbox.code", "tool": "https://letme.dev/microsoft-execution-containers" }, "sameCompany": [ "azure-foundry-fine-tuning", "azure-ai-content-safety", "azure-speech-to-text", "azure-text-to-speech", "microsoft-agent-framework", "microsoft-entra-agent-id", "azure-key-vault", "azure-document-intelligence", "azure-devops-mcp", "microsoft-learn-mcp", "playwright-mcp", "azure-mcp", "azure-maps", "azure-translator", "microsoft-graph-calendar", "azure-blob-storage", "onedrive-sharepoint", "microsoft-teams", "dynamics-365-sales", "power-automate", "foundry-local", "microsoft-advertising-api", "microsoft-excel-graph", "outlook-mail-graph" ], "area": "agent-runtime", "provenance": { "legalEntity": "Microsoft Corporation", "domain": "microsoft.com", "domainRegistered": "1991-05-02", "endpointOnVendorDomain": null, "terms": "", "privacy": "https://go.microsoft.com/fwlink/?linkid=521839", "statusPage": "", "changelog": "https://github.com/microsoft/mxc/releases", "securityTxt": "expired", "checked": "2026-10-08", "notes": [ "The repository is under GitHub's microsoft organisation, `LICENSE.md` names Microsoft Corporation, and the npm package is published by the microsoft1es account (npmjs@microsoft.com).", "www.microsoft.com/.well-known/security.txt loads and points to the MSRC researcher portal, but its Expires field is 2026-09-23T16:00:00.000Z, which had passed on 8 October 2026.", "RDAP for microsoft.com gives a registration date of 1991-05-02.", "No terms page applies to the open-source SDK beyond the MIT licence. The privacy link is the Microsoft Privacy Statement that the telemetry consent prompt uses, per docs/development/architecture/telemetry-consent-design.md.", "No status page is listed because the software runs on the owner's machine, and there is no endpoint to place on a vendor domain.", "https://learn.microsoft.com/en-us/windows/ai/mxc/ returned 404 on 8 October 2026, so the repository is the only documentation found." ], "score": 79 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/microsoft-execution-containers.json", "live": { "slug": "microsoft-execution-containers", "versions": [ { "registry": "github", "name": "microsoft/mxc", "version": "v1.0.0", "released": "2026-10-07", "seenAt": "2026-10-08T16:20:44.186904887Z" }, { "registry": "npm", "name": "@microsoft/mxc-sdk", "version": "1.0.0", "seenAt": "2026-10-08T16:20:42.947200785Z" } ], "githubStars": 1580, "npmWeekly": 471674, "securityTxt": { "url": "https://microsoft.com/.well-known/security.txt", "state": "expired", "expires": "2026-09-23T16:00:00.000Z", "checkedAt": "2026-10-08T15:39:08.216544687Z" }, "pages": [ { "url": "https://go.microsoft.com/fwlink/?linkid=521839", "kind": "privacy", "status": 0, "checkedAt": "2026-10-08T18:20:40.027295892Z", "changedAt": "0001-01-01T00:00:00Z", "blockedByRobots": true } ], "updatedAt": "2026-10-08T18:20:40.027295892Z" } }, "facts": [ { "a": "HTTP API", "b": "SDK + MCP", "name": "Kind" }, { "a": "Amazon Web Services", "b": "Microsoft", "name": "Vendor" }, { "a": "https://bedrock-agentcore.{region}.amazonaws.com/code-interpreters/{id}/tools/invoke", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "", "name": "Transports" }, { "a": "API key", "b": "None", "name": "Auth" }, { "a": "Pay per use", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the AWS Service Terms. The AgentCore SDKs for Python and TypeScript and the AgentCore MCP server are Apache-2.0", "b": "MIT", "name": "Licence" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-10-07", "b": "2026-10-06", "name": "Last release" }, { "a": "2026-10-01", "b": "no document linked", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "", "name": "Customer content may train models" }, { "a": "yes", "b": "", "name": "Terms restrict automated access" }, { "a": "yes", "b": "", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "776 stars, 335k npm/wk", "b": "1.5k stars, 472k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Microsoft Execution Containers scores 76.3 (BB) on agent readiness against Amazon Bedrock AgentCore Code Interpreter's 73.1 (BB), and leads in 3 of 7 scored categories. Amazon Bedrock AgentCore Code Interpreter leads on security \u0026 auth.", "question": "Which is better for AI agents, Amazon Bedrock AgentCore Code Interpreter or Microsoft Execution Containers?" }, { "answer": "Amazon Bedrock AgentCore Code Interpreter has a hosted endpoint at https://bedrock-agentcore.{region}.amazonaws.com/code-interpreters/{id}/tools/invoke. No hosted endpoint is listed for Microsoft Execution Containers.", "question": "Can an agent call Amazon Bedrock AgentCore Code Interpreter and Microsoft Execution Containers without installing anything?" }, { "answer": "No open-source release is listed for Amazon Bedrock AgentCore Code Interpreter. Microsoft Execution Containers is open source (MIT).", "question": "Are Amazon Bedrock AgentCore Code Interpreter and Microsoft Execution Containers open source?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 87 against 69" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "A team already on AWS that wants agent code to run under IAM, inside a VPC and beside S3 data, for sessions up to eight hours.", "slug": "agentcore-code-interpreter", "watchFor": "No pause, resume or snapshot. Session files are removed when the session ends, and persistence needs a customer-owned S3 Files or EFS mount inside a VPC" }, { "aheadOn": [ "Payments \u0026 pricing, 60 against 30", "Maintenance \u0026 community, 92 against 65", "Transparency \u0026 trust, 83 against 70" ], "also": [ "No key needed to call it", "Open source" ], "goodFor": "A developer building an agent or tool host that must run model-written code on the user's own machine, above all on Windows, where it reaches Microsoft's process and session isolation.", "slug": "microsoft-execution-containers", "watchFor": "1.0.0 shipped on 6 October 2026, and the Node changelog still lists the V1 changes under Unreleased" } ], "job": { "capability": "sandbox.code", "name": "Sandbox code" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agent37-vs-agentcore-code-interpreter.json", "title": "Agent 37 Cloud vs Amazon Bedrock AgentCore Code Interpreter", "url": "https://www.anchorterminal.com/compare/agent37-vs-agentcore-code-interpreter" }, { "json": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-blaxel-sandboxes.json", "title": "Amazon Bedrock AgentCore Code Interpreter vs Blaxel Sandboxes", "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-blaxel-sandboxes" }, { "json": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-cloudflare-sandbox-sdk.json", "title": "Amazon Bedrock AgentCore Code Interpreter vs Cloudflare Sandbox SDK", "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-cloudflare-sandbox-sdk" }, { "json": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-daytona.json", "title": "Amazon Bedrock AgentCore Code Interpreter vs Daytona", "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-daytona" }, { "json": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-deno-sandbox.json", "title": "Amazon Bedrock AgentCore Code Interpreter vs Deno Sandbox", "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-deno-sandbox" }, { "json": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-e2b.json", "title": "Amazon Bedrock AgentCore Code Interpreter vs E2B", "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-e2b" }, { "json": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-freestyle.json", "title": "Amazon Bedrock AgentCore Code Interpreter vs Freestyle", "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-freestyle" }, { "json": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-modal-sandboxes.json", "title": "Amazon Bedrock AgentCore Code Interpreter vs Modal Sandboxes", "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-modal-sandboxes" }, { "json": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-morph-cloud.json", "title": "Amazon Bedrock AgentCore Code Interpreter vs Morph Cloud", "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-morph-cloud" }, { "json": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-runloop.json", "title": "Amazon Bedrock AgentCore Code Interpreter vs Runloop Devboxes", "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-runloop" }, { "json": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-sprites.json", "title": "Amazon Bedrock AgentCore Code Interpreter vs Sprites", "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-sprites" }, { "json": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-together-code-sandbox.json", "title": "Amazon Bedrock AgentCore Code Interpreter vs Together Code Sandbox", "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-together-code-sandbox" }, { "json": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-vercel-sandbox.json", "title": "Amazon Bedrock AgentCore Code Interpreter vs Vercel Sandbox", "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-vercel-sandbox" }, { "json": "https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-microsoft-execution-containers.json", "title": "Blaxel Sandboxes vs Microsoft Execution Containers", "url": "https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-microsoft-execution-containers" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-microsoft-execution-containers.json", "title": "Cloudflare Sandbox SDK vs Microsoft Execution Containers", "url": "https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-microsoft-execution-containers" }, { "json": "https://www.anchorterminal.com/compare/daytona-vs-microsoft-execution-containers.json", "title": "Daytona vs Microsoft Execution Containers", "url": "https://www.anchorterminal.com/compare/daytona-vs-microsoft-execution-containers" }, { "json": "https://www.anchorterminal.com/compare/deno-sandbox-vs-microsoft-execution-containers.json", "title": "Deno Sandbox vs Microsoft Execution Containers", "url": "https://www.anchorterminal.com/compare/deno-sandbox-vs-microsoft-execution-containers" }, { "json": "https://www.anchorterminal.com/compare/e2b-vs-microsoft-execution-containers.json", "title": "E2B vs Microsoft Execution Containers", "url": "https://www.anchorterminal.com/compare/e2b-vs-microsoft-execution-containers" }, { "json": "https://www.anchorterminal.com/compare/freestyle-vs-microsoft-execution-containers.json", "title": "Freestyle vs Microsoft Execution Containers", "url": "https://www.anchorterminal.com/compare/freestyle-vs-microsoft-execution-containers" }, { "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-modal-sandboxes.json", "title": "Microsoft Execution Containers vs Modal Sandboxes", "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-modal-sandboxes" }, { "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-morph-cloud.json", "title": "Microsoft Execution Containers vs Morph Cloud", "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-morph-cloud" }, { "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-runloop.json", "title": "Microsoft Execution Containers vs Runloop Devboxes", "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-runloop" }, { "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-sprites.json", "title": "Microsoft Execution Containers vs Sprites", "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-sprites" }, { "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-together-code-sandbox.json", "title": "Microsoft Execution Containers vs Together Code Sandbox", "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-together-code-sandbox" }, { "json": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-vercel-sandbox.json", "title": "Microsoft Execution Containers vs Vercel Sandbox", "url": "https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-vercel-sandbox" }, { "json": "https://www.anchorterminal.com/compare/agent37-vs-microsoft-execution-containers.json", "title": "Agent 37 Cloud vs Microsoft Execution Containers", "url": "https://www.anchorterminal.com/compare/agent37-vs-microsoft-execution-containers" } ], "scores": [ { "agentcore-code-interpreter": 85, "by": 4, "edge": "agentcore-code-interpreter", "key": "reliability", "microsoft-execution-containers": 81, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "agentcore-code-interpreter": 81, "by": 0, "edge": "", "key": "schema", "microsoft-execution-containers": 81, "name": "Schema \u0026 documentation", "weight": 13 }, { "agentcore-code-interpreter": 75, "by": 1, "edge": "agentcore-code-interpreter", "key": "ergonomics", "microsoft-execution-containers": 74, "name": "Agent ergonomics", "weight": 13 }, { "agentcore-code-interpreter": 87, "by": 18, "edge": "agentcore-code-interpreter", "key": "security", "microsoft-execution-containers": 69, "name": "Security \u0026 auth", "weight": 14 }, { "agentcore-code-interpreter": 30, "by": 30, "edge": "microsoft-execution-containers", "key": "payments", "microsoft-execution-containers": 60, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "agentcore-code-interpreter": 65, "by": 27, "edge": "microsoft-execution-containers", "key": "maintenance", "microsoft-execution-containers": 92, "name": "Maintenance \u0026 community", "weight": 7 }, { "agentcore-code-interpreter": 70, "by": 13, "edge": "microsoft-execution-containers", "key": "transparency", "microsoft-execution-containers": 83, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Microsoft Execution Containers scores 76.3 (BB) on agent readiness against Amazon Bedrock AgentCore Code Interpreter's 73.1 (BB), and leads in 3 of 7 scored categories. Amazon Bedrock AgentCore Code Interpreter leads on security \u0026 auth. Both do sandbox code.", "verdicts": { "agentcore-code-interpreter": "Each session runs in its own microVM with 2 vCPU, 8 GB and a 10 GB disk for up to eight hours, and IAM can scope access to one interpreter. Sessions cannot be paused or resumed, and an AWS account with IAM set-up is needed before a first call.", "microsoft-execution-containers": "MXC puts nine operating-system sandbox backends behind one typed request, with network access denied by default and a JSON Schema for the stable 1.0.0 contract. Version 1.0.0 is two days old as of 8 October 2026. Enforcement varies by backend, and `isolation_session` cannot restrict networking at all." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-microsoft-execution-containers", "json": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-microsoft-execution-containers.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-microsoft-execution-containers.md", "slim": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-microsoft-execution-containers.min.md" }, "markdown": "Microsoft Execution Containers scores 76.3 (BB) on agent readiness against Amazon Bedrock AgentCore Code Interpreter's 73.1 (BB), and leads in 3 of 7 scored categories. Amazon Bedrock AgentCore Code Interpreter leads on security \u0026 auth. Both do sandbox code.\n\n- Amazon Bedrock AgentCore Code Interpreter: grade BB, 73.1/100, rank #89 of 842. Markdown https://www.anchorterminal.com/tools/agentcore-code-interpreter.md · JSON https://www.anchorterminal.com/api/v1/tools/agentcore-code-interpreter.json\n- Microsoft Execution Containers: grade BB, 76.3/100, rank #35 of 842. Markdown https://www.anchorterminal.com/tools/microsoft-execution-containers.md · JSON https://www.anchorterminal.com/api/v1/tools/microsoft-execution-containers.json\n\n## Which one, for what\n\n### Amazon Bedrock AgentCore Code Interpreter (BB)\n\nGood for: A team already on AWS that wants agent code to run under IAM, inside a VPC and beside S3 data, for sessions up to eight hours.\n\nAhead on:\n- Security \u0026 auth, 87 against 69\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No pause, resume or snapshot. Session files are removed when the session ends, and persistence needs a customer-owned S3 Files or EFS mount inside a VPC\n\n### Microsoft Execution Containers (BB)\n\nGood for: A developer building an agent or tool host that must run model-written code on the user's own machine, above all on Windows, where it reaches Microsoft's process and session isolation.\n\nAhead on:\n- Payments \u0026 pricing, 60 against 30\n- Maintenance \u0026 community, 92 against 65\n- Transparency \u0026 trust, 83 against 70\n\nAlso in its favour:\n- No key needed to call it\n- Open source\n\nWatch for: 1.0.0 shipped on 6 October 2026, and the Node changelog still lists the V1 changes under Unreleased\n\n\n## Score by category\n\n| Category | Weight | Amazon Bedrock AgentCore Code Interpreter | Microsoft Execution Containers | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 85 | 81 | Amazon Bedrock AgentCore Code Interpreter +4 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 81 | 81 | even |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 74 | Amazon Bedrock AgentCore Code Interpreter +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 87 | 69 | Amazon Bedrock AgentCore Code Interpreter +18 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 60 | Microsoft Execution Containers +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 65 | 92 | Microsoft Execution Containers +27 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 70 | 83 | Microsoft Execution Containers +13 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **73.1 · BB** | **76.3 · BB** | |\n\n## Facts side by side\n\n| Fact | Amazon Bedrock AgentCore Code Interpreter | Microsoft Execution Containers |\n| --- | --- | --- |\n| Kind | HTTP API | SDK + MCP |\n| Vendor | Amazon Web Services | Microsoft |\n| Hosted endpoint | `https://bedrock-agentcore.{region}.amazonaws.com/code-interpreters/{id}/tools/invoke` | no (local only) |\n| Transports | HTTP | |\n| Auth | API key | None |\n| Pricing | Pay per use | Free |\n| x402 | no | no |\n| Licence | Proprietary service under the AWS Service Terms. The AgentCore SDKs for Python and TypeScript and the AgentCore MCP server are Apache-2.0 | MIT |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | no |\n| Last release | 2026-10-07 | 2026-10-06 |\n| Terms last updated | 2026-10-01 | no document linked |\n| Privacy policy last updated | 2026-05-18 | couldn't be read |\n| Customer content may train models | yes, with an opt-out | |\n| Terms restrict automated access | yes | |\n| Terms restrict benchmarking | yes | |\n| Terms or service can change without notice | yes | |\n| Arbitration or class-action waiver | not found in the text | |\n| Popularity | 776 stars, 335k npm/wk | 1.5k stars, 472k npm/wk |\n\n## Verdicts\n\n**Amazon Bedrock AgentCore Code Interpreter.** Each session runs in its own microVM with 2 vCPU, 8 GB and a 10 GB disk for up to eight hours, and IAM can scope access to one interpreter. Sessions cannot be paused or resumed, and an AWS account with IAM set-up is needed before a first call.\n\n**Microsoft Execution Containers.** MXC puts nine operating-system sandbox backends behind one typed request, with network access denied by default and a JSON Schema for the stable 1.0.0 contract. Version 1.0.0 is two days old as of 8 October 2026. Enforcement varies by backend, and `isolation_session` cannot restrict networking at all.\n\n## Before you call either\n\n### Amazon Bedrock AgentCore Code Interpreter\n\n1. Start a session with `StartCodeInterpreterSession`, then pass its id in the `x-amzn-code-interpreter-session-id` header on every `InvokeCodeInterpreter` call\n2. Set `sessionTimeoutSeconds` when starting. The default is 900 seconds and the maximum is eight hours, and the session ends itself at the timeout\n3. Stop sessions when done. Billing runs per second while code is busy, and a session left open counts against the 1,000 concurrent-session quota\n4. Use `startCommandExecution`, `getTask` and `stopTask` for work longer than the 15-minute synchronous request limit\n5. Retry `ThrottlingException` (429) and `InternalServerException` (500) with exponential backoff, and treat `ServiceQuotaExceededException`, returned as HTTP 402, as a quota to raise\n\n### Microsoft Execution Containers\n\n1. Import from `@microsoft/mxc-sdk/v1`. The package root exports nothing.\n2. Call `getPlatformSupport()` first and stop if `isSupported` is false. `getAvailableBackends()` is advisory and launch-time validation still applies.\n3. Set `network.egress.default` to `allow` only when the task needs it. Omitted network policy resolves to deny in every direction.\n4. Never pass `--audit` to an executor for untrusted code. It turns off all sandbox security for the workload.\n5. Read `ExecutionResult.warnings` after each run. Security warnings arrive there and are not written to stdout or stderr.\n\n## Questions\n\n### Which is better for AI agents, Amazon Bedrock AgentCore Code Interpreter or Microsoft Execution Containers?\n\nMicrosoft Execution Containers scores 76.3 (BB) on agent readiness against Amazon Bedrock AgentCore Code Interpreter's 73.1 (BB), and leads in 3 of 7 scored categories. Amazon Bedrock AgentCore Code Interpreter leads on security \u0026 auth.\n\n### Can an agent call Amazon Bedrock AgentCore Code Interpreter and Microsoft Execution Containers without installing anything?\n\nAmazon Bedrock AgentCore Code Interpreter has a hosted endpoint at https://bedrock-agentcore.{region}.amazonaws.com/code-interpreters/{id}/tools/invoke. No hosted endpoint is listed for Microsoft Execution Containers.\n\n### Are Amazon Bedrock AgentCore Code Interpreter and Microsoft Execution Containers open source?\n\nNo open-source release is listed for Amazon Bedrock AgentCore Code Interpreter. Microsoft Execution Containers is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-microsoft-execution-containers.json, and with the fewest tokens: https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-microsoft-execution-containers.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"agentcore-code-interpreter\", \"b\": \"microsoft-execution-containers\"}`. From a terminal: `anchor compare agentcore-code-interpreter microsoft-execution-containers`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/agentcore-code-interpreter.json and https://www.anchorterminal.com/api/v1/tools/microsoft-execution-containers.json\n\n## Other comparisons with Amazon Bedrock AgentCore Code Interpreter or Microsoft Execution Containers\n\n- [Agent 37 Cloud vs Amazon Bedrock AgentCore Code Interpreter](https://www.anchorterminal.com/compare/agent37-vs-agentcore-code-interpreter.md)\n- [Amazon Bedrock AgentCore Code Interpreter vs Blaxel Sandboxes](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-blaxel-sandboxes.md)\n- [Amazon Bedrock AgentCore Code Interpreter vs Cloudflare Sandbox SDK](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-cloudflare-sandbox-sdk.md)\n- [Amazon Bedrock AgentCore Code Interpreter vs Daytona](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-daytona.md)\n- [Amazon Bedrock AgentCore Code Interpreter vs Deno Sandbox](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-deno-sandbox.md)\n- [Amazon Bedrock AgentCore Code Interpreter vs E2B](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-e2b.md)\n- [Amazon Bedrock AgentCore Code Interpreter vs Freestyle](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-freestyle.md)\n- [Amazon Bedrock AgentCore Code Interpreter vs Modal Sandboxes](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-modal-sandboxes.md)\n- [Amazon Bedrock AgentCore Code Interpreter vs Morph Cloud](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-morph-cloud.md)\n- [Amazon Bedrock AgentCore Code Interpreter vs Runloop Devboxes](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-runloop.md)\n- [Amazon Bedrock AgentCore Code Interpreter vs Sprites](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-sprites.md)\n- [Amazon Bedrock AgentCore Code Interpreter vs Together Code Sandbox](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-together-code-sandbox.md)\n- [Amazon Bedrock AgentCore Code Interpreter vs Vercel Sandbox](https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-vercel-sandbox.md)\n- [Blaxel Sandboxes vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/blaxel-sandboxes-vs-microsoft-execution-containers.md)\n- [Cloudflare Sandbox SDK vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/cloudflare-sandbox-sdk-vs-microsoft-execution-containers.md)\n- [Daytona vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/daytona-vs-microsoft-execution-containers.md)\n- [Deno Sandbox vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/deno-sandbox-vs-microsoft-execution-containers.md)\n- [E2B vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/e2b-vs-microsoft-execution-containers.md)\n- [Freestyle vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/freestyle-vs-microsoft-execution-containers.md)\n- [Microsoft Execution Containers vs Modal Sandboxes](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-modal-sandboxes.md)\n- [Microsoft Execution Containers vs Morph Cloud](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-morph-cloud.md)\n- [Microsoft Execution Containers vs Runloop Devboxes](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-runloop.md)\n- [Microsoft Execution Containers vs Sprites](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-sprites.md)\n- [Microsoft Execution Containers vs Together Code Sandbox](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-together-code-sandbox.md)\n- [Microsoft Execution Containers vs Vercel Sandbox](https://www.anchorterminal.com/compare/microsoft-execution-containers-vs-vercel-sandbox.md)\n- [Agent 37 Cloud vs Microsoft Execution Containers](https://www.anchorterminal.com/compare/agent37-vs-microsoft-execution-containers.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Amazon Bedrock AgentCore Code Interpreter vs Microsoft Execution Containers", "url": "" } ], "description": "Microsoft Execution Containers scores 76.3 (BB) on agent readiness against Amazon Bedrock AgentCore Code Interpreter's 73.1 (BB), and leads in 3 of 7 scored categories. Amazon Bedrock AgentCore Code Interpreter leads on security \u0026 auth. Both do sandbox code. Category scores…", "facts": [ "Amazon Bedrock AgentCore Code Interpreter BB 73.1", "Microsoft Execution Containers BB 76.3", "scores" ], "h1": "Amazon Bedrock AgentCore Code Interpreter vs Microsoft Execution Containers", "image": "https://www.anchorterminal.com/assets/og/compare-agentcore-code-interpreter-vs-microsoft-execution-containers.png", "path": "/compare/agentcore-code-interpreter-vs-microsoft-execution-containers", "published": "2026-10-01", "section": "tools", "title": "Amazon Bedrock AgentCore Code Interpreter vs Microsoft Execution…", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/agentcore-code-interpreter-vs-microsoft-execution-containers" }, "tokens": { "markdown": 3100, "slim": 830 }, "version": 1 }