---
title: "Guild vs Claude Managed Agents"
description: "Guild vs Claude Managed Agents: sandboxes, tools, credentials, approvals, schedules, models, and pricing compared, plus how to move an agent to Guild."
canonical: "https://www.guild.ai/compare/claude-managed-agents"
---

# Guild vs Claude Managed Agents

Guild vs Claude Managed Agents: sandboxes, tools, credentials, approvals, schedules, models, and pricing compared, plus how to move an agent to Guild.

Claude Managed Agents runs Claude agents for you, each session in its own sandbox. Guild runs agents on any major model, Claude included, keeps secrets out of agent code, and starts agents from Slack, GitHub, a schedule, or an API call.

Last verified 2026-10-30. Across 35 features, Guild leads on 13, Claude Managed Agents on 5, and 17 are level. Every cell below names its source.

## When to choose Claude Managed Agents

- You only use Claude and want Anthropic to run the agent for you.
- Your agents do long, open-ended work, like research or code changes, and need a shell and files.
- You want tools to run on your own infrastructure while Anthropic runs the agent.
- You want built-in grading, memory, or work that fans out to many sub-agents.
- You want published pricing: Claude token rates plus $0.08 per session-hour.

## When to choose Guild

- You want models from Anthropic, OpenAI, Google, and others, with a backup if one fails.
- Your team builds agents more than one way: TypeScript, plain instructions, Goose, OpenClaw, or LangGraph.
- You need each agent to get only the access it needs, down to single actions.
- Agents should start from Slack, GitHub, or Zendesk without glue code.
- You want to share, version, and reuse agents on a public Agent Hub.

## What Claude Managed Agents and Guild are

**Claude Managed Agents.** Anthropic runs the agent and a fresh sandbox for every session. Secrets are added only to outbound calls, tool calls can pause for approval, and schedules, spend caps, and sub-agents are built in. It's in beta and runs Claude models only.

**Guild.** Guild runs agents built several ways, on models from several providers. Secrets stay out of agent code, you decide which actions each agent can take, and agents start from Slack, GitHub, Zendesk, a schedule, or an API call. Teams share agents on the Agent Hub.

|   | Claude Managed Agents | Guild |
| --- | --- | --- |
| Category | Hosted agent harness (Claude Platform) | One platform to run and control AI agents |
| License | Proprietary platform; SDKs and ant CLI Apache-2.0 | Proprietary platform; CLI published on npm as @guildai/cli |
| Pricing | Claude token rates plus $0.08 per session-hour of running time | No public price list; plans priced with the Guild team; model usage metered at list price |
| Maturity | Beta (launched 2026-04-08; managed-agents-2026-04-01 header) | Generally available |
| Docs | https://platform.claude.com/docs/en/managed-agents/overview | https://docs.guild.ai |

## Concept map: Claude Managed Agents to Guild

| Concept | Claude Managed Agents | Guild | Note |
| --- | --- | --- | --- |
| The agent | `POST /v1/agents` with `model`, `system`, `tools`, `mcp_servers`, `skills` (or an `agent.md` for `ant apply`) | A Native agent (`PROMPT.md` + `guild.yaml`), or TypeScript `agent()` / `llmAgent()` |   |
| Versions | Immutable agent versions; sessions pin to one | Semver versions on the Agent Hub (`guild agent save --publish`) |   |
| A run | Session (`POST /v1/sessions`) | Session |   |
| Run history | Session event stream and the Console session viewer | Sessions and the session event log |   |
| Sandbox with shell and files | Environment (cloud container) + `agent_toolset_20260401` | The OpenClaw agent type: `AGENTS.md` + `skills/`, with shell, git, and files | Guild containers have no direct network; outbound calls go through Guild proxies. |
| Network rules | Environment `networking`: `unrestricted` or `limited` with `allowed_hosts` | No direct network by default; integrations reach out through the credential proxy |   |
| Custom tools | Custom tools your app runs on `agent.custom_tool_use` | The `tools` object in `agent.ts`, run by Guild |   |
| MCP servers | `mcp_servers` + `mcp_toolset` | Guild integrations built from MCP servers (`guild integration`) |   |
| Credentials | Vaults and credentials, attached per session with `vault_ids` | Credentials scoped to an account, workspace, member, or agent, plus credential policies | Secrets stay in the credential proxy. |
| Approvals | Permission policies: `always_ask` or `auto` | Approval gates, set in the Guild UI per agent and per action |   |
| Sub-agents | Multiagent roster and session threads | `guildAgentTool({ calls: 'owner~agent' })`, or `sub_agents` in `guild.yaml` |   |
| Schedules | Scheduled deployments (cron + timezone) | A schedule trigger: `guild trigger create --type time` |   |
| Starting from events | Your code calls the API; webhooks notify you of session changes | Event triggers (Slack mention, GitHub PR, Zendesk ticket) and API triggers |   |
| Skills | Anthropic and custom skills, or `.claude/skills` in a mounted repo | Hub skills (`guild skill`), or skills inside OpenClaw and Goose agents |   |
| Quality checks | Outcomes: a rubric and a grader per session | `guild agent test` and Guild Evaluations |   |
| Spend caps | Session budgets (hard dollar cap per session) | Per-agent and per-workspace spend budgets |   |
| Config as code | `ant apply` and `claude-lock.json` | `guild agent init` + `guild agent save` from CI |   |
| Memory across sessions | Memory stores attached to a session | Sessions; `task.save` / `task.restore` for TypeScript state | No shared memory store equivalent confirmed; check before migrating. |

## Feature by feature: Claude Managed Agents vs. Guild

### Authoring

| Feature | Claude Managed Agents | Guild |
| --- | --- | --- |
| Code-first TypeScript agents | **Partial.** The TypeScript SDK (client.beta.agents, client.beta.sessions) creates agents as versioned config: model, system prompt, tools, MCP servers, skills. Anthropic runs the loop; your code only runs custom tools. ([source](https://platform.claude.com/docs/en/managed-agents/agent-setup.md), checked 2026-10-30) | **Yes.** @guildai/agents-sdk: agent(), llmAgent(), and the task API (task.llm, task.tools, task.ui, task.gather). ([source](https://docs.guild.ai/packages/agents-sdk.md), checked 2026-10-23) |
| Python / LangGraph agents | **No.** No LangGraph hosting. Agents are Anthropic's own harness configured through the API; Python appears only as an SDK for calling it. ([source](https://platform.claude.com/docs/en/managed-agents/overview.md), checked 2026-10-30) | **Yes.** LangGraph agent type: langgraph.json + graph.py using guild_model() and guild_tools(). LangChain v1, Python 3.13, no extra pip packages. ([source](https://docs.guild.ai/guide/agent-types.md), checked 2026-10-23) |
| Instruction-only (no-code) agents | **Yes.** The Console agent builder sets model, system prompt, MCP servers, tools, and skills, with an inline test session runner. ([source](https://platform.claude.com/docs/en/managed-agents/onboarding.md), checked 2026-10-30) | **Yes.** Native agents: PROMPT.md + guild.yaml, no container, ready immediately. ([source](https://docs.guild.ai/guide/agent-types.md), checked 2026-10-23) |
| Several agent formats on one platform | **No.** One agent definition (model, system, tools, MCP servers, skills) run by Anthropic's harness. ([source](https://platform.claude.com/docs/en/managed-agents/overview.md), checked 2026-10-30) | **Yes.** Native, TypeScript, Goose, OpenClaw, and LangGraph agent types, plus ADK (CLI 0.28). ([source](https://docs.guild.ai/guide/agent-types.md), checked 2026-10-23) |
| Typed agent input/output | **Partial.** Custom tools declare a JSON Schema input_schema, and outcomes grade a deliverable against a rubric. No schema for the agent's own input or output is documented. ([source](https://platform.claude.com/docs/en/managed-agents/tools.md), checked 2026-10-30) | **Yes.** Zod inputSchema and outputSchema on agent(); root input must be z.object. ([source](https://docs.guild.ai/packages/agents-sdk.md), checked 2026-10-23) |
| Repo / workspace agents (shell, git, files) | **Yes.** Each session gets its own Linux container with bash and read, write, edit, glob, and grep tools; GitHub repositories can be mounted, with the GitHub MCP for pull requests. ([source](https://platform.claude.com/docs/en/managed-agents/github.md), checked 2026-10-30) | **Yes.** OpenClaw agents (AGENTS.md + skills/) run in the guildai~lobsterpot container with shell, git, and file editing. ([source](https://docs.guild.ai/guide/agent-types.md), checked 2026-10-23) |
| Sub-agents and agent-to-agent calls | **Yes.** Multiagent orchestration: a roster of predefined or inline agents the session delegates to on separate threads, plus dynamic workflows for large fan-out work and an optional advisor model. ([source](https://platform.claude.com/docs/en/managed-agents/multiagent-orchestration.md), checked 2026-10-30) | **Yes.** guildAgentTool calls owner~agent; Native, Goose, and OpenClaw agents declare sub_agents in guild.yaml. ([source](https://docs.guild.ai/guide/guild-yaml.md), checked 2026-10-23) |

### Tools & integrations

| Feature | Claude Managed Agents | Guild |
| --- | --- | --- |
| Managed integrations catalog | **Partial.** Built-in toolset (bash, files, web search, web fetch) and pre-built Anthropic skills (pptx, xlsx, docx, pdf). Third-party systems connect as remote MCP servers you add by URL; no managed connector catalog is documented. ([source](https://platform.claude.com/docs/en/managed-agents/onboarding.md), checked 2026-10-30) | **Yes.** 37 non-model integrations (GitHub, Slack, Gmail, Linear, Jira, Notion, Zendesk, …) plus 8 model publishers. ([source](https://docs.guild.ai/integrations/overview.md), checked 2026-10-23) |
| Use MCP servers as tools | **Yes.** mcp_servers on the agent plus an mcp_toolset per server; remote streamable-HTTP servers, or private servers through MCP tunnels (research preview). ([source](https://platform.claude.com/docs/en/managed-agents/mcp-connector.md), checked 2026-10-30) | **Yes.** Build custom integrations from MCP servers with guild integration. ([source](https://docs.guild.ai/integrations/overview.md), checked 2026-10-23) |
| Platform exposed over MCP | **No.** No MCP server exposing agents or sessions is documented. The MCP server at platform.claude.com/docs/mcp searches the docs only. ([source](https://platform.claude.com/llms.txt), checked 2026-10-30) | **Yes.** Guild is an MCP server: https://api.guild.ai/mcp (OAuth + PKCE) or local `guild mcp`. ([source](https://docs.guild.ai/api-reference/mcp.md), checked 2026-10-23) |
| Custom APIs from OpenAPI | **No.** No OpenAPI import; use custom tools (JSON Schema) or an MCP server. ([source](https://platform.claude.com/docs/en/managed-agents/tools.md), checked 2026-10-30) | **Yes.** guild integration builds tools from OpenAPI specs; Porter drafts integrations from public APIs. ([source](https://docs.guild.ai/integrations/overview.md), checked 2026-10-23) |
| Secrets never reach the agent | **Yes.** Vaults hold MCP OAuth, bearer, and environment-variable credentials. Environment-variable secrets sit in the sandbox as placeholders and are substituted at egress, so the agent never sees the real value. ([source](https://platform.claude.com/docs/en/managed-agents/vaults.md), checked 2026-10-30) | **Yes.** A credential proxy injects auth server-side; GitHub uses short-lived GitHub App tokens. ([source](https://docs.guild.ai/platform/credentials.md), checked 2026-10-23) |
| Per-operation credential policies | **Partial.** Each vault credential can be limited to allowed_hosts, and individual MCP tools can be disabled or given their own permission policy. No ALLOW/DENY rules by operation and resource on a credential. ([source](https://platform.claude.com/docs/en/managed-agents/vaults.md), checked 2026-10-30) | **Yes.** ALLOW/DENY rules by operation, resource, agent, and workspace; DENY wins. ([source](https://docs.guild.ai/platform/credential-policies.md), checked 2026-10-23) |
| Act as the invoking user | **Yes.** A vault is the set of credentials for one end user, attached per session with vault_ids, so the same agent acts with each user's own accounts. ([source](https://platform.claude.com/docs/en/managed-agents/vaults.md), checked 2026-10-30) | **Yes.** Member-scoped credentials plus identity mapping for Slack and GitHub users. ([source](https://docs.guild.ai/platform/credentials.md), checked 2026-10-23) |

### Runtime & triggers

| Feature | Claude Managed Agents | Guild |
| --- | --- | --- |
| Managed hosted runtime | **Yes.** Anthropic runs the agent loop and a per-session cloud sandbox; you send events and stream results over SSE. ([source](https://platform.claude.com/docs/en/managed-agents/overview.md), checked 2026-10-30) | **Yes.** Guild hosts and runs all agent types. ([source](https://docs.guild.ai/platform/security-architecture.md), checked 2026-10-23) |
| Self-host option | **Partial.** Self-hosted sandboxes move tool execution to your infrastructure via an environment worker; the agent loop, model calls, skills, and memory stores stay with Anthropic. ([source](https://platform.claude.com/docs/en/managed-agents/self-hosted-sandboxes.md), checked 2026-10-30) | **No.** Hosted only; no self-host option documented. ([source](https://docs.guild.ai/platform/security-architecture.md), checked 2026-10-23) |
| Sandboxed, network-controlled execution | **Yes.** Each session runs in its own fresh container; environments set networking to unrestricted or limited with allowed_hosts and optional package-manager access. ([source](https://platform.claude.com/docs/en/managed-agents/environments.md), checked 2026-10-30) | **Yes.** Containers lose network access before the agent runs; only Guild proxies can reach out. ([source](https://docs.guild.ai/platform/security-architecture.md), checked 2026-10-23) |
| Durable long-running runs | **Yes.** Sessions are stateful and persist server-side: they go idle and resume on the next message, retry transient errors automatically (rescheduling), and keep the sandbox filesystem and history. ([source](https://platform.claude.com/docs/en/managed-agents/session-operations.md), checked 2026-10-30) | **Partial.** Multi-turn sessions; they can be interrupted but not resumed. ([source](https://docs.guild.ai/llms.txt), checked 2026-10-23) |
| Schedules (cron) | **Yes.** Scheduled deployments run sessions on a cron expression with a timezone, at minute granularity, plus manual runs. ([source](https://platform.claude.com/docs/en/managed-agents/scheduled-deployments.md), checked 2026-10-30) | **Partial.** CLI supports --frequency CRON --cron-expression; docs list hourly–monthly presets. ([source](https://docs.guild.ai/platform/triggers.md), checked 2026-10-23) |
| Webhook, event & API triggers | **Partial.** Sessions start from the REST API or a deployment's run endpoint. Webhooks are outbound notifications (session, deployment, vault events); no built-in inbound triggers from SaaS events. ([source](https://platform.claude.com/docs/en/managed-agents/webhooks.md), checked 2026-10-30) | **Yes.** Event triggers (Slack mention, GitHub PR, Zendesk ticket, …) and API triggers. ([source](https://docs.guild.ai/platform/triggers.md), checked 2026-10-23) |
| Chat channels (Slack, Teams, …) | **No.** No built-in Slack or Teams channel. Anthropic's quickstarts show a chat app built with Vercel's Chat SDK whose adapters you host to reach Slack, Teams, Discord, or WhatsApp. ([source](https://platform.claude.com/docs/en/managed-agents/quickstart.md), checked 2026-10-30) | **Yes.** Slack event triggers; Discord, Telegram, and Twilio integrations. ([source](https://docs.guild.ai/integrations/overview.md), checked 2026-10-23) |

### Control & governance

| Feature | Claude Managed Agents | Guild |
| --- | --- | --- |
| Per-tool-call approval gate | **Yes.** Permission policies per toolset or tool: always_allow, always_ask (session pauses for a tool_confirmation), or auto (server runs, denies as high-risk, or pauses). ([source](https://platform.claude.com/docs/en/managed-agents/permission-policies.md), checked 2026-10-30) | **Yes.** Approval gates are set in the Guild UI, per agent and per action: when the agent reaches a gated action, the run pauses until a designated human approves. No code needed. ([source](https://www.guild.ai/product/ai-governance), checked 2026-10-23) |
| Roles & access control | **Partial.** Workspace roles (User, Limited Developer, Developer, Admin); vaults and credentials are workspace-scoped. No per-agent sharing or access rules documented. ([source](https://platform.claude.com/docs/en/manage-claude/workspaces.md), checked 2026-10-30) | **Partial.** Admin and Member org roles, restricted workspaces, and scoped API keys. ([source](https://docs.guild.ai/llms.txt), checked 2026-10-23) |
| Audit log | **Partial.** Session event history is persisted and inspectable; the Compliance API Activity Feed records Console and API actions. No agent-specific immutable audit log is documented. ([source](https://platform.claude.com/docs/en/manage-claude/compliance-activity-feed.md), checked 2026-10-30) | **Yes.** Immutable, CSV-exportable audit log (admins). ([source](https://docs.guild.ai/llms.txt), checked 2026-10-23) |
| Runtime guardrails & scanning | **Partial.** The auto permission policy has the server evaluate each tool call and deny high-risk ones; model safety classifiers apply. No PII or custom policy scanning documented. ([source](https://platform.claude.com/docs/en/managed-agents/permission-policies.md), checked 2026-10-30) | **No.** No prompt or tool-call scanning documented; isolation comes from the network-less runtime and credential policies. ([source](https://docs.guild.ai/platform/security-architecture.md), checked 2026-10-23) |
| Spend budgets & usage limits | **Yes.** Session budgets are hard dollar caps that pause a session at its limit, also settable per deployment run; workspace spend and rate limits in the Console. ([source](https://platform.claude.com/docs/en/managed-agents/budgets.md), checked 2026-10-30) | **Yes.** Per-agent and per-workspace spend budgets, model allowlists, and daily token limits. ([source](https://docs.guild.ai/llms.txt), checked 2026-10-23) |
| Multi-provider models with fallbacks | **No.** Claude models only (Fable, Opus, Sonnet, Haiku), one per agent with per-session overrides; no other providers or automatic fallback documented. ([source](https://platform.claude.com/docs/en/managed-agents/overview.md), checked 2026-10-30) | **Yes.** guild.yaml models is an ordered fallback list across Anthropic, OpenAI, Gemini, Meta, DeepSeek, and more; BYO keys supported. ([source](https://docs.guild.ai/guide/guild-yaml.md), checked 2026-10-23) |

### Observability

| Feature | Claude Managed Agents | Guild |
| --- | --- | --- |
| Run traces | **Yes.** Console session viewer: timeline, transcript with thinking and tool calls, raw events, per-tool stats, threads; OpenTelemetry export in beta. ([source](https://platform.claude.com/docs/en/managed-agents/session-observability.md), checked 2026-10-30) | **Yes.** Session event log of LLM calls, tool calls, sub-tasks, and container logs; also via the API. ([source](https://docs.guild.ai/llms.txt), checked 2026-10-23) |
| Evaluations | **Partial.** Outcomes give a session a rubric and a separate grader that iterates the agent until it passes. No dataset-based eval runs for agents documented. ([source](https://platform.claude.com/docs/en/managed-agents/define-outcomes.md), checked 2026-10-30) | **Partial.** Evaluations with samples, checks, and llmJudge; enabled per account, no CLI command yet. ([source](https://docs.guild.ai/platform/evaluations.md), checked 2026-10-23) |
| Cost & usage tracking | **Yes.** Per-session usage and list cost on the session object and in the Console; usage grouped by agent on the Usage page and in the usage APIs. ([source](https://platform.claude.com/docs/en/managed-agents/session-observability.md), checked 2026-10-30) | **Yes.** Insights and Spend Explorer. ([source](https://docs.guild.ai/llms.txt), checked 2026-10-23) |

### Ecosystem & business

| Feature | Claude Managed Agents | Guild |
| --- | --- | --- |
| Public agent hub (install & fork) | **No.** No public agent hub. The Console offers quickstart templates, and Anthropic publishes example skills on GitHub. ([source](https://platform.claude.com/docs/en/managed-agents/onboarding.md), checked 2026-10-30) | **Yes.** Agent Hub: Draft, Internal, or Public; owner~name with semver; install and fork (guild agent init --fork). ([source](https://docs.guild.ai/platform/publish-to-agent-hub.md), checked 2026-10-23) |
| Reusable skills | **Yes.** Pre-built Anthropic skills and custom skills uploaded to the workspace, or loaded from a mounted GitHub repository's .claude/skills. ([source](https://platform.claude.com/docs/en/managed-agents/skills.md), checked 2026-10-30) | **Yes.** Hub skills, `guild skill`, and skills inside Goose and OpenClaw agents. ([source](https://docs.guild.ai/cli/commands.md), checked 2026-10-23) |
| Full lifecycle CLI | **Yes.** The ant CLI: ant apply syncs agents, environments, skills, memory stores, deployments, and vaults from files; ant beta:sessions connect follows a live session; ant beta:worker runs self-hosted workers. ([source](https://platform.claude.com/docs/en/cli-sdks-libraries/cli/apply.md), checked 2026-10-30) | **Yes.** 17 top-level commands: init, test, save --publish, workspace chat, trigger, integration, skill, session, and more. ([source](https://docs.guild.ai/cli/commands.md), checked 2026-10-23) |
| Open-source core | **No.** The platform is proprietary. The client SDKs and ant CLI are open source (Apache 2.0 since 2026-10-21). ([source](https://platform.claude.com/docs/en/release-notes/overview.md), checked 2026-10-30) | **No.** Proprietary platform; the CLI is published on npm. ([source](https://docs.guild.ai/llms.txt), checked 2026-10-23) |
| Public pricing | **Yes.** Tokens at standard model rates plus $0.08 per session-hour while a session is running; web search $10 per 1,000. ([source](https://platform.claude.com/docs/en/about-claude/pricing.md), checked 2026-10-30) | **Partial.** No public price list: plans are priced with the Guild team; model usage is metered at list price. ([source](https://docs.guild.ai/reference/pricing.md), checked 2026-10-23) |

## Frequently asked questions

### What is the difference between Guild and Claude Managed Agents?

Claude Managed Agents is Anthropic's hosted service for running Claude as an agent: each session gets its own sandbox with a shell, files, web tools, MCP servers, and skills. Guild runs agents built several ways on models from several providers, keeps secrets out of agent code, starts agents from events, schedules, or API calls, and shares them on a public Agent Hub.

### Is Guild an alternative to Claude Managed Agents?

For some teams. If you only use Claude and want Anthropic to run long tasks in a sandbox, Managed Agents is the more direct fit. Guild fits better when you use several models or ways of building agents, need to control which actions each agent can take, want agents to start from Slack, GitHub, or Zendesk, or want to share agents on a public Hub.

### Can I use Claude models on Guild?

Yes. Anthropic is one of Guild's model providers, and each agent lists its models in order, so Claude can come first with another provider as a backup. You can also bring your own keys. Managed Agents runs Claude models only and documents no automatic backup to another provider.

### How do I move a Claude Managed Agents agent to Guild?

Copy the agent's system prompt, model, and skills into a Guild Native agent (PROMPT.md and guild.yaml), or an OpenClaw agent if it needs a shell and files. MCP servers become Guild integrations, vault credentials become Guild credentials, permission policies become approval steps, scheduled deployments become schedule triggers, and multiagent rosters become sub-agents. Test with guild agent test before you publish.

### How much does Claude Managed Agents cost?

As of October 2026, Managed Agents bills Claude tokens at standard model rates plus $0.08 per session-hour, counted only while a session is running. Web search costs $10 per 1,000 searches. Guild doesn't publish a price list: plans are priced with the Guild team, and model usage is metered at list price.

### Is Claude Managed Agents production-ready?

Not yet: it's in beta as of October 2026. Anthropic launched it on April 8, 2026, every call needs a beta header, and behavior may change between releases. It isn't eligible for zero data retention or HIPAA BAA coverage, because sessions keep their history on Anthropic's servers until you delete them.

### Can I self-host Claude Managed Agents or Guild?

Partly, for Managed Agents: self-hosted sandboxes run tools on your infrastructure, but the agent itself, model calls, skills, and memory stay with Anthropic. Guild is hosted only as of October 2026, and its agents run in containers with no direct network access.

## Sources

- [platform.claude.com/docs/en/managed-agents/agent-setup](https://platform.claude.com/docs/en/managed-agents/agent-setup.md)
- [platform.claude.com/docs/en/managed-agents/overview](https://platform.claude.com/docs/en/managed-agents/overview.md)
- [platform.claude.com/docs/en/managed-agents/onboarding](https://platform.claude.com/docs/en/managed-agents/onboarding.md)
- [platform.claude.com/docs/en/managed-agents/tools](https://platform.claude.com/docs/en/managed-agents/tools.md)
- [platform.claude.com/docs/en/managed-agents/github](https://platform.claude.com/docs/en/managed-agents/github.md)
- [platform.claude.com/docs/en/managed-agents/multiagent-orchestration](https://platform.claude.com/docs/en/managed-agents/multiagent-orchestration.md)
- [platform.claude.com/docs/en/managed-agents/mcp-connector](https://platform.claude.com/docs/en/managed-agents/mcp-connector.md)
- [platform.claude.com/llms.txt](https://platform.claude.com/llms.txt)
- [platform.claude.com/docs/en/managed-agents/vaults](https://platform.claude.com/docs/en/managed-agents/vaults.md)
- [platform.claude.com/docs/en/managed-agents/self-hosted-sandboxes](https://platform.claude.com/docs/en/managed-agents/self-hosted-sandboxes.md)
- [platform.claude.com/docs/en/managed-agents/environments](https://platform.claude.com/docs/en/managed-agents/environments.md)
- [platform.claude.com/docs/en/managed-agents/session-operations](https://platform.claude.com/docs/en/managed-agents/session-operations.md)
- [platform.claude.com/docs/en/managed-agents/scheduled-deployments](https://platform.claude.com/docs/en/managed-agents/scheduled-deployments.md)
- [platform.claude.com/docs/en/managed-agents/webhooks](https://platform.claude.com/docs/en/managed-agents/webhooks.md)
- [platform.claude.com/docs/en/managed-agents/quickstart](https://platform.claude.com/docs/en/managed-agents/quickstart.md)
- [platform.claude.com/docs/en/managed-agents/permission-policies](https://platform.claude.com/docs/en/managed-agents/permission-policies.md)
- [platform.claude.com/docs/en/manage-claude/workspaces](https://platform.claude.com/docs/en/manage-claude/workspaces.md)
- [platform.claude.com/docs/en/manage-claude/compliance-activity-feed](https://platform.claude.com/docs/en/manage-claude/compliance-activity-feed.md)
- [platform.claude.com/docs/en/managed-agents/budgets](https://platform.claude.com/docs/en/managed-agents/budgets.md)
- [platform.claude.com/docs/en/managed-agents/session-observability](https://platform.claude.com/docs/en/managed-agents/session-observability.md)
- [platform.claude.com/docs/en/managed-agents/define-outcomes](https://platform.claude.com/docs/en/managed-agents/define-outcomes.md)
- [platform.claude.com/docs/en/managed-agents/skills](https://platform.claude.com/docs/en/managed-agents/skills.md)
- [platform.claude.com/docs/en/cli-sdks-libraries/cli/apply](https://platform.claude.com/docs/en/cli-sdks-libraries/cli/apply.md)
- [platform.claude.com/docs/en/release-notes/overview](https://platform.claude.com/docs/en/release-notes/overview.md)
- [platform.claude.com/docs/en/about-claude/pricing](https://platform.claude.com/docs/en/about-claude/pricing.md)
- [docs.guild.ai/packages/agents-sdk](https://docs.guild.ai/packages/agents-sdk.md)
- [docs.guild.ai/guide/agent-types](https://docs.guild.ai/guide/agent-types.md)
- [docs.guild.ai/guide/guild-yaml](https://docs.guild.ai/guide/guild-yaml.md)
- [docs.guild.ai/integrations/overview](https://docs.guild.ai/integrations/overview.md)
- [docs.guild.ai/api-reference/mcp](https://docs.guild.ai/api-reference/mcp.md)
- [docs.guild.ai/platform/credentials](https://docs.guild.ai/platform/credentials.md)
- [docs.guild.ai/platform/credential-policies](https://docs.guild.ai/platform/credential-policies.md)
- [docs.guild.ai/platform/security-architecture](https://docs.guild.ai/platform/security-architecture.md)
- [docs.guild.ai/llms.txt](https://docs.guild.ai/llms.txt)
- [docs.guild.ai/platform/triggers](https://docs.guild.ai/platform/triggers.md)
- [guild.ai/product/ai-governance](https://www.guild.ai/product/ai-governance)
- [docs.guild.ai/platform/evaluations](https://docs.guild.ai/platform/evaluations.md)
- [docs.guild.ai/platform/publish-to-agent-hub](https://docs.guild.ai/platform/publish-to-agent-hub.md)
- [docs.guild.ai/cli/commands](https://docs.guild.ai/cli/commands.md)
- [docs.guild.ai/reference/pricing](https://docs.guild.ai/reference/pricing.md)

## Other comparisons

- [Guild vs. AWS](https://www.guild.ai/compare/aws)
- [Guild vs. LangChain](https://www.guild.ai/compare/langchain)
- [Guild vs. Runlayer](https://www.guild.ai/compare/runlayer)
- [Guild vs. Arcade](https://www.guild.ai/compare/arcade)
- [Guild vs. Vercel eve](https://www.guild.ai/compare/vercel-eve)
- [All comparisons](https://www.guild.ai/compare)
- [Book a demo](https://www.guild.ai/talk-to-sales)