eve 0.9.4 → 0.9.8

package/docs/getting-started.mdx

@@ -24,9 +24,9 @@ You also need a model credential. Set the provider or gateway key your model str
 
 ## Manual installation
 
-The quick start uses `eve init` for a guided scaffold. The target can also be an existing project directory (`eve init .`): the project must have a `package.json`, the `agent/` files must not exist yet, and `eve init` adds the missing `eve`, `ai`, and `zod` dependencies. The generated Eve dependency and Node engine come from the same Eve release; the engine is the lowest complete major supported by that release (e.g. `24.x`). An existing range is kept only when every version it permits stays within that major; otherwise Eve replaces it with the pinned major and prints a warning. Either way the final handoff runs the `eve dev` binary through the project's package manager, never the project's own `dev` script.
+The quick start uses `eve init` for a guided scaffold. Run `npx eve@latest init <name>` from a parent directory, or create an empty directory first and run `eve init`, `eve init .`, or `eve init ./` inside it to run the same full scaffold there, including `package.json`. To add Eve to a non-empty existing app, use `npx eve@latest init .`: that add-agent flow requires a `package.json` and no existing `agent/` files yet, and Eve adds the missing `eve`, `ai`, and `zod` dependencies for you. Eve also ensures a compatible Node engine (for example `24.x`) is present; if an existing range is too narrow for the release, Eve updates it and warns you. Either way the final handoff runs the `eve dev` binary through the package manager, not the project’s own `dev` script.
 
-To wire Eve into an existing app yourself instead, make sure the app declares a compatible Node runtime in `package.json`:
+To wire Eve in by hand, declare a compatible Node runtime in `package.json`:
 
 ```json
 {
@@ -36,7 +36,7 @@ To wire Eve into an existing app yourself instead, make sure the app declares a
 }
 ```
 
-Then add only the dependency and author the two files the runtime needs:
+Then install Eve and author the two files the runtime needs:
 
 ```bash
 npm install eve@latest
@@ -109,7 +109,7 @@ The same CLI can point at a deployment. `eve dev https://your-app.vercel.app` dr
 Every Eve app exposes the same stable HTTP API. Start a durable session:
 
 ```bash
-curl -X POST http://127.0.0.1:3000/eve/v1/session \
+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?"}'
 ```
@@ -124,39 +124,17 @@ The response comes back with two things you'll reuse:
 Attach to the session stream:
 
 ```bash
-curl http://127.0.0.1:3000/eve/v1/session/<sessionId>/stream
+curl http://127.0.0.1:2000/eve/v1/session/<sessionId>/stream
 ```
 
-The stream is NDJSON. Expect lifecycle events such as:
-
-- `session.started`
-- `turn.started`
-- `message.received`
-- `step.started`
-- `actions.requested`
-- `action.result`
-- `subagent.called`
-- `subagent.completed`
-- `reasoning.appended`
-- `reasoning.completed`
-- `message.appended`
-- `message.completed`
-- `step.completed`
-- `turn.completed`
-- `session.waiting`
-- `session.completed`
-- `session.failed`
-
-`reasoning.appended` and `message.appended` are optional live-streaming events. Clients that can't surface incremental output can ignore them and rely on `reasoning.completed` and `message.completed`.
-
-`message.completed.data.finishReason` tells you whether assistant text is interim tool-call narration or a terminal reply, and `step.completed.data.usage` carries token usage. When a parent delegates to a subagent, `subagent.called.data.childSessionId` gives you the child session id, so you can subscribe to that child stream and watch the delegated work.
+The stream is NDJSON, one lifecycle event per line. See [Sessions, runs & streaming](./concepts/sessions-runs-and-streaming) for the full list of events and what each one carries.
 
 ## Send a follow-up message
 
 When the session is waiting for the next user message, post a follow-up with the token:
 
 ```bash
-curl -X POST http://127.0.0.1:3000/eve/v1/session/<sessionId> \
+curl -X POST http://127.0.0.1:2000/eve/v1/session/<sessionId> \
   -H 'content-type: application/json' \
   -d '{"continuationToken":"<token>","message":"Now do Queens."}'
 ```
@@ -168,18 +146,13 @@ See [Sessions, runs & streaming](./concepts/sessions-runs-and-streaming) for the
 If a coding agent (Claude Code, Cursor, and the like) is doing the setup, hand it this prompt:
 
 <CopyPrompt text="Set up an Eve agent for the user. Ask one question at a time. Use your prompt tools when available and do not guess. First ask what the agent should do. Then ask whether to create a new project or add it to an existing directory. For a new project, propose a name and ask the user to confirm it, then ask whether it should include Web Chat. Run `npx eve@latest init <target>`, adding `--channel-web-nextjs` if the user wants Web Chat. After scaffolding, read the relevant guide in `<project>/node_modules/eve/docs/`, replace the placeholder in `<project>/agent/instructions.md` with the purpose the user gave you, and do not start `eve dev` because it is interactive. Give the user the exact dev command printed by init.">
-  Set up an Eve agent by asking what it should do, whether to create a new project or use an
-  existing directory, and whether a new project should include Web Chat, one question at a time.
+  Set up an Eve agent by asking what it should do, whether to create a new project, scaffold the
+  current empty directory, or add Eve to an existing app, and whether a new project should include Web Chat, one question at a time.
   Run `npx eve@latest init <target>`, read the bundled docs, fill in agent/instructions.md, and give
   the user the dev command instead of starting the interactive server.
 </CopyPrompt>
 
-Once `eve` is a dependency, the full docs are bundled in the package, so the agent can read them locally without fetching anything:
-
-- Docs: `node_modules/eve/docs/`
-
-`eve init <name>` creates the base agent; `eve init .` adds one to an existing project. Add `--channel-web-nextjs` for Web Chat, or run
-`eve channels add slack` later from an interactive terminal.
+Once `eve` is installed, the complete docs ship at `node_modules/eve/docs/`, so the agent can read them locally instead of fetching anything.
 
 ## What to read next
 

package/docs/guides/client/messages.mdx

@@ -12,7 +12,7 @@ Pass a string to `send()` for plain text:
 ```ts
 import { Client } from "eve/client";
 
-const client = new Client({ host: "http://127.0.0.1:3000" });
+const client = new Client({ host: "http://127.0.0.1:2000" });
 const session = client.session();
 
 const response = await session.send("What is the weather in Brooklyn?");

package/docs/guides/client/output-schema.mdx

@@ -26,7 +26,7 @@ const outputSchema = {
   required: ["title", "count"],
 } as const;
 
-const client = new Client({ host: "http://127.0.0.1:3000" });
+const client = new Client({ host: "http://127.0.0.1:2000" });
 const session = client.session();
 
 const response = await session.send<Summary>({

package/docs/guides/client/overview.mdx

@@ -15,7 +15,7 @@ A `Client` binds one host, auth policy, header policy, and stream reconnection b
 import { Client } from "eve/client";
 
 const client = new Client({
-  host: "http://127.0.0.1:3000",
+  host: "http://127.0.0.1:2000",
 });
 ```
 

package/docs/reference/cli.md

@@ -77,7 +77,7 @@ Pass a bare URL as the only argument and the UI connects to that server instead
 | Flag                                | Effect                                                                                    |
 | ----------------------------------- | ----------------------------------------------------------------------------------------- |
 | `--host <host>`                     | Host interface to bind                                                                    |
-| `--port <port>`                     | Port to listen on (defaults to `$PORT`, then `3000`)                                      |
+| `--port <port>`                     | Port to listen on (defaults to `$PORT`, then `2000`)                                      |
 | `-u, --url <url>`                   | Connect to an existing server URL instead of starting one                                 |
 | `--no-ui`                           | Start the server without an interactive UI                                                |
 | `--name <name>`                     | Title shown in the terminal UI (defaults to the app folder name)                          |

package/docs/schedules.mdx

@@ -86,7 +86,7 @@ A handler-form session runs on the same durable runtime engine as any other sess
 In production the cron cadence is the only thing that fires a schedule, but waiting for the next tick gets old fast while iterating in `eve dev`. So the dev server mounts a one-shot dispatch route: fire a schedule by name, out of band, exactly once.
 
 ```sh
-curl -X POST http://localhost:3000/eve/v1/dev/schedules/heartbeat
+curl -X POST http://localhost:2000/eve/v1/dev/schedules/heartbeat
 # -> { "scheduleId": "heartbeat", "sessionIds": ["..."] }
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eve",
-  "version": "0.9.4",
+  "version": "0.9.8",
   "private": false,
   "description": "Filesystem-first framework for durable backend AI agents that run anywhere.",
   "keywords": [