Problems solved
- Run an agent on a cron cadence
- Deliver proactive messages without an inbound request
- Let tenant users create and manage schedules safely
- Verify schedule dispatch deterministically without credentials
Use cases
- Scheduled product or operations digests
- Proactive agent notifications
- Tenant-owned recurring reminders
- Testing cron and dynamic schedule dispatch
Setup
Requirements, wiring steps, and what this pattern adds to your project.
Requirements
- Complexity
- Intermediate
- Setup time
- ~10 minutes
- Node
- 24+
- Memory
- 256MB
Getting started
Pick how you want to pull this pattern in — then wire env vars and routes the same way.
- 1
Install into an empty project directory

Copy the tokenized install command from the preview toolbar and run it in an empty directory so the Eve package and agent tree stay together.
- 2
Install dependencies and run the verification suite
With Node.js 24+, run `pnpm install`, `pnpm verify:discovery`, `pnpm typecheck`, `pnpm build`, and `pnpm eval`.
- 3
Run the Eve development server
Run `pnpm dev` after every verification gate passes.
Files added
26 files.gitignore.node-versionagent/agent.tsagent/channels/eve.tsagent/channels/notify.tsagent/instructions.mdagent/lib/digest-log.tsagent/lib/schedule-store.tsagent/lib/tenant.tsagent/schedules/daily-digest.tsagent/schedules/dispatch.tsagent/tools/create_schedule.tsagent/tools/delete_schedule.tsagent/tools/get_metrics.tsagent/tools/list_schedules.tsagent/tools/record_digest.tsagent/tools/update_schedule.tsevals/cross-tenant.eval.tsevals/daily-digest.eval.tsevals/dispatch-due-schedule.eval.tsevals/dynamic-schedule-crud.eval.tsevals/evals.config.tsevals/helpers.tspackage.jsonREADME.mdtsconfig.json
Dependencies
3 totalnpm packages
3









