Web Chat

The eve CLI scaffolds the full Next.js web chat app alongside agent/channels/eve.ts:

eve add channel/web

To wire it up by hand instead — including into a Svelte or Nuxt app you already have — install the framework:

npm install eve@latest

The eve channel is on by default. Add agent/channels/eve.ts only when you want to override the default session routes or auth:

// agent/channels/eve.tsimport { eveChannel } from "eve/channels/eve";
export default eveChannel();

Point your frontend at the session routes eve serves (/eve/v1/session) and stream responses with the eve web client. Next.js, Nuxt, and Svelte each have an integration that mounts those routes on your app's own origin, so there's no CORS to configure and no URL env var to keep in sync:

• Next.js. Wrap next.config.ts with withEve() from eve/next, then call useEveAgent() from eve/react. See the Next.js guide.
• Nuxt. Add "eve/nuxt" to modules in nuxt.config.ts; the useEveAgent() composable from eve/vue is auto-imported. See the Nuxt guide.
• Svelte. Add the eveSvelteKit() Vite plugin before sveltekit() in vite.config.ts, then call useEveAgent() from eve/svelte. See the SvelteKit guide.

On any other stack, wire it up by hand: run the agent as its own service and proxy /eve/v1/** to it, or pass its origin as host to useEveAgent() and enable cors on the channel. Server-side code and custom UIs can call the routes through Client from eve/client.

The eve channel is the lowest-friction way to talk to your agent, with no third-party provisioning required. Layer in auth and route protection as needed, and enable cors only when a browser reaches the channel from another origin. See the eve channel docs, the Frontend guide, and the per-framework guides for Next.js, Nuxt, and SvelteKit.