Add Eve addon guide#756
Open
broomva wants to merge 1 commit into
Open
Conversation
Contributor
|
@broomva is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
6 tasks
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
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.
Description
Adds
docs/content/docs/addons/eve.mdx— an addon guide for integrating Eve (Vercel's open-source durable-agent framework) as a workspace app in a next-forge monorepo, following the existing addon shape (c15t, Trunk).The guide covers: scaffolding
apps/agentwitheve init(including the workspace-root changes it makes), a tool that reuses@repo/database's generated Prisma client and validated env keys with graceful degradation whenDATABASE_URLis absent, running and exercising the HTTP channel, evals, client wiring viaeve/react, and deploying as a separate Vercel project.Related Issues
Closes #754
Checklist
<Tip>/<Steps>, imperative voice, structure mirrored from sibling addon pages)Additional Notes
Every command and caveat in the guide was verified on a fresh
next-forge@6.0.2scaffold witheve@0.20.0(scaffold initialized with the pnpm option; command forms in the guide follow this repo's Bun convention):npx eve@latest init .insideapps/agentengines.noderewritten>=18→24.x; pnpm hygiene block appendedeve devboot +GET /eve/v1/health{"ok":true,"status":"ready"}actions.requested→action.result→ assistant reply; replayable@repo/databaseroot entryserver-onlyguard crashes Eve's Nitro runtime → guide documents thegenerated/client+keyssubpath importsimport()inside a toolDATABASE_URLdisabled: true; agent explains which env var enables iteve buildtsc --noEmitwithmoduleResolution: bundlereve eval --strict(the guide's smoke eval)The page was additionally put through two rounds of adversarial review against the eve 0.20.0 source and this repo's conventions (initial findings included pnpm-flavored commands, a snippet that would clobber
eve init's deps, a missingprisma generateprecondition, andeve init's patch-wins semantics silently un-pinning the exact version — all fixed in the current revision).Eve is in beta; the guide pins
eve@0.20.0(scaffolder and dependency) and flags the churn explicitly.