Cloudflare Workers, without the setup drag.

Read non-secret user-configurable defaults without teaching flat public config like env.MODEL.

Usage: Put public values in .pulse and read them as env.pulse.NAME inside server-side Pulses.

const units = env.pulse.DEFAULT_UNITS || "metric";
const queue = env.pulse.SUPPORT_QUEUE_NAME || "support";
return { units, queue };

Call external APIs without turning your Pulse code into a plain secret viewer.

Usage: Use env.fetch with env.secrets.bearer/header/query so secret values stay policy-bound.

if (!env.secrets.has("PROVIDER_API_KEY")) {
  return { error: "Configure PROVIDER_API_KEY first" };
}

const response = await env.fetch("https://api.example.com/v1/messages", {
  method: "POST",
  auth: env.secrets.bearer("PROVIDER_API_KEY"),
});
return await response.json();

Use connected provider accounts without manually storing provider access tokens inside user code.

Usage: Use setup-reviewed connected accounts for provider calls.

const github = env.connections.use("github");
const me = await github.fetch("/user", {
  headers: { "User-Agent": "vibecodr-pulse" },
});
return await me.json();

Perform outbound HTTP requests through the server-side trust boundary instead of from the client-side vibe.

Usage: Use env.fetch for public outbound calls that should follow platform egress policy.

const res = await env.fetch("https://api.weather.com/v1/forecast?city=SF");
if (!res.ok) {
  return { error: "Upstream error: " + res.status };
}
return await res.json();

Coordinate backend work across Pulse calls on the Workers-backed runtime with stable operation keys.

Usage: Use descriptor-declared state resources with runOnce(), claim(), keyFromRequest(), and guarded effects when repeated calls need to agree on the same protected operation; retentionTtlSeconds controls duplicate-memory retention and is capped by plan. Vibecodr persists the coordination record in platform-owned durable storage, so cold starts do not erase it and idle retention mostly costs tiny stored metadata.

const key = await env.state.httpMutations.keyFromRequest(env.request);

return env.state.httpMutations.runOnce(key, async () => {
  await chargeCustomer();
  return { accepted: true };
});

Write request-scoped logs and inspect sanitized request metadata without platform credential headers.

Usage: Use env.log directly for structured runtime logging. env.waitUntil is only best-effort after-response work, not durable processing.

const requestUrl = new URL(env.request.url);
env.log.info("pulse.request", { path: requestUrl.pathname });
return { received: true, path: requestUrl.pathname };

Inspect the Pulse's creator-facing capability surface without probing raw env bindings or platform internals.

Usage: Use it when the Pulse needs to confirm which public config keys, secret names, provider connections, raw-body routes, state resources, or advanced SQL compatibility were exposed to this deployment.

const caps = env.runtime.capabilities();

return {
  publicConfig: caps.pulse.publicConfigKeys,
  providers: caps.connections.declaredProviders,
  stateResources: caps.state.activeResources,
};