eve 0.22.2 → 0.22.4

package/docs/guides/client/overview.mdx

@@ -19,7 +19,7 @@ const client = new Client({
 });
 ```
 
-`host` is the origin where the eve routes are mounted. In a same-origin browser integration this is often `""`; scripts and backend services usually name the full URL.
+`host` is the URL where the eve routes are mounted. In a same-origin browser integration this is often `""`; scripts and backend services usually name the full URL. Any query parameters on `host` are included on every request, including session POSTs and event streams. Request-specific parameters, such as a stream cursor, take precedence when names overlap.
 
 ## Check health
 

package/docs/guides/dev-tui.md

@@ -136,6 +136,10 @@ eve dev https://user:pass@<your-app>
 
 For bearer tokens or custom schemes, repeat `-H, --header` to attach request headers.
 
+Query parameters in the target URL are preserved on every request, including
+session POSTs and event streams. This also supports deployment-protection URLs
+that carry their bypass credential in the query string.
+
 At startup the TUI asks Vercel to resolve the remote origin under the active scope. A resolved response is the authority for a project-scoped OIDC token—refreshing an expired development token when refresh credentials exist—or an automation-bypass secret. An unresolved host is probed anonymously. The TUI then requests `/eve/v1/info`, with a ten-second timeout. A successful response marks the remote ready. An eve OIDC challenge, Vercel Deployment Protection challenge, or `TRUSTED_SOURCES_ENVIRONMENT_MISMATCH` opens `/vc:login` automatically; ordinary network failures and server errors remain remote-availability errors and do not start an authentication flow. Esc or Ctrl-C cancels the authentication flow.
 
 In a remote session, `/vc:login` first resolves the deployment's Vercel project from its URL. If the active Vercel scope cannot resolve it, the flow asks for another team and reruns the lookup in that team's scope. If the CLI is logged out, the same panel runs the browser login first. The flow asks before adding any required Trusted Sources rule and requests a project-scoped token through `@vercel/oidc`. It does not relink the directory or modify `.env.local`. Finally, it retries `/eve/v1/info` to prove the credential works. A failure reports any login or Trusted Sources update that completed before it stopped.

package/docs/guides/dynamic-capabilities.md

@@ -30,7 +30,7 @@ The example below builds one tool per warehouse table. A map return names each t
 ```ts title="agent/tools/query.ts"
 import { defineDynamic, defineTool } from "eve/tools";
 import { z } from "zod";
-import { listTables, runReadOnly } from "../lib/warehouse.js";
+import { listTables, runReadOnly } from "../lib/warehouse";
 
 export default defineDynamic({
   events: {
@@ -89,7 +89,7 @@ A single file can declare handlers for several events, and the most recently fir
 ```ts title="agent/tools/catalog.ts"
 import { defineDynamic, defineTool } from "eve/tools";
 import { z } from "zod";
-import { runReadOnly, searchCatalog } from "../lib/catalog.js";
+import { runReadOnly, searchCatalog } from "../lib/catalog";
 
 export default defineDynamic({
   events: {
@@ -120,7 +120,7 @@ A dynamic skills file resolves which [skill](../skills) a caller can load, keyed
 
 ```ts title="agent/skills/team_playbook.ts"
 import { defineDynamic, defineSkill } from "eve/skills";
-import { PLAYBOOKS } from "../lib/playbooks.js";
+import { PLAYBOOKS } from "../lib/playbooks";
 
 export default defineDynamic({
   events: {

package/docs/guides/frontend/nextjs.mdx

@@ -30,16 +30,41 @@ export default withEve(nextConfig, {
 });
 ```
 
+For multiple agents, use `agents`. String values are agent roots; object values can override the build command or private production service prefix for that agent:
+
+```ts
+export default withEve(nextConfig, {
+  agents: {
+    support: "./agents/support",
+    billing: {
+      root: "./agents/billing",
+      buildCommand: "pnpm build:billing-agent",
+      servicePrefix: "/_eve_internal/billing",
+    },
+  },
+});
+```
+
+Named agents mount under `/eve/agents/<name>/eve/v1/*`. Call the matching agent from React with `agent`:
+
+```tsx
+const support = useEveAgent({ agent: "support" });
+const billing = useEveAgent({ agent: "billing" });
+```
+
+Use either `eveRoot` or `agents`, not both. `eveRoot` remains the shorthand for a single unnamed agent mounted at `/eve/v1/*`.
+
 ### `withEve` options
 
 All fields are optional.
 
-| Option               | Type     | Default                | Purpose                                                                                                                                                   |
-| -------------------- | -------- | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `eveRoot`            | `string` | Next.js app root       | Path to the eve app root, relative to `process.cwd()` unless absolute. Set it when the agent lives outside the Next.js project.                           |
-| `eveBuildCommand`    | `string` | `"eve build"`          | Build command for the generated eve Vercel service. Use it when the eve service needs project-specific prework, without changing the Next.js build.       |
-| `servicePrefix`      | `string` | `"/_eve_internal/eve"` | Private route namespace for legacy manual Vercel service configs and non-Vercel production proxying. Generated Vercel configs use service routes instead. |
-| `devServerTimeoutMs` | `number` | `180000`               | Maximum time to wait for the eve development server to become available.                                                                                  |
+| Option               | Type                  | Default                | Purpose                                                                                                                                                    |
+| -------------------- | --------------------- | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `eveRoot`            | `string`              | Next.js app root       | Path to one unnamed eve app root, relative to `process.cwd()` unless absolute. Do not combine with `agents`.                                               |
+| `agents`             | `Record<string, ...>` | unset                  | Named eve agents to mount under `/eve/agents/<name>/eve/v1/*`. Each value is a root string or `{ root, buildCommand?, servicePrefix? }`.                   |
+| `eveBuildCommand`    | `string`              | generated              | Build command for generated eve Vercel services. In multi-agent mode this is the default for agents without their own `buildCommand`.                      |
+| `servicePrefix`      | `string`              | `"/_eve_internal/eve"` | Private route namespace for legacy manual Vercel service configs and non-Vercel production proxying. Named agents derive unique defaults from this prefix. |
+| `devServerTimeoutMs` | `number`              | `180000`               | Maximum time to wait for each eve development server to become available.                                                                                  |
 
 For slow cold starts, increase the development timeout:
 
@@ -75,7 +100,7 @@ For a public demo, use `none()` (also from `eve/channels/auth`) to skip authenti
 ## Dev vs deploy topology
 
 - **Local dev.** `npm run dev` boots the eve dev server next to `next dev` and rewrites the eve routes over to it. The browser only ever talks to the Next.js origin.
-- **Vercel.** The web app and the eve runtime deploy as a single project. `withEve()` writes Build Output `services` for eve and `routes` that send `/eve/v1/**` to that service before filesystem routing; the Next.js app itself remains the default app. When the agent needs its own build step, set `eveBuildCommand`:
+- **Vercel.** The web app and the eve runtime deploy as a single project. `withEve()` writes Build Output `services` for eve and `routes` that send `/eve/v1/**` to that service before filesystem routing; the Next.js app itself remains the default app. By default, generated services run the installed eve binary from the agent root, so the agent directory does not need its own `package.json`. When the agent needs its own build step, set `eveBuildCommand`:
 
   ```ts
   export default withEve(nextConfig, {

package/docs/guides/frontend/overview.mdx

@@ -254,7 +254,7 @@ const agent = useEveAgent({
 
 Store the full `session` object (`sessionId`, `continuationToken`, `streamIndex`), not a single field. The session cursor lets eve continue the durable conversation; the event log lets your UI render historical messages without replaying the whole stream. A database-backed chat app should usually persist stream events as they arrive with `onEvent` and then save a final snapshot in `onFinish`.
 
-For multiple chat threads, keep one saved event log and session cursor per thread. `host`, `reducer`, `session`, `initialEvents`, `initialSession`, `auth`, `headers`, `maxReconnectAttempts`, and `optimistic` are read when the hook creates its store, so remount the chat component when switching threads, for example with `key={chat.id}`.
+For multiple chat threads, keep one saved event log and session cursor per thread. `agent`, `host`, `reducer`, `session`, `initialEvents`, `initialSession`, `auth`, `headers`, `maxReconnectAttempts`, and `optimistic` are read when the hook creates its store, so remount the chat component when switching threads, for example with `key={chat.id}`.
 
 If the user can refresh or navigate immediately after pressing send, create your app-level chat row and store the pending user message before calling `send()`. After the request starts, persist the session state as soon as it contains a `sessionId`, then reconnect an interrupted in-flight turn with `session.stream({ startIndex: savedEvents.length })` from the lower-level client.
 
@@ -271,6 +271,12 @@ const agent = useEveAgent({
 });
 ```
 
+When a framework integration mounts multiple named agents, pass `agent` instead of `host`:
+
+```tsx
+const support = useEveAgent({ agent: "support" });
+```
+
 ## Per-framework integration
 
 | Framework | Integration                          | Hook                                             |

package/docs/guides/hooks.md

@@ -71,6 +71,15 @@ export default defineHook({
 
 Returns `undefined` when the result doesn't match, or when `isError` is `true`. For authored tools the return includes `{ output, toolName, callId }` with `output` typed as the tool's `TOutput`. For connections it includes `{ output, toolName, connectionToolName, callId }` with `output` as `unknown`.
 
+This works for a mounted extension's tools too — import the tool from the extension's `./tools` export and pass it. `toolResultFrom` matches the namespaced result (`crm__search`) because it keys off the tool definition, not the name:
+
+```ts
+import { search } from "@acme/crm/tools";
+
+// inside "action.result":
+const crmSearch = toolResultFrom(event.data.result, search); // typed; matches crm__search
+```
+
 ## Execution order
 
 When a stream event fires, three things happen in order:

package/docs/guides/instrumentation.md

@@ -66,7 +66,7 @@ Use it when the values depend on the current session, turn, step, channel, or mo
 
 ```ts
 import { defineInstrumentation, isChannel } from "eve/instrumentation";
-import supportChannel from "./channels/support.js";
+import supportChannel from "./channels/support";
 
 export default defineInstrumentation({
   events: {

package/docs/guides/remote-agents.md

@@ -20,14 +20,29 @@ export default defineRemoteAgent({
 
 `defineRemoteAgent` accepts:
 
-| Parameter      | Type                            | Required | Default           | Description                                                                                                                                     |
-| -------------- | ------------------------------- | -------- | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
-| `url`          | `string`                        | Yes      | n/a               | Base URL of the remote eve deployment to call.                                                                                                  |
-| `description`  | `string`                        | Yes      | n/a               | Model-visible delegation description.                                                                                                           |
-| `auth`         | `OutboundAuthFn`                | No       | none              | Outbound auth hook from `eve/agents/auth`.                                                                                                      |
-| `headers`      | `HeadersValue`                  | No       | none              | Static or lazily resolved request headers.                                                                                                      |
-| `path`         | `string`                        | No       | `/eve/v1/session` | Route appended to `url` for the create-session request.                                                                                         |
-| `outputSchema` | `StandardSchema \| JSON Schema` | No       | none              | Structured return type the caller requires. Lowered to JSON Schema at compile time and enforced by the remote like any task-mode output schema. |
+| Parameter      | Type                                          | Required | Default           | Description                                                                                                                                              |
+| -------------- | --------------------------------------------- | -------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `url`          | `string \| (() => string \| Promise<string>)` | Yes      | n/a               | Base URL of the remote eve deployment to call. A string is baked at compile time; a function is resolved at runtime (see [Runtime URLs](#runtime-urls)). |
+| `description`  | `string`                                      | Yes      | n/a               | Model-visible delegation description.                                                                                                                    |
+| `auth`         | `OutboundAuthFn`                              | No       | none              | Outbound auth hook from `eve/agents/auth`.                                                                                                               |
+| `headers`      | `HeadersValue`                                | No       | none              | Static or lazily resolved request headers.                                                                                                               |
+| `path`         | `string`                                      | No       | `/eve/v1/session` | Route appended to `url` for the create-session request.                                                                                                  |
+| `outputSchema` | `StandardSchema \| JSON Schema`               | No       | none              | Structured return type the caller requires. Lowered to JSON Schema at compile time and enforced by the remote like any task-mode output schema.          |
+
+## Runtime URLs
+
+A string `url` is read at compile time and frozen into the build. When the target comes from a runtime env var — known only once the deployment runs — pass a function instead. eve calls it when it resolves the agent graph at runtime, so it can read `process.env`:
+
+```ts title="agent/subagents/weather.ts"
+import { defineRemoteAgent } from "eve";
+
+export default defineRemoteAgent({
+  url: () => process.env.WEATHER_AGENT_URL ?? "https://weather-agent.example.com",
+  description: "Answers weather, temperature, forecast, wind, rain, and snow questions.",
+});
+```
+
+The function may be async and must return a non-empty string. `auth` and `headers` are resolved at runtime the same way.
 
 ## The lowered tool
 

package/docs/guides/state.md

@@ -27,8 +27,8 @@ export const budget = defineState("my-agent.budget", () => ({ count: 0, cap: 25
 ```ts title="agent/tools/spend.ts"
 import { defineTool } from "eve/tools";
 import { z } from "zod";
-import { budget } from "../lib/budget.js";
-import { runQuery } from "../lib/warehouse.js";
+import { budget } from "../lib/budget";
+import { runQuery } from "../lib/warehouse";
 
 export default defineTool({
   description: "Run a query, counting it against the session budget.",
@@ -50,7 +50,7 @@ State is durable by default and does not reset between turns. If you want a clea
 
 ```ts title="agent/hooks/reset-budget.ts"
 import { defineHook } from "eve/hooks";
-import { budget } from "../lib/budget.js";
+import { budget } from "../lib/budget";
 
 export default defineHook({
   events: {

package/docs/instructions.mdx

@@ -21,7 +21,7 @@ A static prompt belongs in markdown (`agent/instructions.md`). Switch to a TypeS
 
 ```ts title="agent/instructions.ts"
 import { defineInstructions } from "eve/instructions";
-import { buildInstructionsPrompt } from "./lib/prompts.js";
+import { buildInstructionsPrompt } from "./lib/prompts";
 
 export default defineInstructions({
   markdown: buildInstructionsPrompt(),

package/docs/patterns/dynamic-scheduling.md

@@ -30,8 +30,8 @@ This is the only authored schedule. It looks up due application-managed rows and
 
 ```ts title="agent/schedules/dynamic.ts"
 import { defineSchedule } from "eve/schedules";
-import slack from "../channels/slack.js";
-import { scheduleStore } from "../lib/schedule-store.js";
+import slack from "../channels/slack";
+import { scheduleStore } from "../lib/schedule-store";
 
 export default defineSchedule({
   cron: "* * * * *",
@@ -119,8 +119,8 @@ Create a one-time schedule with `everyMinutes: null`, or a recurring one with an
 ```ts title="agent/tools/create_schedule.ts"
 import { defineTool } from "eve/tools";
 import { z } from "zod";
-import { scheduleStore } from "../lib/schedule-store.js";
-import { requireScheduleOwner } from "../lib/tenant.js";
+import { scheduleStore } from "../lib/schedule-store";
+import { requireScheduleOwner } from "../lib/tenant";
 
 export default defineTool({
   description: "Create a one-time or repeating scheduled agent run for this tenant.",
@@ -142,8 +142,8 @@ export default defineTool({
 ```ts title="agent/tools/list_schedules.ts"
 import { defineTool } from "eve/tools";
 import { z } from "zod";
-import { scheduleStore } from "../lib/schedule-store.js";
-import { requireScheduleOwner } from "../lib/tenant.js";
+import { scheduleStore } from "../lib/schedule-store";
+import { requireScheduleOwner } from "../lib/tenant";
 
 export default defineTool({
   description: "List this tenant's dynamic schedules and their latest status.",
@@ -157,8 +157,8 @@ export default defineTool({
 ```ts title="agent/tools/update_schedule.ts"
 import { defineTool } from "eve/tools";
 import { z } from "zod";
-import { scheduleStore } from "../lib/schedule-store.js";
-import { requireScheduleOwner } from "../lib/tenant.js";
+import { scheduleStore } from "../lib/schedule-store";
+import { requireScheduleOwner } from "../lib/tenant";
 
 export default defineTool({
   description: "Change, pause, or resume one of this tenant's schedules.",
@@ -183,8 +183,8 @@ export default defineTool({
 import { defineTool } from "eve/tools";
 import { always } from "eve/tools/approval";
 import { z } from "zod";
-import { scheduleStore } from "../lib/schedule-store.js";
-import { requireScheduleOwner } from "../lib/tenant.js";
+import { scheduleStore } from "../lib/schedule-store";
+import { requireScheduleOwner } from "../lib/tenant";
 
 export default defineTool({
   description: "Permanently delete one of this tenant's schedules.",
@@ -232,7 +232,7 @@ export interface ScheduleStore {
   release(job: ClaimedSchedule, failure: { error: unknown; retryAt: Date }): Promise<void>;
 }
 
-export { scheduleStore } from "../../lib/schedule-store.js";
+export { scheduleStore } from "../../lib/schedule-store";
 ```
 
 Implement that adapter with whichever durable store already belongs to your application. It must preserve a few semantics:

package/docs/patterns/multi-tenant-approvals.md

@@ -22,7 +22,7 @@ The current caller and initiating caller are both available on the session. This
 
 ```ts title="agent/lib/tenant-approval.ts"
 import type { ApprovalContext, ApprovalStatus } from "eve/tools";
-import { approvalPolicies } from "./approval-policies.js";
+import { approvalPolicies } from "./approval-policies";
 
 type Surface = "connection" | "tool";
 
@@ -77,8 +77,8 @@ Approval runs before `execute`. The executor must still derive and enforce tenan
 ```ts title="agent/tools/transfer_funds.ts"
 import { defineTool } from "eve/tools";
 import { z } from "zod";
-import { transferFunds } from "../../lib/payments.js";
-import { decideTenantApproval } from "../lib/tenant-approval.js";
+import { transferFunds } from "../../lib/payments";
+import { decideTenantApproval } from "../lib/tenant-approval";
 
 export default defineTool({
   description: "Transfer funds from the current tenant's account.",
@@ -111,7 +111,7 @@ The same callback gates every generated operation. The qualified operation name
 
 ```ts title="agent/connections/billing.ts"
 import { defineOpenAPIConnection } from "eve/connections";
-import { decideTenantApproval } from "../lib/tenant-approval.js";
+import { decideTenantApproval } from "../lib/tenant-approval";
 
 export default defineOpenAPIConnection({
   spec: "https://billing.example.com/openapi.json",
@@ -135,7 +135,7 @@ The allow-list limits what the model can discover. Approval independently decide
 
 ```ts title="agent/connections/support.ts"
 import { defineMcpClientConnection } from "eve/connections";
-import { decideTenantApproval } from "../lib/tenant-approval.js";
+import { decideTenantApproval } from "../lib/tenant-approval";
 
 export default defineMcpClientConnection({
   url: "https://support.example.com/mcp",
@@ -176,7 +176,7 @@ export interface ApprovalPolicyProvider {
   decide(request: ApprovalPolicyRequest): Promise<ApprovalPolicyDecision>;
 }
 
-export { approvalPolicies } from "../../lib/approval-policies.js";
+export { approvalPolicies } from "../../lib/approval-policies";
 ```
 
 Your provider decides the policy model. A common implementation checks active tenant membership, finds an exact resource rule before a connection-wide fallback, evaluates role and input thresholds, and defaults to deny. Keep those choices in application code rather than encoding a database design into the agent.

package/docs/patterns/multi-tenant-auth.md

@@ -44,7 +44,7 @@ the caller before eve starts a run, then stamp the tenant onto the session:
 ```ts title="agent/channels/eve.ts"
 import { eveChannel } from "eve/channels/eve";
 import { localDev, type AuthFn } from "eve/channels/auth";
-import { verifyAgentCaller } from "../../lib/app-auth.js";
+import { verifyAgentCaller } from "../../lib/app-auth";
 
 function tenantAppAuth(): AuthFn<Request> {
   return async (request) => {
@@ -92,7 +92,7 @@ cache by that user, and pass the projected principal into `getToken`:
 
 ```ts title="agent/lib/tenant-connection-auth.ts"
 import type { ConnectionPrincipal, NonInteractiveAuthorizationDefinition } from "eve/connections";
-import { tenantCredentials, type TenantService } from "./tenant-credentials.js";
+import { tenantCredentials, type TenantService } from "./tenant-credentials";
 
 function requireTenantPrincipal(principal: ConnectionPrincipal): {
   tenantId: string;
@@ -136,8 +136,8 @@ Derive the tenant inside `execute`, fetch its credential from your application p
 ```ts title="agent/tools/list_invoices.ts"
 import { defineTool } from "eve/tools";
 import { z } from "zod";
-import { tenantCredentials } from "../lib/tenant-credentials.js";
-import { requireTenantCaller } from "../lib/tenant.js";
+import { tenantCredentials } from "../lib/tenant-credentials";
+import { requireTenantCaller } from "../lib/tenant";
 
 export default defineTool({
   description: "List recent invoices from the current tenant's billing account.",
@@ -167,9 +167,9 @@ receive the token at call time without exposing it to the model:
 
 ```ts title="agent/connections/billing.ts"
 import { defineOpenAPIConnection } from "eve/connections";
-import { tenantCredentials } from "../lib/tenant-credentials.js";
-import { tenantBearerAuth } from "../lib/tenant-connection-auth.js";
-import { requireTenantCaller } from "../lib/tenant.js";
+import { tenantCredentials } from "../lib/tenant-credentials";
+import { tenantBearerAuth } from "../lib/tenant-connection-auth";
+import { requireTenantCaller } from "../lib/tenant";
 
 export default defineOpenAPIConnection({
   spec: "https://billing.example.com/openapi.json",
@@ -193,9 +193,9 @@ MCP connections accept the same callbacks:
 
 ```ts title="agent/connections/support.ts"
 import { defineMcpClientConnection } from "eve/connections";
-import { tenantCredentials } from "../lib/tenant-credentials.js";
-import { tenantBearerAuth } from "../lib/tenant-connection-auth.js";
-import { requireTenantCaller } from "../lib/tenant.js";
+import { tenantCredentials } from "../lib/tenant-credentials";
+import { tenantBearerAuth } from "../lib/tenant-connection-auth";
+import { requireTenantCaller } from "../lib/tenant";
 
 export default defineMcpClientConnection({
   url: "https://support.example.com/mcp",
@@ -220,8 +220,8 @@ tenant API key from `headers` instead:
 
 ```ts title="agent/connections/support.ts"
 import { defineMcpClientConnection } from "eve/connections";
-import { tenantCredentials } from "../lib/tenant-credentials.js";
-import { requireTenantCaller } from "../lib/tenant.js";
+import { tenantCredentials } from "../lib/tenant-credentials";
+import { requireTenantCaller } from "../lib/tenant";
 
 export default defineMcpClientConnection({
   url: "https://support.example.com/mcp",
@@ -274,7 +274,7 @@ export interface TenantCredentialProvider {
   ): Promise<TenantApiKeyCredential>;
 }
 
-export { tenantCredentials } from "../../lib/tenant-credentials.js";
+export { tenantCredentials } from "../../lib/tenant-credentials";
 ```
 
 Implement the provider with the secret system your application already trusts:

package/docs/patterns/multi-tenant-memory.md

@@ -53,8 +53,8 @@ Resolve on `turn.started` so later turns in the same session see memories writte
 
 ```ts title="agent/instructions/memory.ts"
 import { defineDynamic, defineInstructions } from "eve/instructions";
-import { memoryStore } from "../lib/memory-store.js";
-import { requireTenantCaller } from "../lib/tenant.js";
+import { memoryStore } from "../lib/memory-store";
+import { requireTenantCaller } from "../lib/tenant";
 
 export default defineDynamic({
   events: {
@@ -88,8 +88,8 @@ The model chooses the memory key and value. The executor chooses the tenant and
 ```ts title="agent/tools/remember.ts"
 import { defineTool } from "eve/tools";
 import { z } from "zod";
-import { memoryStore } from "../lib/memory-store.js";
-import { requireTenantCaller } from "../lib/tenant.js";
+import { memoryStore } from "../lib/memory-store";
+import { requireTenantCaller } from "../lib/tenant";
 
 export default defineTool({
   description: "Remember one stable fact or preference for the current user.",
@@ -110,8 +110,8 @@ export default defineTool({
 ```ts title="agent/tools/list_memories.ts"
 import { defineTool } from "eve/tools";
 import { z } from "zod";
-import { memoryStore } from "../lib/memory-store.js";
-import { requireTenantCaller } from "../lib/tenant.js";
+import { memoryStore } from "../lib/memory-store";
+import { requireTenantCaller } from "../lib/tenant";
 
 export default defineTool({
   description: "List long-term memories saved for the current user.",
@@ -126,8 +126,8 @@ export default defineTool({
 import { defineTool } from "eve/tools";
 import { always } from "eve/tools/approval";
 import { z } from "zod";
-import { memoryStore } from "../lib/memory-store.js";
-import { requireTenantCaller } from "../lib/tenant.js";
+import { memoryStore } from "../lib/memory-store";
+import { requireTenantCaller } from "../lib/tenant";
 
 export default defineTool({
   description: "Delete one long-term memory belonging to the current user.",
@@ -165,7 +165,7 @@ export interface MemoryStore {
 }
 
 // Implement this with your application's PostgreSQL, KV, or vector-store client.
-export { memoryStore } from "../../lib/memory-store.js";
+export { memoryStore } from "../../lib/memory-store";
 ```
 
 Whatever backend you choose, preserve these invariants:

package/docs/schedules.mdx

@@ -61,7 +61,7 @@ Use a handler when the schedule needs to deliver to a channel, branch on conditi
 ```ts title="agent/schedules/critical-alerts.ts"
 import { defineSchedule } from "eve/schedules";
 
-import slack from "../channels/slack.js";
+import slack from "../channels/slack";
 
 export default defineSchedule({
   cron: "* * * * *",

package/docs/tutorial/guard-the-spend.mdx

@@ -23,8 +23,8 @@ export function estimateScanGb(sql: string): number {
 ```ts title="agent/tools/run_sql.ts"
 import { defineTool } from "eve/tools";
 import { z } from "zod";
-import { runReadOnlySql } from "../lib/sample-db.js";
-import { estimateScanGb } from "../lib/cost.js";
+import { runReadOnlySql } from "../lib/sample-db";
+import { estimateScanGb } from "../lib/cost";
 
 const THRESHOLD_GB = 50;
 

package/docs/tutorial/query-sample-data.mdx

@@ -47,7 +47,7 @@ export async function runReadOnlySql(sql: string) {
 ```ts title="agent/tools/run_sql.ts"
 import { defineTool } from "eve/tools";
 import { z } from "zod";
-import { runReadOnlySql } from "../lib/sample-db.js";
+import { runReadOnlySql } from "../lib/sample-db";
 
 export default defineTool({
   description:

package/docs/tutorial/remember-definitions.mdx

@@ -26,7 +26,7 @@ export const glossary = defineState<Glossary>("analytics.glossary", () => ({
 ```ts title="agent/tools/define_metric.ts"
 import { defineTool } from "eve/tools";
 import { z } from "zod";
-import { glossary } from "../lib/glossary.js";
+import { glossary } from "../lib/glossary";
 
 export default defineTool({
   description: "Record the team's definition of a metric so it persists across turns.",
@@ -41,7 +41,7 @@ export default defineTool({
 ```ts title="agent/tools/recall_metrics.ts"
 import { defineTool } from "eve/tools";
 import { z } from "zod";
-import { glossary } from "../lib/glossary.js";
+import { glossary } from "../lib/glossary";
 
 export default defineTool({
   description: "Read the team's recorded metric definitions.",

package/docs/tutorial/ship-it.mdx

@@ -98,7 +98,7 @@ Now point the channel at it. Replace the contents of `agent/channels/eve.ts`, wh
 ```ts title="agent/channels/eve.ts"
 import { eveChannel } from "eve/channels/eve";
 import { localDev, vercelOidc, type AuthFn } from "eve/channels/auth";
-import { authenticate } from "../lib/auth.js";
+import { authenticate } from "../lib/auth";
 
 const appAuth: AuthFn<Request> = async (request) => {
   const user = await authenticate(request); // your cookie/session/provider

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eve",
-  "version": "0.22.2",
+  "version": "0.22.4",
   "private": false,
   "description": "Filesystem-first framework for durable backend AI agents that run anywhere.",
   "keywords": [
@@ -186,6 +186,11 @@
       "import": "./dist/src/public/context/index.js",
       "default": "./dist/src/public/context/index.js"
     },
+    "./extension": {
+      "types": "./dist/src/public/extension/index.d.ts",
+      "import": "./dist/src/public/extension/index.js",
+      "default": "./dist/src/public/extension/index.js"
+    },
     "./instrumentation": {
       "types": "./dist/src/public/instrumentation/index.d.ts",
       "import": "./dist/src/public/instrumentation/index.js",