WeChat
ai-engineering
Original source

AgentScope Java 2.0 GA — Enterprise AI Agent Framework

Summary

Technical deep-dive on AgentScope Java 2.0 GA release (by Alibaba/Tongyi team). Based on a public talk by 刘军 (2026-07). The framework adds a “Harness” engineering layer on top of the ReActAgent core, enabling enterprise-grade distributed agent deployment.

Architecture

  • Core: ReActAgent loop (reasoning + tool calling) — unchanged from 1.0
  • Harness layer: New in 2.0, wraps ReAct with enterprise capabilities
  • Languages: Java, Python, TypeScript (Go in development)
  • Ecosystem: DeepSeek, OpenAI-compatible, Qwen models; OpenTelemetry observability; Higress for MCP proxy; Nacos for skill registry

Key Harness Features

  1. Workspace — Agent’s source of truth. Contains static assets (AGENTS.md, Skills, Sub-agents) + runtime data (Session state, Task state, MEMORY.md). Abstract File System interface supports local disk, MySQL/Redis/OSS, or Sandbox backends.

  2. Context Compression (4 layers) — Tool result truncation + file reference, input param truncation, message history compression. Preserves critical state: task plans, async sub-agent status, permission records.

  3. Dual-layer Long-term Memory — Daily flush to per-day files → periodic distillation into global MEMORY.md (loaded into system prompt). Companion tools: Memory Search, Memory Get, Session Search.

  4. Sub-agent Orchestration — Fork/Spawn tools. Sync + async + remote sub-agents. Async agents notify parent on completion. TaskList toolkit for status tracking. Users can directly chat with sub-agents.

  5. Sandbox — Isolated tool execution with lifecycle management. Workspace maps to sandbox for multi-tenant isolation.

  6. Skills — 4-layer registry (Nacos integration). Per-user skill isolation. Skill scripts execute inside sandbox.

  7. Plan Mode — PlanEnter/PlanExit tools. Auto or manual mode switching. Permission-gated transitions (like Coding Agents).

  8. Channel — Native IM platform integration (messaging → Gateway → Agent).

Migration 1.0 → 2.0

  • Most APIs backward-compatible (deprecated but preserved)
  • Breaking: Agent State management redesigned, RuntimeContext required on call/stream methods (user/session isolation)
  • Gradual: deprecated APIs removed in 2.1

Official Examples

  • Personal assistant (local FS + Shell, like simplified QwenPaw)
  • Multi-tenant managed agent platform (zero-code Agent Builder SaaS)

Docs: https://java.agentscope.io