Skip to main content
AgentScope unifies all components that need distributed persistence under the DistributedStore interface. One line of configuration switches agent state, workspace filesystem, sandbox snapshots, and concurrency locks to the same distributed store.

Quick Start

Capability Matrix

OSS does not provide SandboxExecutionGuard — object storage is unsuitable for distributed locking. Mix in a Redis guard via DistributedStore.builder().

Mixed Stores

Different components can come from different storage stores:

Components

AgentStateStore — Agent State Persistence

Conversation context, compaction summaries, permission rules, Plan Mode state, addressed by (userId, sessionId). Auto-wired by distributedStore; can be overridden via .stateStore(...).

BaseStore — Workspace Filesystem KV

Storage provider for RemoteFilesystemSpec, routing MEMORY.md, memory/, skills/, sessions/ to shared KV storage. Auto-injected into RemoteFilesystemSpec when using the no-arg constructor.

SandboxSnapshotSpec — Sandbox Snapshots

Persists Docker/K8s sandbox workspace as tar archives for cross-call recovery. Auto-wired into SandboxFilesystemSpec by distributedStore.

SandboxExecutionGuard — Sandbox Concurrency Lock

Distributed lock for AGENT / GLOBAL isolation scope under multi-replica deployment. Auto-wired into SandboxFilesystemSpec by distributedStore.

Priority

Store Documentation

  • Redis — full capability coverage, recommended for multi-replica production
  • JDBC — for existing relational database infrastructure
  • MongoDB — document-oriented storage, ideal for large conversation histories
  • Alibaba Cloud OSS — object storage, best for large-capacity snapshots