Pipedream

Platform surfaces

Supported locally

Wrap client.proxy with clientAdapter in your Node runtime. The offline fixture exercises the actual proxy client with a synthetic local transport.

Planned

Partner publication and hosted/provider qualification remain pending.

Unsupported / unqualified

Wrapping a container does not discover nested clients. Auth and storage helpers are outside the guard; hidden provider calls are not inspected.

Observe before enabling repair.

1. Build the unpublished local package. Select the supported adapter and explicitly identify write or ambiguous operations; generic callables default to read.
2. Await readiness and supply scoped detection selections. Detection is off until you configure it; watch warming and bypass events.
3. Review request/response evidence in observe. Enabling repair requires an explicit trusted engine, confidence and verification; changing mode does not add a repair implementation.
4. Review completed dispatch and idempotency evidence before any caller-authorized replay. A response halt cannot roll back an upstream action.

Node Fetch inspection requires complete JSON with known content length and a bounded copy. Chunked, unknown-length and non-JSON bodies skip inspection; incoming Node streams are not consumed or repaired.

Adoption order / Pipedream → LangChain → Nango → Mastra