Skip to main content

Datalayer

Become a Sponsor

🤖 👥 Agent Teams

PyPI - Version npm

The Datalayer orchestration extension

agent_teams.a2a (Python) and @datalayer/agent-teams (TypeScript) implement the Datalayer orchestration extension — an optional A2A extension that lets a worker and an orchestrator say the things about delegated work that A2A leaves unsaid: which execution a delegation is part of and where it sits in its tree, a budget to decline before exceeding, a checkpoint to resume from, and instructions delivered to a turn already in progress.

from agent_teams.a2a import ExecutionRef, build_delegation_meta

meta = build_delegation_meta(
    ExecutionRef(execution_id="exec_1", root_execution_id="exec_1", depth=0),
    budget={"outputTokens": 4000},
)
import { buildDelegationMeta } from '@datalayer/agent-teams';

const meta = buildDelegationMeta(
  { executionId: 'exec_1', rootExecutionId: 'exec_1', depth: 0 },
  { budget: { outputTokens: 4000 } },
);

Nothing here requires the rest of this package, and nothing here imports Datalayer's own platform — agent_teams.a2a.orchestration_extension and @datalayer/agent-teams's src/orchestrationExtension.ts are each a standalone module (Python built on fasta2a alone; TypeScript with zero runtime dependencies at all) implementing the identical wire shape, field for field. A worker implementing none of it still runs; see the normative specification and its JSON Schema at docs/extension-v1.md for the full field-by-field contract both modules implement.

This is distinct from agent_teams.a2a.extensions' own team-coordination extension (https://datalayer.io/ext/team-coordination/v1) — member assignment, task dependencies, health and reactions for a team's own internal coordination. The two extensions are independent and separately negotiated; a card may advertise either, both, or neither.

A reference worker, and a public conformance suite

agent_teams.a2a.reference_worker is the smallest thing that speaks the extension correctly: no model, no framework beyond fasta2a, no Datalayer control plane. Run it standalone —

python -m agent_teams.a2a.reference_worker  # serves on :8000

— point any A2A client at it, and its card advertises the extension. It answers a turn with what it "spent" (a character count, not a model call, so this needs no API key), declines a delegation whose budget already reads outputTokens: 0 naming the limit, and answers a pause request by ending the turn at a checkpoint it makes up on the spot.

tests/test_reference_worker_conformance.py drives it over real ASGI HTTP (httpx.ASGITransport, no socket) with hand-built JSON-RPC requests matching docs/extension-v1.md's documented wire shapes — negotiation, a declined budget, pause and resume — runnable by anyone against their own worker, with no Datalayer service in the loop.

Release files for agent-teams 0.0.7

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for agent-teams 0.0.7
File Size Uploaded
agent_teams-0.0.7.tar.gz 750.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for agent-teams 0.0.7
File Interpreter ABI Platform
agent_teams-0.0.7-py3-none-any.whl Python 3 none any Details

Total release size: 834.5 kB

Release files / agent_teams-0.0.7.tar.gz

Download URL agent_teams-0.0.7.tar.gz
Size 750.7 kB
Tags Source
SHA-256 checksum
How to use checksums
b6985ce4f3dbf03f0167ed09896ea82588f59782b9551f95b505985aecf43d13
BLAKE2b-256 checksum
How to use checksums
a5feca1ea620535304663bed680be56cfb002dbf0f6921396de14cea201a9a3f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 26, 2026.

Transparency log

Release files / agent_teams-0.0.7-py3-none-any.whl

Download URL agent_teams-0.0.7-py3-none-any.whl
Size 83.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5e9446d081bde4350be7d1c39a0c938ff97a18d003e216a2a09ec9f191bf8d14
BLAKE2b-256 checksum
How to use checksums
08d8966b143ff39a391bb3a7c8336bfb564d06871f78b8b5cda071507c35fc3b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 26, 2026.

Transparency log

Release history Release notifications | RSS feed

1.0.0

2 release files

This release

0.0.7 This release

2 release files

0.0.5

2 release files

0.0.4

2 release files

0.0.3

2 release files

0.0.2

1 release file

0.0.1

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page