fix(evi): migrate to eve 0.31 session APIs - #553
Merged
Merged
Conversation
eve 0.31.0 replaced continuation-token sessions with fixed, ID-addressed
handles and changed the proactive-delivery surface: schedule handlers now
use to(channel, target).send(message, { auth }), custom-channel routes use
from(address).send(...), and eval delivery takes positional send(message,
options). Migrate the digest and upstream-sync schedules, the MCP channel,
and the first-responder eval to the new shapes, and re-pin the eve runtime
patch (0.31.3): keep the !reset escape hatch, ported to the new
from().clear() API, and drop the dynamic-tool step-registry hunk since
0.31 ships its own registry and the app inlines dynamic tool executes.
Checks: lint, typecheck, and test all pass; eve build succeeds.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Contributor
|
Thank you for following the naming conventions! 🙏 |
commit: |
HugoRCD
approved these changes
Aug 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
Upstream sync: eve released 0.31.0 with a breaking session-API migration (continuation tokens replaced by fixed, ID-addressed handles), followed by patch releases up to 0.31.3. The other tracked packages are current:
@agent-browser/eve0.33.2,@github-tools/eve-extension0.3.2,@vercel/connect0.6.1.This PR bumps
eveto^0.31.3and adapts the app to the new surfaces:digest.ts,upstream-sync.ts):receive(photon, { message, target, auth })is gone; schedule handlers now useto(channel, target).send(message, { auth }).channels/mcp.ts): the route-levelsend(message, { continuationToken })is replaced byfrom(address).send(message, { auth }); the mcp-session-id now keys the continuation address, so one Raycast chat still maps to one Evi conversation.evals/safety/first-responder.eval.ts):t.send(message, options)is now positional.Runtime patch
The pnpm patch is regenerated against 0.31.3 (
patches/eve@0.31.3.patch):!resetescape hatch on the iMessage channel, ported from the removedcontinuationToken-basedclearto the newfrom(threadId).clear()API.__eveStepRegistrymechanism, and since fix(evi): inline dynamic tool executes so resumed sessions keep their tools #551 the app inlines all dynamic tool executes in resolvers, which is what actually prevents the "step function not registered" failures on resumed sessions. Worth a sanity check on a resumed iMessage session after deploy, since I cannot exercise the resume path here.Checks
pnpm run lint: 22/22 tasks passpnpm run typecheck: cleanpnpm run test: 22/22 tasks pass (evlog 1788 tests, evi 63 tests)pnpm --filter evi run build: eve build succeedsNo changeset: the change is confined to
apps/evi.