Skip to content

Team Coordination

li team gives agents in a flow a persistent inbox for mid-run signals. The team file survives at ~/.lionagi/teams/<id>.json after the flow exits.

Setup

pip install lionagi          # or: uv add lionagi
# claude — npm install -g @anthropic-ai/claude-code && claude login

Create a team

li team create "research-review" -m researcher,reviewer,orchestrator

# output:
Created team 'research-review' (e7a3d91bf542)
  Members: researcher, reviewer, orchestrator
  File: ~/.lionagi/teams/e7a3d91bf542.json

Attach a flow to the team

li o flow claude/sonnet \
  "Research Python async patterns, then review the draft for completeness" \
  --team-attach research-review --save ~/team-out

# output:
Team 'research-review' attached (e7a3d91bf542, 0 prior msgs)

--team-attach research-review loads the named team and preserves its message history. It has upsert semantics, so it creates the team if the name does not exist. Use --team-mode only when you want a fresh team with a new ID for each invocation.

Mid-flow signals

Workers call li team send while their op is still running:

li team send \
  "Draft at ~/team-out/researcher/research.md — ready for review" \
  -t research-review --to reviewer --from researcher --from-op o1

# output:
Sent to reviewer in 'research-review'

The reviewer reads its inbox before starting its own op:

li team receive -t research-review --as reviewer

# output:
[2026-04-20T14:03:08] researcher op=o1 → reviewer
  Draft at ~/team-out/researcher/research.md — ready for review

(1 message)

--as reviewer marks the message read for that member only. Concurrent sends serialize under fcntl.flock — parallel workers don't clobber each other.

Inspect the inbox

After the flow, check the full thread:

li team show research-review

# output:
Team: research-review (c4f8b2a01e73)
Created: 2026-04-20T14:02:55.123456+00:00
Members: orchestrator, researcher, reviewer

────────────────────────────────────────────────────────────
  [2026-04-20T14:03:08] researcher op=o1 → reviewer  (read by: reviewer)
    Draft at ~/team-out/researcher/research.md — ready for review

  [2026-04-20T14:04:31] reviewer op=o2 → *
    Review complete. 2 gaps noted in ~/team-out/reviewer/review.md

Run li team list to see all teams.

How it works

--team-attach research-review loads the persistent team and injects TEAM_COORD_SECTION into each worker's system prompt — the agent knows its team id, role, and teammates' names. Workers call li team send --from-op <id> to tag which op the signal belongs to; one agent can run several ops on the same branch and each message stays traceable. li team receive --as <name> returns only unread messages for that member and timestamps them as read. At flow end, each worker's result is also posted as a team message, so li team show shows mid-flow signals and final outputs in one thread.

Artifacts use <save>/<agent_id>/.... A role's first assignment normally uses the role name as its agent ID; repeated assignments are suffixed, such as researcher-2.

Next