ya-agent-stream-protocol
Shared stream protocol adapters between ya-agent-sdk and applications.
The Python import package is ya_agent_stream_protocol.
Compact AGUI replay drops redundant text/reasoning and tool-end scaffolding, but retains
TOOL_CALL_START as an observed execution fact. A run interrupted before its first tool
argument chunk must still be able to reconstruct the visible invocation.
The package owns the shared protocol boundary between ya-agent-sdk and applications:
- AGUI event adaptation
- compact replay buffers
- message artifact validation
- SSE framing helpers
YAACLI, YA Claw, and future applications configure their own event namespaces through
AguiAdapterConfig instead of embedding application-specific names in this package.
SDK lifecycle projections use canonical snake-case names such as
ya_agent.subagent_start, ya_agent.subagent_complete, and
ya_agent.model_request_complete. The adapter is also a fail-closed public-data
boundary: only explicitly allowlisted lifecycle DTOs are emitted, and unknown or future
SDK events are dropped rather than generically serialized. Subagent projections omit
parent logical-run IDs, native enqueue projections expose only a message count,
model-request projections omit internal event/run IDs, file changes omit replacement
content, and execution start/resume events omit prompt and deferred-result content. Full
injected messages, durable input/enqueue identities, idempotency keys, raw lifecycle
event IDs/timestamps, resumable state, and other host-owned data must remain outside
AGUI replay and SSE.
Tool display identity
Provider toolCallId values remain unchanged. Adapted tool start/chunk/end/result
events carry a separate toolCallKey, scoped to the display run and invocation.
The adapter retains that key across deferred-result segments and allocates a new key
when another invocation starts, even if an agent reuses a provider ID. Result
messageId derives from this display key. Replay, rendering, and argument budgets use
toolCallKey; older stored events without it retain their original ID-based behavior.
1 maintainer
Metadata
1 maintainer
Release files for ya-agent-stream-protocol 2.12.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ya_agent_stream_protocol-2.12.0.tar.gz | 14.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ya_agent_stream_protocol-2.12.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.5 kB
Release files / ya_agent_stream_protocol-2.12.0.tar.gz
| Download URL | ya_agent_stream_protocol-2.12.0.tar.gz |
|---|---|
| Size | 14.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6c347daf746c293edf24ce33fd32cd540c53ac1fdd64e19edadf216f1b82b449
|
|
BLAKE2b-256 checksum How to use checksums |
dcad1c4efbfaf05088fcc014797053b4a98c26c805f12e82eef3a3cebb25ab89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.14 {"installer":{"name":"uv","version":"0.11.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / ya_agent_stream_protocol-2.12.0-py3-none-any.whl
| Download URL | ya_agent_stream_protocol-2.12.0-py3-none-any.whl |
|---|---|
| Size | 12.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1f0d9ca7c54eeecb2a172c8288fdc02334f1a97adb3cc9c90ce8f1e9917f2556
|
|
BLAKE2b-256 checksum How to use checksums |
d5fc60ed642578fdd96480c60a4e9da39bda2d92f50eab7926478f1fe2f6aa65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.14 {"installer":{"name":"uv","version":"0.11.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for ya-agent-stream-protocol 2.12.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
