EveStudioDocs

Keep eve current

Every agent pins its own eve version in package.json. Studio compares that against the latest release on npm and, when there's something newer, shows an ↑ <latest> available chip in the agent header. Clicking it upgrades that agent in place, without a terminal.

What the chip shows

The header's mono metadata line reads eve <version> for the version installed in the agent. When npm has a newer release, an ↑ 0.49.0 available chip appears next to it. The chip is per agent: two agents on different eve lines each get their own.

The upgrade modal

Click the chip and Studio opens the Upgrade eve modal, showing the installed and latest versions side by side. It explains what will happen and notes that eve 0.49 needs Node 24 (Studio provisions a Node 24 runtime for the local dev server; production runs on Vercel's Node) and that your source files are not modified. Click Upgrade to <latest> (or Not now). The upgrade then:

  1. Stops the dev server for the agent, so the next Start boots the new version.

  2. Upgrades eve with the agent's own package manager, detected from the lockfile:

    pnpm add eve@latest        # pnpm-lock.yaml
yarn add eve@latest        # yarn.lock
npm install eve@latest     # package-lock.json

    If npm refuses the peer-dependency graph (ERESOLVE), Studio retries the same install with --legacy-peer-deps and says so in the log.

  3. Bumps @kybernesis/arcana to latest in the same install when the agent depends on it, so the memory extension moves with eve.

  4. Runs eve info --json to rebuild the manifest and reports the diagnostics count.

The console streams the whole run. The result line reads Now on eve <version> (and @kybernesis/arcana@latest when it was bumped) with the error and warning counts. With zero errors it tells you to Start the agent to run on the new version; with errors, review the diagnostics first. The structure in every tab refreshes from the new manifest.

Before a big jump

Small upgrades are usually a no-op for your code. Jumping across several minor versions (for example 0.24 or 0.38 → 0.49) can need changes, and eve info will name them as diagnostics after the upgrade. The ones Studio users hit most:

  • Node 24. eve 0.49 requires Node 24 or newer. Studio provisions Node 24 for the local dev server; production runs on Vercel's Node runtime, so make sure the project's Node version setting is 24 too.
  • Schedule handlers. The run form now receives { to, waitUntil, appAuth } and delivers with to(channel, target).send(message, { auth: appAuth }). The older receive(...) shape is gone. See Schedules.
  • Custom channels. Route handlers receive { from, resolveSession, attachSession, to, params, waitUntil, requestIp }; from(address).send(...) starts or continues a session and attachSession(id).getEventStream() streams it. The older { send, getSession, receive } context is gone. See Connections & channels.
  • Built-in tools. Overrides import the default from eve/tools/<name> (for example eve/tools/todo) and spread it into your own defineTool.
  • Channel installs. eve channels add no longer exists; channels come from the registry with eve add channel/<name>.
  • Session API. Follow-up requests no longer carry a continuationToken; a session is addressed by its id and controlled with the cancel, compact, clear, and reset routes.

After the modal reports diagnostics, the header shows a red N build errors chip; click it, fix the file it names, and hit reload so Studio re-runs eve info --json.

Extensions pin to an eve line

Extension packages (@eve/self-modification, @kybernesis/arcana, @kybernesis/*) declare the eve versions they support. Upgrade eve first, then the extensions. Installing an extension built for 0.49 into an older agent produces a discovery error rather than a working mount, which is why Studio replaces the self-modification card's Enable button with a needs eve 0.49.0+ note on older agents.

From a terminal

The same thing by hand, in the agent folder:

pnpm add eve@latest          # or yarn add / npm install
eve info                     # expect 0 errors, 0 warnings

Where to go next