Overview / Surfaces

CLI, portal, A2A

Three ways to talk to the same units. The CLI does anything the portal shows; every unit speaks A2A at its boundary.

$ spring unit create engineering-team \
    --description "Backend squad"
 Unit engineering-team created

$ spring agent create --name ada \
    --unit engineering-team \
    --from-package software-engineering
 Agent ada added (github connector bound)

$ spring unit start engineering-team
 engineering-team running

$ spring message send agent:8c5fab… \
    "Review PR #1086 — focus on the threading model."
 message queued (id 9f2c…)
 ada working
 checkpoint: needs decision → @savas

The spring CLI

Create units, add agents, wire connectors, send messages, watch activity.

Default Tenant3
engineering-team3
tech-lead
backend-engineer
qa-engineer
Default Tenant engineering-team
engineering-team
Running
Agents
3
Sub-units
0
Cost (24h)
$0.00

Web portal

The unit tree, conversations, activity streams, cost. Live, deep-linkable.

A2A protocol

External agents and orchestrators participate as peers — ADK, LangGraph, MCP clients, anything that speaks A2A.