Guidance for coding agents (and humans) working in this repository. For setup, PR workflow, and release process, see CONTRIBUTING.md. eve is a filesystem-first framework for durable backend AI agents. You author an agent as a directory on disk — instructions, skills, tools, connections, channels, subagents, and schedules are all files — and eve compiles and runs it. See the README for the full overview and docs/ for user-facing documentation. Always style the framework name as eve, lowercase, in user-facing copy,…
All user-facing UI changes must be mobile-responsive. Before completing a UI change, verify it at a narrow mobile viewport and a desktop viewport. Check for page-level horizontal overflow, clipped content, unreadably narrow columns, overlapping controls, and whether dense navigation should wrap or scroll horizontally. This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ (resolved from this file's directory; in monorepos the next package may not…
This project uses the eve framework. Before writing code, always read the relevant guide in node_modules/eve/dist/docs/public/. Use eve lowercase in user-facing copy, docs, prompts, and comments. Do not title-case it unless it is part of an exact external title or quoted text.
This project uses the eve framework. Before writing code, read the relevant guide from the installed eve package docs. In most installs, those docs are at node_modules/eve/docs/. In workspaces or local package installs, resolve the installed eve package location first and read its docs/ directory. If package docs are unavailable, use https://eve.dev/docs as a fallback. Before implementing an integration yourself, use eve registry search <query> or eve registry list to discover available integrations. Inspect one with eve registry view <item>,…
Durable personal AI assistant built with Eve and Nuxt. This project deploys its Nuxt frontend and eve agent as peer Vercel services through vercel.ts. Before writing agent code, read the relevant guide in node_modules/eve/dist/docs/public/. The Eve agent calls Nuxt over HTTP: Authenticated with Authorization: Bearer <INTERNALAPISECRET>. See apps/web/server/utils/internal-api.ts. Categories: lib/types/memory.ts. One prose block per category; saves replace the full block. See docs/CUSTOMIZATION.md for details.
This private package is the source of the eve/extensions/code extension for CLI-based coding work. It contributes one patch editing primitive, computer use, an authenticated gh tool, sandbox grep, shared PR-watch primitives, investigation and PR skills, instruction fragments, a read-only worker subagent, Connect-backed authentication hooks, and consumer sandbox helpers. Durable prwatch / prwatch_delete wrappers currently live beside e0's consumer mount because eve workflow directives are application-only. Before writing code, read the installed eve package docs for extensions, hooks, tools, skills, subagents,…
These defaults are optimized for AI coding agents (and humans) working on apps that deploy to Vercel. - Treat Vercel Functions as stateless + ephemeral (no durable RAM/FS, no background daemons), use Blob or marketplace integrations for preserving state - Edge Functions (standalone) are deprecated; prefer Vercel Functions - Don't start new projects on Vercel KV/Postgres (both discontinued); use Marketplace Redis/Postgres instead - Store secrets in Vercel Env Variables; not in git or NEXTPUBLIC* - Provision Marketplace native integrations with…
CRITICAL RULES: - NEVER push directly to the main or stable branches - Do not remove or break agent-discoverable docs sitemap behavior: keep docs/app/sitemap.md/route.ts and docs/app/[lang]/sitemap.md/route.ts, and keep the sitemap link in docs/app/[lang]/llms.mdx/[[...slug]]/route.ts. Workflow SDK is a durable functions framework for JavaScript/TypeScript that enables writing long-running, stateful application logic on top of stateless compute. The runtime persists progress as an event log and deterministically replays code to reconstruct state after cold starts, failures, or scale events. This repository contains the…
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ (resolved from this file's directory; in monorepos the next package may not be visible from the repo root) before writing any code. Heed deprecation notices. This block is written and re-added by next dev — verify at node_modules/next/dist/server/lib/generate-agent-files.js. Removing it from a diff only re-creates the uncommitted change; committing it with your work keeps the tree…
Guidance for coding agents working in this repository. For PR workflow, signed commits, and changeset rules, see .github/CONTRIBUTING.md. Install dependencies with pnpm add, not by editing package.json by hand. pnpm + Turborepo monorepo. Packages are ESM ("type": "module"), TypeScript, bundled with tsup. When editing a specific package, read its AGENTS.md if present (most adapters, state packages, create-chat-sdk, and packages/chat/src/adapters/ have one). {adapter}:{channel}:{thread} — e.g. slack:C123ABC:1234567890.123456. Some adapters base64-encode IDs that contain delimiters (Teams, Google Chat). mdast is the canonical message…
This app (chat-sdk.dev) uses the packaged Geistdocs architecture. The @vercel/geistdocs package owns shared runtime behavior; this app owns local content, configuration, adapters, and site-specific routes. Use these instructions when an AI coding agent edits this app.
Build multi-platform chat bots with Chat SDK (`chat` npm package). Use when developers want to scaffold a bot with create-chat-sdk, build a Slack, Teams, Google Chat, Discord, Telegram, GitHub, Linear, or WhatsApp bot, handle mentions, direct messages, subscribed threads, reactions, slash commands, cards, modals, files, or AI streaming, set up webhook routes or multi-adapter bots, send rich cards or streamed AI responses to chat platforms, or build a custom adapter or state adapter.
Guidance for coding agents working inside the Discord adapter package. The top-level repository AGENTS.md covers monorepo-wide build, lint, and release rules — read it first. This file documents the adapter-specific surface, conventions, and pitfalls. @chat-adapter/discord connects a Chat SDK bot to a Discord guild via HTTP interactions and the Discord Gateway. It covers: - HTTP webhook endpoint at /api/webhooks/discord for slash commands, message components (buttons / selects), and modal submissions. - Gateway transport (websocket) that listens for MESSAGECREATE, MESSAGEUPDATE, MESSAGEDELETE,…
Guidance for coding agents working inside the Google Chat adapter package. The top-level repository AGENTS.md covers monorepo-wide build, lint, and release rules — read it first. This file documents the adapter-specific surface, conventions, and pitfalls. @chat-adapter/gchat connects a Chat SDK bot to Google Chat (the Workspace messaging product, not Hangouts/Meet). It covers: - HTTP webhook endpoint at /api/webhooks/gchat, validated with Google-issued JWTs. - Card v2 rendering for cards, fields, action buttons, image attachments, and dialog modals. - Workspace Events API…
Guidance for coding agents working inside the GitHub adapter package. The top-level repository AGENTS.md covers monorepo-wide build, lint, and release rules — read it first. This file documents the adapter-specific surface, conventions, and pitfalls. @chat-adapter/github connects a Chat SDK bot to issue and pull-request comment threads on GitHub. It covers: - HTTP webhook endpoint at /api/webhooks/github for issues, issuecomment, pullrequest, pullrequestreviewcomment, and pullrequest_review events, validated with HMAC-SHA256 against the App secret. - Comment posting, editing, and deletion via the REST…
Follow the repository-level AGENTS.md plus these package-specific rules. This package integrates Instagram Direct Messages through the native Instagram API with Instagram Login (graph.instagram.com). Do not switch outbound calls to the Facebook Graph host or use Page access tokens. - Factory: createInstagramAdapter - Adapter name: instagram - Thread ID: instagram:{professionalAccountId}:{igsid} - Webhook object: instagram - Required permissions: instagrambusinessbasic and instagrambusinessmanagemessages - Required env vars: INSTAGRAMACCESSTOKEN, INSTAGRAMAPPSECRET, INSTAGRAMVERIFYTOKEN, INSTAGRAMACCOUNT_ID - A customer must initiate the conversation. - Standard sends are limited to…
Guidance for coding agents working inside the Linear adapter package. The top-level repository AGENTS.md covers monorepo-wide build, lint, and release rules — read it first. This file documents the adapter-specific surface, conventions, and pitfalls. @chat-adapter/linear connects a Chat SDK bot to issue and project comment threads inside Linear. It covers: - HTTP webhook endpoint at /api/webhooks/linear for Issue.create / update / remove, Comment.create / update / remove, IssueLabel, and Reaction events, validated via the Linear webhook signing secret. - Comment…
Guidance for coding agents working inside the Messenger adapter package. The top-level repository AGENTS.md covers monorepo-wide build, lint, and release rules — read it first. This file documents the adapter-specific surface, conventions, and pitfalls. @chat-adapter/messenger connects a Chat SDK bot to Facebook Messenger via the Meta Messenger Platform. It covers: - HTTP webhook endpoint at /api/webhooks/messenger with the GET challenge handshake plus signed POST event delivery (HMAC-SHA256 via appSecret). - Outbound messages via the Send API: text, attachments, templates (button…
Guidance for coding agents working inside the Notion adapter package. The top-level repository AGENTS.md covers monorepo-wide build, lint, and release rules — read it first. @chat-adapter/notion connects a Chat SDK bot to Notion comments (page-level and discussion threads) via: - Webhooks (comment.created) with X-Notion-Signature HMAC verification and a one-time verificationtoken handshake - Comments REST API (create / update / delete / list / retrieve) - Outbound Vercel Connect authentication via an async token resolver; inbound webhooks remain direct and use…
VercelAGENTS.md