How do I review TypeScript Montage transport cleanup around direct calls?
A TypeScript client can discover tools and later fail because the transport closes before execution settles. Trace connection ownership and cleanup order using the installed SDK generation, without confusing resource timing with account permission or changing to a server-hosting API as a workaround. Review pending execution relative to connection release, using the installed generation’s documented methods. A real status response before cleanup is stronger evidence than a successful early discovery that occurs before the application closes a needed transport.
Help me review TypeScript Montage transport cleanup around direct calls. Locate transport construction, client connection, tool discovery, direct calls and cleanup. Record which client generation and execution point succeeded, including unresolved cleanup errors. No writes.Map connection ownership
Locate transport construction, client connection, tool discovery, direct calls and cleanup. Check whether asynchronous execution is still pending when the application releases the connection or returns a tool reference to another layer.
Consult generation-matched cleanup
Follow the installed SDK’s documented lifecycle and resource-release methods. Do not guess a close method from another version or copy a server shutdown pattern into an outbound client that has different ownership.
Preserve approved auth scope
Keep the connection associated with its intended user while work is active. A single unbounded global transport is not a safe repair for request-scoped timing problems in applications serving multiple accounts.
Exercise the pending-call boundary
Execute signals_status directly and observe the real response before supported cleanup completes. Distinguish transport closure from a server auth rejection and do not convert either into success-shaped empty workspace output.
Report result and limits
Record which client generation and execution point succeeded, including unresolved cleanup errors. This bounded test needs no model run and does not prove that every later concurrent or hosted application path handles connection disposal correctly.
Keep the boundaries clear.
- A single unbounded global transport is not a safe repair for request-scoped timing problems in applications serving multiple accounts.
- This bounded test needs no model run and does not prove that every later concurrent or hosted application path handles connection disposal correctly.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.