0.35.0

Connecta 0.35.0 brings the provider kit and standard agent surfaces to all 15 maintained providers. Operation search and details expose reviewed API contracts without reading account data; indexed read and write tools complement the retained named tools. Gmail keeps its reviewed exception: draft writes use named tools and sending remains unavailable. Results use consistent list envelopes, narrowing fields, signed continuations and truncation paths. The provider migration guide maps every renamed or removed tool and argument, including retired raw/select arguments, list keys, paging inputs and wrappers replaced by indexed operations. Update saved programs, pool grants, classification entries and deployment instructions before upgrading, and restart old continuations where the guide requires it.

Pools can opt into a native tool surface for clients with their own tool search, retaining the same classification, scope and invocation enforcement. Native pools include execute_code by default; code-off pools provide read_result for bounded result paging. The separate @zackbart/connecta-eve helper supplies an Eve connection, endpoint instructions and an optional host write gate. Explicit Vercel workload bindings can admit declared agents without separately provisioned Connecta tokens. Existing agent tokens remain supported. See native tools and Eve agents and Vercel workload credentials. The helper requires Node 24 and Eve 0.83.x. Eve 0.83.0 apps need their own undici 8.12.3 override; the repository's development override does not ship with the helper. Its package guide gives the operator steps.

Write outcomes now follow the whole logical call's dispatch evidence (H1). A dispatched write with an uncertain result is non-retryable and requires reading the target before another write; a later refusal or caught program error cannot erase earlier uncertainty. Source or effective write classification prevents automatic replay. Signed continuations also bind the admitted caller and pool owner when downstream identity varies by caller, refusing cross-caller continuation before dispatch. Security fixes strengthen credential withholding, response safety, authentication bounds, OAuth state and cancellation while keeping activity records free of request and response payloads.

The core now composes storage, registry and calls, authentication, executors, remote MCP and upward MCP orchestration through native Effect programs. HTTP routes use cached public Effect HttpRouters, and SQLite/D1 execution uses public Effect SQL services. The published API still returns Promises and retains existing database formats. The pinned modern and legacy MCP SDK adapters remain the protocol implementations; this release does not adopt Effect McpServer or add MCP Apps, Tasks, prompts or subscriptions.

On Node, listen() from @zackbart/connecta/node installs the owned sender for every maintained-provider request, reads included, remote MCP writes, and downstream OAuth token, registration and revocation POSTs. Install the template's exact optional peer, undici@6.29.1. A Node host serving connecta.fetch without listen() refuses maintained-provider writes, reviewed POST reads, remote MCP writes and those credential POSTs before sending; these paths worked in 0.34.1. The sender connects directly by default or through an explicit HTTP(S) CONNECT proxy option on listen(). It ignores ambient proxy variables and host dispatchers. Remote MCP reads and OAuth discovery GETs retain native fetch and need their own host proxy policy. An uncertain OAuth refresh requires fresh authorization rather than replaying the spent token. Shutdown closes unused connections and active connections as their responses finish, including SSE. See Node deployment requirements.

Authenticated MCP request bodies now default to a 4 MiB limit on every endpoint. Node's separate pre-auth buffer drops from 10 MiB to 4 MiB; deployments accepting larger bodies must configure both limits. Discovery can find API-only capabilities through bounded operation vocabulary, ranks exact resources across versioned namespaces, and preserves vendor summaries beside a separate reviewed refusal field. Planning Center exposes reliable page totals and respects excluded applications in discovery. Vercel connections can opt into a deployment-owned team pin. The operator UI lists OIDC-only agents and bounded last-seen observations. These additions retain existing classification, caller scope and one-attempt write rules.

The maintained Infisical, Notion and Mixpanel API providers and their package subpaths are removed. Replace Notion and Mixpanel with generic remoteMcp() connections to their hosted servers, then rediscover live tool names, schemas and permissions. Infisical has no packaged replacement; remove it or supply a deployment-owned connector. Hosted connections do not inherit removed providers' API coverage or value-safety projections. Vercel environment-variable value arguments are now writeOnly; hosts must treat them as private write inputs, and reads and write replies withhold their values. The migration guide also covers response-media and numeric-path validation, changed error meanings and each provider's exact upgrade actions.

Deployments using unchanged tools can ignore unrelated provider mappings; deployments without the removed providers need no replacement connections. Existing pools keep the meta-tool surface unless configured otherwise, and deployments without Eve or Vercel-hosted agents need neither new integration. No database conversion or agent-token rotation is required solely for 0.35.0. Workers deployments do not need Node's transport peer or startup changes. Follow Upgrade an existing deployment for the installed-package handoff.