Eve

https://eve.dev/docs
Admin
Eve is a framework for building durable agents as ordinary files in a TypeScript project, allowing...
Tokens:89,873
Snippets:1,177
Trust Score:5.1
Update:3 months ago
Show doc for...
Tokens:
Raw
### Start Development Server

Source: https://eve.dev/docs/reference/cli

Basic usage for starting the development server or connecting to a remote URL.

```bash
eve dev [options]
eve dev https://your-app.vercel.app
```

--------------------------------

### Build and Start Node Service

Source: https://eve.dev/docs/guides/deployment

Build the application and start it as a Node.js service, specifying the host and port.

```bash
eve build
PORT=3000 eve start --host 0.0.0.0
```

--------------------------------

### Install dependencies

Source: https://eve.dev/docs/getting-started

Install the core Eve package along with the required ai and zod libraries.

```bash
npm install eve@latest ai zod
```

--------------------------------

### Start development server with eve start

Source: https://eve.dev/docs/reference/cli

Serves the previously built output on a specified host and port. Defaults to all interfaces and port 3000 if not provided.

```bash
eve start [--host <host>] [--port <port>]
```

--------------------------------

### Run the development server

Source: https://eve.dev/docs/tutorial/first-agent

Start the local development runtime.

```bash
npm run dev
```

--------------------------------

### Install Chat SDK dependencies

Source: https://eve.dev/docs/channels/chat-sdk

Install the core eve package, the Chat SDK, a specific platform adapter, and a state store adapter.

```bash
npm install eve@latest chat @resend/chat-sdk-adapter @chat-adapter/state-memory
```

--------------------------------

### eve start

Source: https://eve.dev/docs/reference/cli

Serves the previously built output on a specified host and port.

```APIDOC
## eve start

### Description
Serves the previously built output. Prints the listening URL.

### Usage
`eve start [--host <host>] [--port <port>]`

### Parameters
- **--host** (string) - Optional - Host interface to bind (Default: all interfaces)
- **--port** (number) - Optional - Port to listen on (Default: $PORT, then 3000)
```

--------------------------------

### eve extension init

Source: https://eve.dev/docs/reference/cli

Initializes a new extension package, installs dependencies, and sets up Git.

```APIDOC
## eve extension init

### Description
Creates a new extension package, installs dependencies, and initializes Git. This command cannot target an existing project that already contains a package.json.

### Usage
`eve extension init [target]`

### Arguments
- **target** (string) - Optional - The directory to initialize. If omitted, defaults to the current directory.
```

--------------------------------

### Install and Configure Vercel Connect

Source: https://eve.dev/docs/connections/mcp

CLI commands to install the Vercel Connect package and link a connector to your project.

```bash
npm install @vercel/connect
vercel link
vercel connect create mcp.linear.app --name linear
vercel connect attach <connector-uid> --yes
vercel env pull
```

--------------------------------

### Install provider package

Source: https://eve.dev/docs/agent-config

Installs the necessary AI SDK provider package for direct model configuration.

```bash
npm install @ai-sdk/anthropic
```

--------------------------------

### Install GitHub channel package

Source: https://eve.dev/docs/channels/github

Install the required dependency to enable GitHub channel connectivity.

```bash
npm install @vercel/connect
```

--------------------------------

### TUI Startup Output

Source: https://eve.dev/docs/guides/dev-tui

Example of the brand line and tip displayed upon TUI initialization.

```text
 eve weather-agent
 Use /channels to add more ways to reach your agent.
```

--------------------------------

### Re-resolve dynamic tools on turn start

Source: https://eve.dev/docs/guides/dynamic-capabilities

Demonstrates replacing tools defined at session start with new tools at the start of each turn.

```ts
import { defineDynamic, defineTool } from "eve/tools";
import { z } from "zod";
import { runReadOnly, searchCatalog } from "../lib/catalog";

export default defineDynamic({
  events: {
    "session.started": async (_event, ctx) => ({
      query: defineTool({
        description: "Run a read-only query.",
        inputSchema: z.object({ sql: z.string() }),
        execute: ({ sql }) => runReadOnly(sql),
      }),
    }),
    // On each turn, re-resolve. Replaces this file's session.started tools for later calls.
    "turn.started": async (_event, ctx) => ({
      search: defineTool({
        description: "Search the catalog.",
        inputSchema: z.object({ term: z.string() }),
        execute: ({ term }) => searchCatalog(term),
      }),
    }),
  },
});
```

--------------------------------

### POST /eve/v1/session

Source: https://eve.dev/docs/channels/eve

Starts a new session with the agent.

```APIDOC
## POST /eve/v1/session

### Description
Starts a new session with the agent.

### Method
POST

### Endpoint
/eve/v1/session

### Request Body
- **message** (string) - Required - The initial message to start the session.
```

--------------------------------

### Example query

Source: https://eve.dev/docs/tutorial/first-agent

A sample question to test the agent's persona response.

```text
What's a good way to measure week-over-week retention?
```

--------------------------------

### Run the Eve application

Source: https://eve.dev/docs/getting-started

Commands to start the local development runtime using either a scaffolded script or the binary directly.

```bash
npm run dev
```

```bash
npx eve dev
```

--------------------------------

### Initialize an extension package

Source: https://eve.dev/docs/reference/cli

Scaffolds a new extension package, installs dependencies, and initializes Git. Cannot be run in a directory that already contains a package.json.

```bash
eve extension init [target]
```

--------------------------------

### Start the Dev TUI

Source: https://eve.dev/docs/guides/dev-tui

Launch the local runtime and interactive terminal UI.

```bash
eve dev
```

--------------------------------

### Install Workflow World Package

Source: https://eve.dev/docs/agent-config

Install the specific workflow world package, ensuring the version matches the current eve release line.

```bash
pnpm add @workflow/world-postgres@5.0.0-beta.x
```

--------------------------------

### POST /eve/v1/session

Source: https://eve.dev/docs/getting-started

Starts a new durable session with the Eve application.

```APIDOC
## POST /eve/v1/session

### Description
Starts a new durable session. Returns a continuation token and a session ID header.

### Method
POST

### Endpoint
/eve/v1/session

### Request Body
- **message** (string) - Required - The initial message to start the session.

### Response
#### Success Response (200)
- **continuationToken** (string) - Token used to resume the conversation.
- **x-eve-session-id** (header) - Unique identifier for the session.
```

--------------------------------

### Initialize a new eve agent

Source: https://eve.dev/docs/getting-started

Use npx to scaffold a new agent project in a specified directory without requiring a global installation.

```bash
npx eve@latest init my-agent
```

--------------------------------

### Configure Slack Connect via CLI

Source: https://eve.dev/docs/channels/slack

Use these commands to install the Vercel CLI, create a Slack client, and attach it to the specific agent route.

```bash
npm install -g vercel@latest
vercel connect create slack --triggers
vercel connect detach <uid> --yes
vercel connect attach <uid> --triggers --trigger-path /eve/v1/slack --yes
```

--------------------------------

### Directory Structure for Evals

Source: https://eve.dev/docs/evals/cases

Example of how to organize evaluation files and shared helper modules within a project directory.

```text
evals/
├── evals.config.ts
├── weather/
│   ├── shared.ts                    # helpers, not an eval
│   ├── brooklyn-forecast.eval.ts
│   └── no-tools-for-greetings.eval.ts
└── smoke.eval.ts
```

--------------------------------

### Configure Linear Connect via CLI

Source: https://eve.dev/docs/channels/linear

Use these commands to install the Vercel CLI, create a Linear Connect client, and attach it to the eve Linear route.

```bash
npm install -g vercel@latest
vercel connect create linear --triggers
vercel connect detach <uid> --yes
vercel connect attach <uid> --triggers --trigger-path /eve/v1/linear --yes
```

--------------------------------

### Initialize Teams Channel

Source: https://eve.dev/docs/channels/teams

Basic setup for the Teams channel in your agent configuration.

```ts
import { teamsChannel } from "eve/channels/teams";

export default teamsChannel();
```

--------------------------------

### Configure GitHub Connect via CLI

Source: https://eve.dev/docs/channels/github

Commands to install Vercel CLI, create a GitHub Connect client, and attach it to the agent's GitHub route.

```bash
npm install -g vercel@latest
vercel connect create github --triggers
vercel connect detach <uid> --yes
vercel connect attach <uid> --triggers --trigger-path /eve/v1/github --yes
```

--------------------------------

### Configure Vercel Connect CLI

Source: https://eve.dev/docs/connections/openapi

Commands to install and link a Vercel connector for OAuth-backed APIs.

```bash
npm install @vercel/connect
vercel link
vercel connect create github --name github
vercel connect attach <connector-uid> --yes
vercel env pull
```

--------------------------------

### Start a durable session

Source: https://eve.dev/docs/getting-started

Initiate a new conversation session with the Eve app via an HTTP POST request.

```bash
curl -X POST http://127.0.0.1:2000/eve/v1/session \
  -H 'content-type: application/json' \
  -d '{"message":"What is the weather in Brooklyn?"}'
```

--------------------------------

### send(input, options)

Source: https://eve.dev/docs/channels/chat-sdk

Starts or resumes an eve session. The thread parameter ensures replies are routed back to the originating thread.

```APIDOC
## send(input, options)

### Description
Starts or resumes an eve session. The `thread` parameter determines the continuation token and persisted channel state.

### Parameters
- **input** (string|UserContent[]) - Required - The message text or AI SDK UserContent array.
- **options** (object) - Optional - Configuration object.
  - **thread** (object) - Optional - The current thread instance.
  - **auth** (object) - Optional - Authenticated principal to attach to the turn.
  - **title** (string) - Optional - Display title for the session.
  - **mode** (string) - Optional - Session mode.
  - **callback** (function) - Optional - Callback function.
  - **adapterName** (string) - Optional - Name of the adapter to use.
```

--------------------------------

### Start a session via HTTP

Source: https://eve.dev/docs/concepts/sessions-runs-and-streaming

Initiates a new session by sending a message to the session endpoint. The response includes a sessionId and a continuationToken for subsequent interactions.

```bash
curl -X POST http://127.0.0.1:3000/eve/v1/session \
  -H 'content-type: application/json' \
  -d '{"message":"Summarize the latest forecast."}'
```

--------------------------------

### Run Analysis Prompt

Source: https://eve.dev/docs/tutorial/run-analysis

Example prompt to ask the analytics assistant to perform an analysis beyond plain SQL, such as plotting total order revenue per customer. This leverages the seeded schema and custom tools like chart_series.

```text
Plot total order revenue per customer.
```

--------------------------------

### GET /eve/v1/info

Source: https://eve.dev/docs/concepts/sessions-runs-and-streaming

Returns a JSON snapshot of the running agent's configuration, including model details, tools, skills, and workspace metadata.

```APIDOC
## GET /eve/v1/info

### Description
Returns a JSON inspection snapshot for the running agent.

### Method
GET

### Endpoint
/eve/v1/info
```

--------------------------------

### Start an agent session via curl

Source: https://eve.dev/docs/channels/eve

Initiate a new session by sending a POST request to the session endpoint. The response includes a sessionId and continuationToken for subsequent interactions.

```bash
curl -X POST https://<deployment>/eve/v1/session \
  -H "Content-Type: application/json" \
  -d '{"message":"What is the weather in Paris?"}'
```

--------------------------------

### Initialize a new extension

Source: https://eve.dev/docs/extensions

Use the CLI to scaffold a new extension project with the necessary directory structure and configuration files.

```bash
npx eve@latest extension init my-crm
```

--------------------------------

### Create a Client instance

Source: https://eve.dev/docs/guides/client/overview

Initialize a client with a host URL. Query parameters on the host are included in all requests.

```ts
import { Client } from "eve/client";

const client = new Client({
  host: "http://127.0.0.1:3000",
});
```

--------------------------------

### Initialize an Eve project

Source: https://eve.dev/docs/reference/cli

Scaffold a new agent application or add agent dependencies to an existing directory.

```bash
eve init [target] [--channel-web-nextjs]
```

--------------------------------

### GET /eve/v1/info

Source: https://eve.dev/docs/channels/eve

Retrieves information about the agent.

```APIDOC
## GET /eve/v1/info

### Description
Retrieves information about the agent.

### Method
GET

### Endpoint
/eve/v1/info
```

--------------------------------

### GET /eve/v1/health

Source: https://eve.dev/docs/channels/eve

Checks the health status of the agent.

```APIDOC
## GET /eve/v1/health

### Description
Returns the health status of the agent.

### Method
GET

### Endpoint
/eve/v1/health
```

--------------------------------

### Add eve to an existing project

Source: https://eve.dev/docs/getting-started

Run the initialization command in the root of an existing project to add eve dependencies.

```bash
eve init .
```

--------------------------------

### receive

Source: https://eve.dev/docs/channels/github

Starts a proactive session without an inbound mention.

```APIDOC
## receive(channel, { message, target, auth })

### Description
Initiates a session proactively. The target must include the repository owner, repo name, and either an issue number or pull request number.

### Parameters
- **channel** (object) - Required - The GitHub channel instance.
- **message** (string) - Required - The message to send.
- **target** (object) - Required - Target object containing `owner`, `repo`, and `issueNumber` or `pullRequestNumber`.
- **auth** (object) - Required - Authentication context.
```

--------------------------------

### Define system instructions

Source: https://eve.dev/docs/getting-started

Create the system prompt file to define the agent's behavior.

```md
You are a concise assistant. Use tools when they are available.
```

--------------------------------

### Scaffold the agent project

Source: https://eve.dev/docs/tutorial/first-agent

Initialize a new Eve project directory and navigate into it.

```bash
npx eve@latest init analytics-assistant
cd analytics-assistant
```

--------------------------------

### GET /eve/v1/session/:sessionId/stream

Source: https://eve.dev/docs/channels/eve

Streams events from a session as newline-delimited JSON.

```APIDOC
## GET /eve/v1/session/:sessionId/stream

### Description
Streams events from a session as newline-delimited JSON (NDJSON).

### Method
GET

### Endpoint
/eve/v1/session/:sessionId/stream

### Parameters
#### Path Parameters
- **sessionId** (string) - Required - The ID of the session.
```

--------------------------------

### eve init

Source: https://eve.dev/docs/reference/cli

Initializes a new agent project or adds agent functionality to an existing directory.

```APIDOC
## eve init

### Description
Creates a new agent app or adds an agent to an existing app. This command installs necessary dependencies and initializes Git for new directories.

### Usage
`eve init [target] [--channel-web-nextjs]`

### Arguments
- **target** (string) - Optional - The directory name for a new project or '.' to initialize in the current directory.

### Flags
- **--channel-web-nextjs** (flag) - Optional - Adds the Web Chat app (Next.js). Note: This is not for existing projects; use 'eve channels add web' for those.
```

--------------------------------

### Override Stream Start Index

Source: https://eve.dev/docs/guides/client/streaming

Overrides the stored cursor by providing a specific startIndex when streaming.

```ts
for await (const event of session.stream({ startIndex: 0 })) {
  console.log(event.type);
}
```

--------------------------------

### Deploy to Vercel

Source: https://eve.dev/docs/guides/deployment

Use the Vercel CLI to deploy the application.

```bash
vercel deploy
```

--------------------------------

### Adjust development server timeout

Source: https://eve.dev/docs/guides/frontend/nextjs

Increase the devServerTimeoutMs option to accommodate slow cold starts during development.

```ts
export default withEve(nextConfig, {
  devServerTimeoutMs: 300_000,
});
```

--------------------------------

### Check agent health

Source: https://eve.dev/docs/guides/client/overview

Verify agent availability before starting a session. Non-2xx responses throw a ClientError.

```ts
const health = await client.health();
console.log(health.status, health.workflowId);
```

--------------------------------

### Model-authored workflow logic

Source: https://eve.dev/docs/guides/dynamic-workflows

Example of JavaScript authored by the model to fan out subagent calls and merge results.

```js
const metrics = ["revenue", "signups", "churn"];
const findings = await Promise.all(
  metrics.map((metric) => tools.analyst({ message: `Summarize last week's ${metric}.` })),
);
return findings.join("\n\n");
```

--------------------------------

### Build an extension package

Source: https://eve.dev/docs/reference/cli

Compiles the mount factory and tool re-exports into the dist/ directory. Requires the package.json to contain an eve.extension definition.

```bash
eve extension build
```

--------------------------------

### Deploy Slack channel

Source: https://eve.dev/docs/channels/slack

Deploy the application with the experimental framework flag enabled.

```bash
VERCEL_USE_EXPERIMENTAL_FRAMEWORKS=1 vercel deploy --prod
```

--------------------------------

### Define memory usage instructions

Source: https://eve.dev/docs/patterns/multi-tenant-memory

Provides system instructions to guide the model on what data is appropriate for long-term storage.

```markdown
Use long-term memory only for durable preferences and facts that will help in
future sessions. Never save passwords, access tokens, payment data, private
keys, or one-time codes. Tell the user when you save or delete a memory.
```

--------------------------------

### Scaffold a channel with eve channels add

Source: https://eve.dev/docs/reference/cli

Creates a new channel in the agent/channels/ directory. Use the kind argument to bypass interactive prompts.

```bash
eve channels add [kind] [-f] [-y]
```

--------------------------------

### Use state in a tool

Source: https://eve.dev/docs/guides/state

Access and modify state within a tool's execution context using get() and update().

```ts
import { defineTool } from "eve/tools";
import { z } from "zod";
import { budget } from "../lib/budget";
import { runQuery } from "../lib/warehouse";

export default defineTool({
  description: "Run a query, counting it against the session budget.",
  inputSchema: z.object({ sql: z.string() }),
  async execute({ sql }) {
    const { count, cap } = budget.get();
    if (count >= cap) throw new Error("Query budget exhausted for this session.");
    budget.update((s) => ({ ...s, count: s.count + 1 }));
    return runQuery(sql);
  },
});
```

--------------------------------

### Define an eval with defineEval

Source: https://eve.dev/docs/evals/overview

Example of defining an eval that sends a message to the agent and asserts on the tool usage and reply content.

```ts
import { defineEval } from "eve/evals";
import { includes } from "eve/evals/expect";

export default defineEval({
  description: "Basic message and tool-usage coverage for the weather agent.",
  async test(t) {
    await t.send("What is the weather in Brooklyn?");
    t.succeeded();
    t.calledTool("get_weather");
    t.check(t.reply, includes("Sunny"));
  },
});
```

--------------------------------

### ctx.github.request

Source: https://eve.dev/docs/channels/github

Makes an arbitrary API call to the GitHub API using installation-token authentication.

```APIDOC
## ctx.github.request({ method, path, body })

### Description
Executes a direct request to the GitHub API for operations not explicitly wrapped by the channel.

### Parameters
- **method** (string) - Required - HTTP method (e.g., GET, POST).
- **path** (string) - Required - The API endpoint path.
- **body** (object) - Optional - The request payload.
```

--------------------------------

### List project channels with eve channels list

Source: https://eve.dev/docs/reference/cli

Displays all user-authored channels within the current project, with an option for JSON output.

```bash
eve channels list [--json]
```

--------------------------------

### Deploy Project

Source: https://eve.dev/docs/channels/chat-sdk

Command to link the project and deploy to Vercel production.

```bash
eve deploy
```

--------------------------------

### Stream session events via curl

Source: https://eve.dev/docs/channels/eve

Consume session events as newline-delimited JSON by performing a GET request to the stream endpoint.

```bash
curl -N https://<deployment>/eve/v1/session/ses_01h.../stream
```

--------------------------------

### Add Web Channel

Source: https://eve.dev/docs/tutorial/ship-it

Scaffold a Next.js web frontend for the agent.

```bash
npx eve channels add web
```

--------------------------------

### Build the agent

Source: https://eve.dev/docs/guides/deployment

Compiles the agent and generates the necessary host output artifacts.

```bash
eve build
```

--------------------------------

### eve build

Source: https://eve.dev/docs/reference/cli

Compiles and bundles the project into an invocation-owned directory and publishes the output.

```APIDOC
## eve build

### Description
Compiles and bundles in an invocation-owned directory under .eve/builds/, then publishes the completed host output and prints its path. Scratch workspaces are removed after success or failure.

### Usage
`eve build`
```

--------------------------------

### Create a packaged markdown skill

Source: https://eve.dev/docs/skills

A skill directory containing a SKILL.md file with required description frontmatter.

```md
---
description: Research unfamiliar topics before answering with confidence.
---

When the task is novel or ambiguous, gather evidence first, then answer with the
key facts and the remaining uncertainty.
```

--------------------------------

### Configure deployment and host settings

Source: https://eve.dev/docs/guides/frontend/sveltekit

Customize build commands for Vercel or specify a host for non-Vercel deployments.

```ts
export default defineConfig({
  plugins: [
    eveSvelteKit({
      eveBuildCommand: "npm run build:eve",
    }),
    sveltekit(),
  ],
});
```

```ts
const agent = useEveAgent({
  host: "https://agent.example.com",
});
```

--------------------------------

### Create a new session

Source: https://eve.dev/docs/guides/deployment

Initiate a session by sending a POST request to the session endpoint.

```bash
curl -X POST https://<your-app>/eve/v1/session \
  -H 'content-type: application/json' \
  -d '{"message":"Hello from production"}'
```

--------------------------------

### Define base identity with instructions.md

Source: https://eve.dev/docs/concepts/context-control

Use this file for stable, core agent behavior that applies to every turn.

```md
You are a careful support assistant. Be concise, verify facts before replying, and explain when you
used a tool.
```

--------------------------------

### GET /eve/v1/session/<sessionId>/stream

Source: https://eve.dev/docs/concepts/sessions-runs-and-streaming

Retrieves a durable stream of events for a specific session. Use the startIndex parameter to resume from a specific event count or rewind the stream.

```APIDOC
## GET /eve/v1/session/<sessionId>/stream

### Description
Streams events for a given session. The stream is durable and replayable.

### Method
GET

### Endpoint
/eve/v1/session/<sessionId>/stream

### Parameters
#### Path Parameters
- **sessionId** (string) - Required - The unique identifier for the session.

#### Query Parameters
- **startIndex** (integer) - Optional - The event count index to start streaming from.
```

--------------------------------

### Override a built-in tool

Source: https://eve.dev/docs/concepts/default-harness

Replace a default tool by creating a new definition with the same slug. This example wraps the default 'write_file' tool to add custom logging before execution.

```ts
import { defineTool } from "eve/tools";
import { writeFile } from "eve/tools/defaults";

export default defineTool({
  ...writeFile, // keep the default description, schema, and executor
  async execute(input, ctx) {
    console.log("[write_file]", input.path);
    return writeFile.execute(input, ctx);
  },
});
```

--------------------------------

### Initiate a cross-channel session

Source: https://eve.dev/docs/channels/custom

Use args.receive to start a session on a target channel from a route handler. The target channel's receive hook manages the session state and continuation tokens.

```ts
import { defineChannel, POST } from "eve/channels";
import slack from "./slack";

export default defineChannel({
  routes: [
    POST("/incident", async (req, args) => {
      const incident = await req.json();

      args.waitUntil(
        args.receive(slack, {
          message: `Investigate ${incident.reference}: ${incident.title}`,
          target: { channelId: "C0123ABC" },
          auth: {
            authenticator: "incidentio",
            principalType: "service",
            principalId: incident.actor.id,
            attributes: { reference: incident.reference, severity: incident.severity },
          },
        }),
      );

      return new Response("ok");
    }),
  ],
});
```

--------------------------------

### Implement a custom approval policy

Source: https://eve.dev/docs/human-in-the-loop

Define a custom function to evaluate approval based on session context and tool input. This example denies cross-tenant calls and requires approval for amounts exceeding 1000.

```typescript
approval: ({ session, toolInput }) => {
  const callerTenant = session.auth.current?.attributes.tenantId;
  if (callerTenant === undefined || callerTenant !== toolInput?.tenantId) {
    return { type: "denied", reason: "Caller cannot access this tenant." };
  }
  return (toolInput?.amount ?? 0) > 1000 ? "user-approval" : "not-applicable";
},
```

--------------------------------

### Chart Series Tool

Source: https://eve.dev/docs/tutorial/run-analysis

A tool to plot a time series to a PNG in the workspace. It takes points with date and value, writes them to a JSON file, and then uses a Python script to generate the chart. Ensure Python and matplotlib are installed in the sandbox environment.

```typescript
import { defineTool } from "eve/tools";
import { z } from "zod";

export default defineTool({
  description:
    "Plot a time series to a PNG in the workspace. Pass {date, value} points; " +
    "returns the chart path.",
  inputSchema: z.object({
    title: z.string(),
    points: z.array(z.object({ date: z.string(), value: z.number() })),
  }),
  async execute({ title, points }, ctx) {
    const sandbox = await ctx.getSandbox();
    await sandbox.writeTextFile({
      path: "analysis/series.json",
      content: JSON.stringify({ title, points }),
    });
    await sandbox.writeTextFile({
      path: "analysis/plot.py",
      content:
        "import json, matplotlib\n"
        "matplotlib.use('Agg')\n"
        "import matplotlib.pyplot as plt\n"
        "d = json.load(open('series.json'))\n"
        "plt.plot([p['date'] for p in d['points']], [p['value'] for p in d['points']])\n"
        "plt.title(d['title']); plt.savefig('chart.png')";
    });
    const root = sandbox.resolvePath("analysis");
    await sandbox.run({ command: `cd ${JSON.stringify(root)} && python plot.py` });
    return { chart: `${root}/chart.png` };
  },
});
```

--------------------------------

### Create a custom tool

Source: https://eve.dev/docs/getting-started

Define a new tool by creating a file in the agent/tools directory; the filename determines the tool name.

```ts
import { defineTool } from "eve/tools";
import { z } from "zod";

// The model sees this tool as `get_weather`, from the filename.
export default defineTool({
  description: "Get the current weather for a city.",
  inputSchema: z.object({ city: z.string().min(1) }),
  async execute({ city }) {
    return { city, condition: "Sunny", temperatureF: 72 };
  },
});
```

--------------------------------

### Project structure for dynamic scheduling

Source: https://eve.dev/docs/patterns/dynamic-scheduling

Recommended file organization for managing dynamic schedules, storage adapters, and CRUD tools.

```text
agent/
  channels/slack.ts
  lib/schedule-store.ts     # your storage adapter
  lib/tenant.ts
  schedules/dynamic.ts
  tools/create_schedule.ts
  tools/delete_schedule.ts
  tools/list_schedules.ts
  tools/update_schedule.ts
```

--------------------------------

### eve extension build

Source: https://eve.dev/docs/reference/cli

Builds the current package as an extension.

```APIDOC
## eve extension build

### Description
Builds the current package as an extension by compiling the mount factory and tool re-exports into the dist/ directory and updating the package exports map. Requires a valid package.json with an eve.extension configuration.

### Usage
`eve extension build`
```

--------------------------------

### Mounting an extension

Source: https://eve.dev/docs/extensions

Mount a standard extension by exporting the factory call from a file in the agent/extensions/ directory.

```ts
import crm from "@acme/crm";

export default crm({ apiKey: process.env.CRM_API_KEY });
```

```ts
export { default } from "@acme/gizmo";
```
Tokens:
Raw