Skip to content

Local A/B adapters / limited C codegen

Nango

Choose an accessible execution boundary, start in observe mode, then verify detector readiness before relying on policy decisions.

Platform surfaces

Supported locally
Surface A: clientAdapter on HTTP proxy methods. Surface B: bounded JSON in a customer Node proxy script through httpAdapter. Surface C: zero-dependency codegen for supported action/sync exec bodies; only explicitly confirmed same-type request sibling renames may repair.
Planned
Hosted snapshot delivery, runtime opt-out delivery, partner adoption and deployed Nango qualification remain pending.
Unsupported / unqualified
No npm in the action/sync sandbox. Never guard batchSave, getCheckpoint or saveCheckpoint. Codegen has no statistics, learned invariants, automatic conversions, hosted audit or write-integrity proof; arrays, deep paths and incomplete captures are unavailable.
Authoritative setup and limitations ↗Local evidence ↗

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.

Protection, evidence and deployment prerequisites →

Adoption order / Pipedream → LangChain → Nango → Mastra

Compare all platform surfaces →