Identity, errors, and environments¶
Browser tokens restore identity, but service admission still uses current Role/lifecycle. Own-task, conversation, sandbox-tool, and current agent.use conditions must all hold. A member’s access to one task’s MCP App does not authorize taking over another user’s browser.
Protocol |
Actual response |
|---|---|
Browser token |
Numeric code0/data with token/expires_at; successful responses use no-store. |
Browser stream |
Text/binary frames after successful 101. Rejected upgrades may still return HTTP JSON; periodic authorization failures may close with 1008. |
runtime builder |
Numeric success envelope. Runtime rejection and owner recovery feedback may use string code/message/data. |
runtime skill files |
ZIP and frozen-version headers. Failure uses the skill error envelope and cannot be parsed as successful JSON. |
WebSocket and ZIP use their respective response types. Do not decode them as ordinary JSON success envelopes.
Real acceptance should use isolated tasks and test pages, recording manual release/closure and resource cleanup. Do not copy the current user’s session as a test sample.