Compose execution with @agentium/harness
Define a harness from abilities and context sources, select an execution driver, and enforce grants, budgets, and policies. The package owns its sessions, events, portable manifests, and watches. Start with the research recipe or workspace reviewer. The old agent-embedded harness API is removed. Import the package from@agentium/harness; see harness migration.
Connect voice and phone systems
Control longer-running work
Durable records cover tasks, actions, approvals, events, and artifacts. Queue integration, protocol bridges, and watches connect those records to workers and external systems. Follow recovery guidance before retrying an operation that may already have had an effect.Run and observe integrations
- Sandbox backends: local execution, E2B, and Daytona have explicit ownership and dependency contracts.
- Telemetry exporters: JSONL files, OTLP/HTTP JSON, a host-owned OpenTelemetry tracer, and Langfuse OTLP.
- Transport: caller scope and authentication, bounded streaming, multipart cleanup, and Socket.IO session ownership.
- Evaluation: cancellation, deadlines, case identity, and assertion results.
- MCP: approved text resources have URI, MIME, and ownership constraints; harness context explains how to consume them.
- Tools: schema support includes Zod 3, Zod 4 Classic, and Zod 4 Mini. Skills cover file and package validation.