eve Vercel Drives Starter

eve Vercel Drives Starter is a starter template for an eve agent that reads and saves team files stored on a Vercel Drive, with each session getting a read-only snapshot the agent can search with shell commands. It runs on Vercel and is maintained in the vercel-labs GitHub organization under the MIT License.

What is eve Vercel Drives Starter?

The template is a starter for an eve agent that reads and saves your team's files on a Vercel Drive. Each conversation session receives a read-only snapshot of the Drive mounted at /drive in a Vercel Sandbox, and the agent can write new notes and documents back to the Drive. It runs on the Vercel platform and is published by vercel-labs under the MIT License.

Key Features

• eve agent framework — the agent's behavior is defined in agent/instructions.md, and model and session limits are configured in agent/agent.ts.
• Vercel Drives file storage — the Drive is mounted into each session; the Drive name and region are controlled by the DRIVE_NAME and DRIVE_REGION environment variables.
• Vercel Sandbox workspace — sessions mount the read-only Drive snapshot at /drive and explore it with shell commands such as ls, find, and grep, reading files with read_file.
• Slack integration via Vercel Connect — chat with the agent in a Slack thread, or locally with pnpm dev; the Slack app is created and installed through Vercel Connect with no manual environment variables.
• save_to_drive tool — runs in the app rather than the sandbox, starting a short-lived read-write sandbox to write the file and then stopping; if another write holds the mount it reports drive_busy and the agent offers to retry.
• Upload script — pnpm drive:upload copies a local folder into the Drive (overwriting files at the same paths), with --prefix to target a subfolder.
• Network isolation — the sandbox has no network access and the template turns off eve's web_fetch and web_search tools so file contents can't be sent to outside URLs.
• Drive helpers and mount code — located in agent/lib/drive.ts and agent/sandbox.ts.

Who is it for?

• Teams keeping documents in Vercel Drives: search and summarize team files and save notes back during a Slack thread.
• Slack-first teams: @mention the agent in a channel and ask questions like "What's in my Drive?" or "Summarize the onboarding checklist".
• Developers building on eve: use the template as a starting point, then customize approval before saving, add a delete tool, or schedule file syncs.

What can you do with eve Vercel Drives Starter?

• Slack users: @mention the agent in a channel to search Drive files and save new notes such as "Save a summary of this thread to notes/standup.md".
• Local developers: run pnpm dev for an interactive terminal chat that reads and saves on the same Drive as the deployed agent.
• Teams onboarding files: run pnpm drive:upload content (or a custom folder with --prefix) to populate the Drive, since sessions can't mount a Drive that has never been written to.

How does eve Vercel Drives Starter work?

A session is one Slack thread or one local chat. On first sandbox use, the sandbox mounts a read-only Drive snapshot at /drive; saving runs a short-lived read-write sandbox in the app instead. Because a snapshot reflects the Drive when mounted, a saved file appears in new sessions and might not appear in the session that saved it.

FAQ

Is eve Vercel Drives Starter free?

Yes. The repository is released under the MIT License. Running it requires a Vercel account; the setup flow creates a Git repository and a Vercel project, and Slack is connected through Vercel Connect.

Why is /drive missing in my session?

Sessions can't mount a Drive that has never been written to. Run the upload script or let the agent save a file once to create the Drive; until then /drive is unavailable.

What Node.js version does local development need?

Local development uses Node.js 24 with pnpm, plus the Vercel CLI. Run vercel link, then vercel env pull .env.local; the downloaded token expires after 12 hours, so rerun it on OIDC credential errors.

Why did a save fail with drive_busy?

Only one sandbox can mount a Drive read-write at a time. If another save or upload holds the mount, the save_to_drive tool reports drive_busy and the agent offers to retry.