Released 2026-11-20 · Compare with 1.2.0
Features
- Custom skills scope resolvers now receive the turn being run and, in a delegated session, its parent, so an app can choose a turn's skill scopes from what it records per turn. (#6727)
- Add
eve/solidwithuseEveAgentfor Solid 2 apps.
The binding has the same options and methods as the React, Vue, and Svelte bindings, and exposes state as Solid accessors such asagent.messages()andagent.status(). RegistereveVite()to mount the agent routes, and addnitro()fromnitro/viteto deploy a server-rendered Solid app to Vercel.solid-js2 is an optional peer dependency. With npm, a Solid 1 project that installs eve adds"overrides": { "eve": { "solid-js": "$solid-js" } }topackage.json, because npm otherwise rejects that peer. (#6621) - Cold starts load the MCP client only when an agent first connects to an MCP server, so apps pay for its protocol schemas only when they use MCP. (#6709)
Bug Fixes
- A message sent to a pre-1.0 session's original address on a local or self-hosted World now ends that stranded session and starts a fresh one, instead of leaving the session stuck after an upgrade.
Thanks @muratsu for reporting this in #6646. (#6653) - Fix
eve buildfor an app that importseve/extensions/code/sandboxand also mounts@eve/self-improvement.
The self-improvement maintainer mounts its owncodeextension, so the build rejected the app'sinstallCodeToolingimport as belonging to two mounts. An app import now binds to the app's mount and skips mounts nested inside another extension. The coordinator'ssteptool input is now an object with anactionenum instead of a root-level union, which Claude rejects. (#6725)