BuilderIO/agent-native @agent-native/core@0.146.6

on GitHub

Patch Changes

• a882a53: Make a slow cold-start response diagnosable from one look. HTTP telemetry now
  reports the pre-handler boot phases (boot_to_module_ms, module_to_request_ms)
  that no in-handler measurement can see, logs one structured line to stdout for
  every cold or slow (>=1s) request, and stops putting live-looking per-phase
  server-timing entries on shared-cacheable responses — a CDN replays those
  bytes, so a cacheable response now carries a single origin entry stamped with
  the wall-clock time of the render that produced it.
• a882a53: Stop MCP hydration from running on every serverless cold start. Eager
  initialization now only happens on long-lived runtimes; serverless functions
  initialize on first use from the agent-chat handler, the MCP management routes,
  and the recurring-jobs sweep. The 60-second MCP config refresh timer is gated by
  shouldDisableInProcessSweeps() like the other in-process sweeps, and an
  unreadable settings table now rejects with McpConfigUnreadableError instead of
  being coerced into "no MCP servers configured".
• a882a53: Stop inlining the translation catalog into the render-blocking locale init
  script. getLocaleInitScript() now emits only locale, preference, and
  dir; the catalog already reaches AgentNativeI18nProvider through loader data
  as initialMessages. The messages option is removed — passing it is now a
  type error rather than a silently duplicated payload.
• a882a53: Provision recurring scheduler health during release migrations so serverless background sweeps can execute scheduled automations.
• a882a53: Stop shipping the serverless browser runtime into apps that cannot use it. The
  Chromium/Playwright copy now runs only when the app itself depends on the
  browser runtime, instead of resolving a sibling workspace package's Chromium
  through the pnpm store. Serverless function dirs also drop prebuilds that cannot
  execute on Linux x64/arm64 and any local data/ SQLite database before the
  extra Netlify functions are cloned, and the Netlify deploy guard now reports
  per-function sizes and fails when one exceeds its budget.