Topolo Docs Topolo Platform
Open workspace

Context agent pack

Connect portable agent pack identities, scoped continuity and Bytes artifacts through published workspace contracts.

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.

Outcome

Connect portable agent pack identities, scoped continuity and Bytes artifacts through published workspace contracts.

GET /api/agent-packs/{instanceId}/context

Before calling

Discover the exact credential-scoped published action and intended context. Bind the authorized Agent workspace when required. Confirm the declared knowledge:read permission. This is a read; it does not authorize a later mutation.

Input fields

FieldRequiredType
instanceIdYesstring
logicalIdYesstring

Source input template

The following schema-based example is illustrative and has not been executed. Every fixture identifier/decision reference must be replaced with a genuinely discovered resource or recorded decision. Do not send it unchanged.

{
  "instanceId": "example-pack-instance",
  "logicalId": "intakes/intake"
}

Interpret and verify

  • Confirm organization, workspace, logical role, exact agent version and Bytes binding. truncated=true means the bounded result is incomplete.

The exact input and output schemas accompany this draft in the hidden agent layer and contract bundle. No successful/refused deployed response is supplied here; capture and validate it after the original activation/usage proof.

Effects

  • Reads role instructions and permitted instruction, knowledge and durable memories. Excludes episodes, prior tasks, runs, transcripts, expired records and other users private records. Returns Bytes references without downloading files.

Errors and recovery

  • 409 pack_agent_version_conflict: Review the changed published agent and reconnect explicitly; never use an unreviewed replacement version.

This action does not change service state.