@adcp/sdk API Reference - v7.9.0
    Preparing search index...

    Interface SessionContext

    Pre-resolution session context passed to a function-form instructions. Slim by design — no account (resolution hasn't run yet at MCP initialize time, which is the natural eval moment for per-session instructions).

    Both fields are reserved: today they are always undefined because the framework's serve() does not yet plumb auth + registry state into the factory before MCP initialize. Adopters who need tenant identity should use closures captured in their factory's HTTP-scoped state. The shape is forward-compatible: when the framework wires authInfo/agent through, the fields will populate without breaking existing function bodies.

    AdcpServerConfig.instructions

    interface SessionContext {
        authInfo?: ResolvedAuthInfo;
        agent?: BuyerAgent;
    }
    Index

    Properties

    Properties

    authInfo?: ResolvedAuthInfo

    Always undefined in v6.x. The framework does not yet plumb authInfo into the factory before MCP initialize — use closures captured in your factory's HTTP-scoped state for tenant identity today. Forward-compatible: when the framework wires this through, your ctx.authInfo?.… reads start returning real values without breaking existing function bodies.

    agent?: BuyerAgent

    Always undefined in v6.x. The framework does not yet plumb the resolved BuyerAgent into the factory before MCP initialize — use closures captured in your factory's HTTP-scoped state for tenant identity today. Forward-compatible: when the framework wires this through, your ctx.agent?.… reads start returning real values without breaking existing function bodies.