AgentScope Java 1.1 · Harness

​

Why Harness

1. Distributed workspace state: local directory assumptions break in multi-replica deployments.
2. Execution safety: user-driven shell/code execution must be isolated from host processes.
3. Storage abstraction: agent logic should not be coupled to one storage store.
4. Subagent orchestration: task delegation and lifecycle management become complex quickly.
5. Memory governance: context growth and cross-session fact retention need first-class support.

​

Core Design

​

Workspace as source of truth

• persona and rules (AGENTS.md)
• long-term memory (MEMORY.md)
• domain knowledge
• skills
• subagent definitions
• session artifacts

​

AbstractFilesystem as portability layer

• local disk
• remote storage
• sandbox filesystem
• composite routing across stores

​

What 1.1 Delivers

• Workspace-driven runtime for durable identity and evolving behavior
• Pluggable filesystem abstraction for local/remote/sandbox execution
• Built-in context governance (compaction + layered memory)
• Subagent orchestration with sync/async delegation and task lifecycle

​

Typical Deployment Scenarios

​

Personal productivity agents

• local execution
• durable memory and persona
• workspace-driven skill iteration

​

Enterprise data/service agents

• sandboxed execution for untrusted input
• distributed memory/session continuity across replicas
• async subagent orchestration for long-running tasks

​

API-first online agents

• strict tool boundaries (no implicit shell exposure)
• shared remote state for cross-instance continuity
• stable multi-turn behavior under production traffic

​

Quick Start (Harness)

<dependency>
  <groupId>io.agentscope</groupId>
  <artifactId>agentscope-harness</artifactId>
  <version>${agentscope.version}</version>
</dependency>

HarnessAgent agent = HarnessAgent.builder()
    .name("my-agent")
    .model(model)
    .workspace(Paths.get(".agentscope/workspace"))
    .compaction(CompactionConfig.builder()
        .triggerMessages(50)
        .keepMessages(20)
        .build())
    .build();

RuntimeContext ctx = RuntimeContext.builder()
    .sessionId("user-session-001")
    .userId("alice")
    .build();

Msg reply = agent.call(userMessage, ctx).block();

​

Recommended Reading

• Harness Overview
• Harness Architecture
• Filesystem
• Sandbox
• Chinese full article