已弃用 APIDeprecated API

Use `#forNumber(int)` instead.

Use `#forNumber(int)` instead.

Use `#forNumber(int)` instead.

Returns the skill repository.

Sets the skill repository.

use `#acquireOrConflict(String, String, Runnable)`

use `SessionStatuses#CREATED`

use `SessionStatuses#RUNNING`

use `SessionStatuses#IDLE`

use `SessionStatuses#REQUIRES_ACTION`

use `SessionStatuses#TERMINATED`

use `SessionStatuses#RESCHEDULED`

use `SessionStatuses#ARCHIVED`

use `#dispatchAndAwaitReply(String, String, String, String)`

host-disk materialization is no longer used; memory stores are mounted live via `#createFilesystems`. Retained only so callers mid-migration keep compiling; delegates to `#resolveMounts`.

writeback is a no-op: `MemoryStoreFilesystem` writes directly through to `MemoryStoreService` on every tool call, so there is nothing left to reconcile after a turn.

Use `#forNumber(int)` instead.

Use `#forNumber(int)` instead.

Use `#forNumber(int)` instead.

Use `#interrupt(String, String)` with explicit userId/sessionId.

Use `#interrupt(String, String, Msg)` with explicit userId/sessionId.

Use `#interrupt(String, String)` with explicit userId/sessionId.

since 2.0.0, for removal. Use `#streamEvents(List)` (and overloads that accept `RuntimeContext` via `call()`-driven lifecycle) for the fine-grained `AgentEvent` stream.

since 2.0.0, for removal. Use `#streamEvents(List)` for the fine-grained `AgentEvent` stream.

since 2.0.0, for removal. Use `#streamEvents(List)` for the fine-grained `AgentEvent` stream.

Use `#getAgentState(RuntimeContext)` or `#getAgentState(String, String)` with explicit session identity. This method delegates to the default session slot.

Use `getAgentState(userId, sessionId).getPermissionContext()` instead.

Use `getAgentState(userId, sessionId).getPermissionContext()` instead.

Permission HITL no longer uses a Reactor Sink. Confirm results are now delivered via a second `agent.call(msgs)` carrying a `ConfirmResult` payload — see `applyConfirmResults`. This constant is retained as a compile-time marker and will be removed in a future release.

No longer enforced; per-session serialization handles concurrency.

Use `RuntimeContext` with `agent.call(msg, runtimeContext)` or register POJOs directly via `RuntimeContext.builder().put(Type, value)`.

since 2.0.0. Long-term memory is being redesigned around the upcoming reme base class. Hooks added through this path still work.

since 2.0.0. See `#longTermMemory`.

since 2.0.0. See `#longTermMemory`.

since 2.0.0. RAG is being redesigned; legacy adapters remain functional.

since 2.0.0. See `#knowledge`.

since 2.0.0. See `#knowledge`.

since 2.0.0. See `#knowledge`.

since 2.0.0. Skills now flow through `#skillRepository` / `#skillRepositories`; legacy `io.agentscope.core.skill.SkillBox` instances are still accepted for source compatibility, but combining a `skillBox(...)` with `skillRepository(...)` is untested — new code should prefer `#skillRepository(AgentSkillRepository)`.

Use `#AgentBase(String, String, List)` instead.

No longer enforced; per-session serialization handles concurrency.

Subclasses should implement per-session interrupt via RuntimeContext.

Subclasses should implement per-session interrupt via RuntimeContext.

Subclasses should implement per-session interrupt via RuntimeContext.

No longer needed; ReActAgent uses per-execution InterruptControl.

No-op; interrupt state is owned by the execution.

No-op stub.

Returns USER. Interrupt source is owned by the execution.

since 2.0.0, for removal. Use `ReActAgent#streamEvents(List)` for the fine-grained `AgentEvent` stream.

since 2.0.0, for removal. Use `ReActAgent#streamEvents(...)` for the fine-grained `AgentEvent` stream.

since 2.0.0, for removal. Use `ReActAgent#streamEvents(...)` for the fine-grained `AgentEvent` stream.

since 2.0.0. This is the v1 coarse-grained event type, kept as the return type of the deprecated `stream(...)` API and as the wire format consumed by the harness, AGUI, A2A, chat-completions-web, and Kotlin extension modules. New code should use `io.agentscope.core.event.AgentEvent` via `ReActAgent#streamEvents(...)`, which exposes the fine-grained event hierarchy (28 typed events covering the full agent lifecycle and HITL flow). The class will be marked `forRemoval = true` once the dependent internal modules migrate to `AgentEvent`.

since 2.0.0. Used only by the v1 `Event` stream to attribute events to a spawned subagent. A subagent-source channel for the new `io.agentscope.core.event.AgentEvent` stream is on the v2 roadmap; once it lands, `EventSource` will be marked `forRemoval = true`.

since 2.0.0. The v1 coarse-grained event discriminator. New code should use `io.agentscope.core.event.AgentEventType` (and the typed `AgentEvent` subclasses) exposed by `ReActAgent#streamEvents(...)`.

since 2.0.0, for removal in a future minor release. Every `stream(...)` method on this interface returns the coarse-grained `Event` type, which is a v1 carry-over. Use `ReActAgent#streamEvents(...)` instead — it returns `Flux<io.agentscope.core.event.AgentEvent>`, the fine-grained event hierarchy that covers the full agent lifecycle (28 typed events including HITL) and is the single streaming surface going forward. See the v2 changelog section B.4 for migration details.

since 2.0.0, for removal. Use `ReActAgent#streamEvents(...)` for the fine-grained `AgentEvent` stream.

since 2.0.0, for removal. Use `ReActAgent#streamEvents(...)` for the fine-grained `AgentEvent` stream.

since 2.0.0, for removal. Use `ReActAgent#streamEvents(...)` for the fine-grained `AgentEvent` stream.

since 2.0.0, for removal. Use `ReActAgent#streamEvents(Msg)` for the fine-grained `AgentEvent` stream.

since 2.0.0, for removal. Use `ReActAgent#streamEvents(Msg)` for the fine-grained `AgentEvent` stream.

since 2.0.0, for removal. Use `ReActAgent#streamEvents(...)` for the fine-grained `AgentEvent` stream.

since 2.0.0, for removal. Use `ReActAgent#streamEvents(...)` for the fine-grained `AgentEvent` stream.

since 2.0.0, for removal. Use `ReActAgent#streamEvents(List)` for the fine-grained `AgentEvent` stream.

since 2.0.0, for removal. Use `ReActAgent#streamEvents(List)` for the fine-grained `AgentEvent` stream.

since 2.0.0, for removal. Use `ReActAgent#streamEvents(...)` for the fine-grained `AgentEvent` stream.

since 2.0.0, for removal. Use `ReActAgent#streamEvents(...)` for the fine-grained `AgentEvent` stream.

since 2.0.0, for removal. Use `ReActAgent#streamEvents(...)` for the fine-grained `AgentEvent` stream.

since 2.0.0. Replaced by the `io.agentscope.core.middleware.MiddlewareBase` system. Use `io.agentscope.core.ReActAgent#streamEvents(java.util.List)` for fine-grained event streaming.

Stream-based user input implementation that reads from any InputStream and writes to any OutputStream.

UserAgent class for handling user interaction within the agent framework.

Strategy interface for handling user input from different sources.

Data class that holds user input information with dual representation.

since 2.0.0. Use `io.agentscope.core.middleware.MiddlewareBase` instead.

since 2.0.0. Use `io.agentscope.core.middleware.MiddlewareBase` instead.

since 2.0.0. Use `io.agentscope.core.middleware.MiddlewareBase` instead.

since 2.0.0. Use `io.agentscope.core.middleware.MiddlewareBase` instead. Middleware exposes `onAgent`, `onReasoning`, `onActing`, `onModelCall`, and `onSystemPrompt` hook points and replaces this entire hook system.

since 2.0.0. Use `io.agentscope.core.middleware.MiddlewareBase` instead.

since 2.0.0. Use `io.agentscope.core.middleware.MiddlewareBase` instead.

since 2.0.0, for removal. Will be deleted together with the Hook system.

since 2.0.0. Use `io.agentscope.core.middleware.MiddlewareBase` instead.

since 2.0.0. Use `io.agentscope.core.middleware.MiddlewareBase` instead.

since 2.0.0. Use `io.agentscope.core.middleware.MiddlewareBase` instead.

since 2.0.0. Use `io.agentscope.core.middleware.MiddlewareBase` instead.

since 2.0.0. Use `io.agentscope.core.middleware.MiddlewareBase` instead.

since 2.0.0. Use `io.agentscope.core.middleware.MiddlewareBase` instead.

since 2.0.0. Use `io.agentscope.core.middleware.MiddlewareBase` instead.

since 2.0.0. Use `io.agentscope.core.middleware.MiddlewareBase` instead.

since 2.0.0. Use `io.agentscope.core.middleware.MiddlewareBase` instead.

since 2.0.0. Use `io.agentscope.core.middleware.MiddlewareBase` instead.

since 2.0.0. Use `io.agentscope.core.middleware.MiddlewareBase` instead.

since 2.0.0. Use `io.agentscope.core.middleware.MiddlewareBase` instead.

since 2.0.0. The hook system is replaced by `io.agentscope.core.middleware.MiddlewareBase`.

since 2.0.0. New code should read context directly from `AgentState#getContext()`.

since 2.0.0. Conversation context lives on `io.agentscope.core.state.AgentState#getContext()`; this class is retained for source compatibility with 1.0.x user code.

since 2.0.0. Long-term memory is removed; conversation context now lives on `io.agentscope.core.state.AgentState#getContext()`. Integrate any cross-session persistence at the application layer.

since 2.0.0. Long-term memory is removed.

since 2.0.0. Long-term memory is removed.

since 2.0.0. Conversation context is now held on `io.agentscope.core.state.AgentState#getContext()`. This interface is retained as a write-only mirror for source compatibility with 1.0.x user code.

since 2.0.0. Use `AgentState#getContext()` directly.

since 2.0.0. Long-term memory and the `Hook` system are removed; reimplement as a `io.agentscope.core.middleware.MiddlewareBase` if required.

Not in official API spec

Not in official API spec

Not in official API spec

Use `#topK(Integer)` instead

since 2.0.0. The rag package is removed; integrate retrieval at the application layer.

since 2.0.0. The rag package is removed; integrate retrieval at the application layer.

since 2.0.0. The rag package is removed; integrate retrieval at the application layer.

since 2.0.0. The rag package is removed; integrate retrieval at the application layer.

RAGFlow identifies rerank models by name, not by a numeric id, so no `Integer` maps to a real model and the retrieval request is rejected. Use `#rerankId(String)` instead. This overload only keeps existing call sites compiling and stringifies the value.

since 2.0.0. The rag package is removed; integrate retrieval at the application layer.

since 2.0.0. The rag package is removed; integrate retrieval at the application layer.

since 2.0.0. The rag package is removed; integrate retrieval at the application layer.

Use `MilvusStore#builder()` instead

Use `#truncateAllSessions()` instead

Use `io.agentscope.core.session.redis.RedisSession` with jedisClient instead. RedisSession provides a unified session implementation that works with multiple Redis clients. For basic usage, simple constructors are available. For advanced configuration, use `RedisSession#builder()`. This implementation stores session state in Redis with the following key structure: - Single state: `{prefix}{sessionId}:{stateKey}` - Redis String containing JSON - List state: `{prefix}{sessionId}:{stateKey}:list` - Redis List containing JSON items - Session marker: `{prefix}{sessionId}:_keys` - Redis Set tracking all state keys - Incremental list storage (only appends new items) - Type-safe state serialization using Jackson - Automatic session key tracking

Use `io.agentscope.core.session.redis.RedisSession` with redissonClient instead. RedisSession provides a unified session implementation that works with multiple Redis clients. For basic usage, simple constructors are available. For advanced configuration, use `RedisSession#builder()` This implementation stores session state in Redis with the following key structure: - Single state: `{prefix}{sessionId}:{stateKey}` - Redis String containing JSON - List state: `{prefix}{sessionId}:{stateKey}:list` - Redis List containing JSON items - Session marker: `{prefix}{sessionId}:_keys` - Redis Set tracking all state keys - Incremental list storage (only appends new items) - Type-safe state serialization using Jackson - Automatic session key tracking

since 2.0.0. Use `ShutdownStateSaver` with `GracefulShutdownManager#bindStateSaver` instead.

since 2.0.0. The skill package and the hook system are removed; manage markdown skill catalogs in application code or via `MiddlewareBase`.

Part of the `ToolExecutionContext` layer which is superseded by `io.agentscope.core.agent.RuntimeContext`.

Use `#getRuntimeContext()` instead.

Use `#runtimeContext(RuntimeContext)` instead.

Use `io.agentscope.core.agent.RuntimeContext` instead. Register POJOs via `RuntimeContext.builder().put(Type.class, value).build()` and pass to `agent.call(msg, runtimeContext)`.

Part of the `ToolExecutionContext` layer which is superseded by `io.agentscope.core.agent.RuntimeContext`.

Use `io.agentscope.core.agent.RuntimeContext` instead.

Use `io.agentscope.core.agent.RuntimeContext` instead.

Use `#McpTool(String, String, Map, Map, McpClientWrapper, Map, String, boolean)` so the MCP server name and read-only hint are propagated. Kept for source compatibility with callers that pre-date the `ToolBase` integration.

Use `#McpTool(String, String, Map, Map, McpClientWrapper, Map, String, boolean)` so the MCP server name and read-only hint are propagated.

Use `#McpTool(String, String, Map, Map, McpClientWrapper, Map, String, boolean)` so the MCP server name and read-only hint are propagated.

since 2.0.0. Use `OtelTracingMiddleware` instead.

since 2.0.0. Use `OtelTracingMiddleware` instead.

since 2.0.0. Use `OtelTracingMiddleware` instead.

Recommend using `#selectionStrategy(TrainingSelectionStrategy)`

use the canonical constructor (or `#from`) so the reception mode is explicit

use `io.agentscope.extensions.model.openai.compat.deepseek.DeepSeekFormatter`.

use `io.agentscope.extensions.model.openai.compat.deepseek.DeepSeekMultiAgentFormatter`.

use `io.agentscope.extensions.model.openai.compat.glm.GLMFormatter`.

use `io.agentscope.extensions.model.openai.compat.glm.GLMMultiAgentFormatter`.

Use `io.agentscope.extensions.jdbc.JdbcDistributedStore` from the `agentscope-extensions-jdbc` module instead. The new module provides a unified multi-database dialect abstraction that supports MySQL, PostgreSQL, H2, and SQLite with a single aggregated interface. This class is preserved unchanged for backward compatibility and will be removed in a future major release.

Use `#truncateAllSessions()` instead

Use `io.agentscope.extensions.jdbc.JdbcDistributedStore` from the `agentscope-extensions-jdbc` module instead. The new module provides a unified multi-database dialect abstraction that supports MySQL, PostgreSQL, H2, and SQLite with a single aggregated interface. This class is preserved unchanged for backward compatibility and will be removed in a future major release.

Use `io.agentscope.extensions.redis.state.RedisAgentStateStore` with jedisClient instead. RedisAgentStateStore provides a unified session implementation that works with multiple Redis clients. For basic usage, simple constructors are available. For advanced configuration, use `RedisAgentStateStore#builder()`. This implementation stores session state in Redis with the following key structure: - Single state: `{prefix}{sessionId}:{stateKey}` - Redis String containing JSON - List state: `{prefix}{sessionId}:{stateKey}:list` - Redis List containing JSON items - AgentStateStore marker: `{prefix}{sessionId}:_keys` - Redis Set tracking all state keys - Incremental list storage (only appends new items) - Type-safe state serialization using Jackson - Automatic session key tracking

Use `io.agentscope.extensions.redis.state.RedisAgentStateStore` with redissonClient instead. RedisAgentStateStore provides a unified session implementation that works with multiple Redis clients. For basic usage, simple constructors are available. For advanced configuration, use `RedisAgentStateStore#builder()` This implementation stores session state in Redis with the following key structure: - Single state: `{prefix}{sessionId}:{stateKey}` - Redis String containing JSON - List state: `{prefix}{sessionId}:{stateKey}:list` - Redis List containing JSON items - AgentStateStore marker: `{prefix}{sessionId}:_keys` - Redis Set tracking all state keys - Incremental list storage (only appends new items) - Type-safe state serialization using Jackson - Automatic session key tracking

Use `#getDelegate()``.getAgentState(RuntimeContext)` or `.getAgentState(String, String)` with explicit session identity.

Use `#call(List, RuntimeContext)` with explicit runtime context.

Use `#call(List, Class, RuntimeContext)` with explicit runtime context.

Use `#call(List, JsonNode, RuntimeContext)` with explicit runtime context.

since 2.0.0, for removal. Use `#streamEvents(List)` for the fine-grained `AgentEvent` stream that aligns with Python 2.0's `agent.reply_stream()`.

since 2.0.0, for removal. Use `#streamEvents(List)` for the fine-grained `AgentEvent` stream.

since 2.0.0, for removal. Use `#streamEvents(List)` for the fine-grained `AgentEvent` stream.

since 2.0.0, for removal. Use `#streamEvents(Msg, RuntimeContext)`.

since 2.0.0, for removal. Use `#streamEvents(List, RuntimeContext)`.

since 2.0.0, for removal. Use `#streamEvents(List, RuntimeContext)`.

since 2.0.0, for removal. Use `#streamEvents(List, RuntimeContext)`.

since 2.0.0, for removal. Use `#streamEvents(List, RuntimeContext)`.

Use `#streamEvents(Msg, RuntimeContext)` with explicit runtime context.

Use `#streamEvents(List, RuntimeContext)` with explicit runtime context.

Use `#streamEvents(String, RuntimeContext)` with explicit runtime context.

use `#ProjectAwareOverlay(AbstractSandboxFilesystem, AbstractFilesystem, LocalFilesystem, Path, NamespaceFactory)` so workspace-rooted absolute paths resolve identically to their relative spelling under namespace scoping

use `#mode(LocalFsMode)` for the full three-way selection

use `#runWakeup(String, String)` so the wakeup-driven round loads agent state from the correct `(userId, sessionId)` slot. This overload preserves legacy anonymous-wakeup behavior.

implementers should override `#runWakeup(String, String)` instead, so the dispatcher can propagate the owning user id. Required for runtimes that isolate agent state by `(userId, sessionId)`: without it, a wakeup-driven round loads state from an anonymous slot and the original conversation is lost. This overload is retained for backward compatibility and defaults to ignoring the user id.

Prefer `SessionTranscriptWriter#resolveContextPath`.

Prefer `SessionTranscriptWriter#appendMessages`. Kept as a thin delegate so compaction / overflow-recovery call sites keep compiling during the migration; new code should use `SessionTranscriptWriter` directly.

Prefer `#SkillLoadTool()` and bind catalogs through `SkillRuntime#install(SkillCatalog, io.agentscope.core.agent.RuntimeContext, io.agentscope.core.tool.Toolkit)`.

Use `#currentCatalog(RuntimeContext)` so catalog lookup is request-scoped.

Use `#install(SkillCatalog, RuntimeContext, Toolkit)`.

since Phase A — use `#getSteps()`. Returns the same value; kept for source compatibility with callers built before the `steps` field existed.

since Phase A — use `#steps(int)`. Equivalent in behaviour.

Use `#resolveSessionContextFile(RuntimeContext, String, String)` for the JSONL format.

Normalize a path to workspace-relative form by stripping the active mode's prefix.