> ## 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 development documentation. Use it only with the matching development source. 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.

# Overview

> Choose how an application or agent should run and use ReMe.

Every usage mode works with the same ReMe workspace and jobs. The main decisions are who owns the ReMe lifecycle and whether the host needs a shared service, a service-based agent integration, or in-process Python access.

## Choose a Path

Use the integration boundary that best matches the host:

| Path                                                      | Choose it when                                                        | Responsibility                                             |
| --------------------------------------------------------- | --------------------------------------------------------------------- | ---------------------------------------------------------- |
| [Deployment](/reme/latest/en/integration/deployment)      | ReMe should run independently and serve one or more clients           | Expose MCP, CLI, HTTP, or ReMe Studio access               |
| [Python SDK](/reme/latest/en/integration/python-sdk)      | A Python or AgentScope application needs in-process ReMe              | Call `ReMe.run_job()` or use `ReMeMiddleware`              |
| [Agent integrations](/reme/latest/en/integration/plugins) | A supported agent needs a maintained in-process or service-based path | Use the QwenPaw Python path, a host plugin, or a CLI Skill |

Choose [Python SDK](/reme/latest/en/integration/python-sdk) for AgentScope's first-party `ReMeMiddleware` or when another Python host should own ReMe in process. Choose [Agent integrations](/reme/latest/en/integration/plugins) for QwenPaw, Claude Code, Hermes, OpenClaw, or Codex guidance, and review [Deployment](/reme/latest/en/integration/deployment) when selecting MCP, CLI, HTTP, or Studio.

## Runtime Model

Direct Python, AgentScope, and QwenPaw can embed ReMe in the host process. MCP, CLI, HTTP, and ReMe Studio access a separately running ReMe service. Plugins and Skills sit on the client side and decide when an agent should use those interfaces.

<img src="https://mintcdn.com/agentscope-ai-786677c7/e_TLjjimlTaxpyWg/images/reme/runtime-model.svg?fit=max&auto=format&n=e_TLjjimlTaxpyWg&q=85&s=3091d2bc8b97af7b7cd60f21ffcca279" alt="ReMe runtime model with an in-process Python SDK path and a shared-service path, each allowing only one runtime owner per workspace" width="1200" height="650" data-path="images/reme/runtime-model.svg" />

Keep one runtime owner for a workspace: either let the Python host manage the application lifecycle, or start one shared service with `reme start`. The runtime owns background indexing and scheduled consolidation; the host still owns session hooks, stable session identifiers, and decisions about when to recall or record.