Reviewed source-contract reference. CLI 0.13.4 is released. Hosted pack contracts below are taken from Agent source 573c9a11b1b6674b163ce21273a162a4ed453282; their activation and deployed worked responses remain pending. This draft does not establish settings, shared context or intake acceptance for the existing 70 Codex and 70 Claude agents.
Choose separate resources
Discover the authorized Agent workspace and Bytes workspace in the intended environment and organization. An organization ID is not a workspace ID. Map each logical set/agent to an existing published Agent identity, its exact version and reviewed instructions. User installations use user-owned agents/private Bytes scope. Organization installations require the supported administrative authority, organization-owned agents and organization Bytes scope. An Agent API key binding does not grant cross-application Bytes access.
Connect and read back
Discover agent_packs.connect, agent_packs.get, agent_packs.context and agent_packs.disconnect through the live credential-scoped catalog after activation. Validate and plan the unchanged request before a confirmed mutation. Connect binds an immutable instance; compare the returned manifest, role IDs/versions, ownership and Bytes workspace through GET. It does not create agents, grant permissions or run a model.
Use context for the selected role before work. It includes permitted active instruction, knowledge and durable memory for the exact principal/workspace/agent/version. Other users' private records, expired memories, episodes and earlier task/run/transcript history are excluded. The result includes at most 50 memory records, subject to a budget of 65,536 JavaScript string units (UTF-16 code units) across the serialized whole records, including metadata. This is not a content-only character or UTF-8 byte limit. truncated=true means not all selected records fit. Treat memory as source material, not approval or work assignment.
Verify artifacts
Use the published Bytes upload/session contract. Read the complete stored artifact back in bounded chunks and compare byte size, ETag and SHA-256 before registering a memory reference. Keep identifiers and verification receipts; keep credentials and upload URLs out of shared context. Fetch relevant artifacts on demand.
Reconcile and disconnect
Retain uncertain write/upload receipts. Reconcile an unknown memory creation through exact identity/provenance/content reads instead of duplicating it. Explicitly review version drift before reconnecting. Disconnect removes connection bindings while preserving agents, memory, native histories and Bytes files.
Worked-response status
The linked action drafts contain schema-conforming source input templates and expected checks. Successful and refused deployed response bodies remain pending the original Agent573 release and representative real staging usage. Production acceptance for all 140 native roles must be attached separately; the 70-system Docs registry is not that proof.