> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentscope.io/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For AgentScope Python, use https://docs.agentscope.io/stable/en/index for new projects. For existing projects, check the installed agentscope version and use matching versioned documentation.
> The /latest/ alias points to the newest documentation and may move ahead of /stable/ when a development version exists. Do not mix AgentScope 1.x and 2.x APIs.
> State the AgentScope version when providing installation commands or code examples. ReMe uses its own continuously updated /reme/latest/ documentation.

# FAQ

> Frequently asked questions about AgentScope v2.0

> [accordion] Is AgentScope 2.0 compatible with 1.0?
>
> No. AgentScope 2.0 is a breaking release that introduces a redesigned agent abstraction, a new event system, the workspace and permission systems, and many other new features. APIs are not source-compatible with 1.0, and there is no automatic migration path.
>
> We recommend upgrading to 2.0 for all new projects to benefit from the new capabilities. The 1.0 documentation remains available for existing users.

> [accordion] Does AgentScope support sandboxed execution?
>
> Yes. The **workspace** abstraction is AgentScope's execution environment for agents and ships three implementations — `LocalWorkspace` (host filesystem), `DockerWorkspace` (container), and `E2BWorkspace` (E2B cloud sandbox) — sharing the same interface so the same agent code runs against any backend. Workspaces also own MCP server lifecycles, skill management, and context offloading.
>
> See [Workspace](https://docs.agentscope.io/en/versions/2.0.4/building-blocks/workspace.md) for the full overview, including how to plug a workspace into an `Agent` and the multi-tenant `WorkspaceManager`.

> [accordion] Is there a frontend for AgentScope 2.0?
>
> Yes, on two layers:
>
> * **TypeScript SDK** — install with `pnpm install @agentscope-ai/agentscope`. It mirrors the Python `Msg` and `Event` types so frontend code can consume agent streams without re-implementing the protocol.
> * **Frontend UI** — a ready-to-use web app for [Agent Service](https://docs.agentscope.io/en/versions/2.0.4/deploy/agent-service.md), letting developers exercise their deployed agents without writing any UI code.

> [accordion] Will RAG and long-term memory return in 2.0?
>
> Yes. Both modules are being ported from 1.0 to the 2.0 architecture and will land in upcoming releases. Track the changelog and GitHub releases for availability.

> [accordion] Are there language bindings other than Python?
>
> Yes. AgentScope is available in three languages, each with its own repository:
>
> * **Python** — [`agentscope-ai/agentscope`](https://github.com/agentscope-ai/agentscope) (this documentation)
> * **TypeScript** — [`agentscope-ai/agentscope-typescript`](https://github.com/agentscope-ai/agentscope-typescript)
> * **Java** — [`agentscope-ai/agentscope-java`](https://github.com/agentscope-ai/agentscope-java)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.