Roadmap

Jev Events is young, and its API may still change before 1.0.

AvailableCopy Anchor Link

• Core: monitor() and runtime(), typed events, policies and review bands, dry-run, protected users, budgets, rate limits, stale dropping, the text cache, burst(), logTo() and mockJev().
• For your users: one monitor runs for every account your users connect, with sign-in, cron and webhook routes for your web app, a worker for chat streams, and tokens encrypted in your Postgres database. See For your users.
• Sources: from(), webhook(), and the read-only public Twitch chat and Bluesky firehose.
• Gmail and Google Calendar: new mail with trash, archive, label, star, mark read and draft reply; new and changed events with accept, decline and maybe. Colleagues are protected by default, and nothing is ever deleted or sent. You use your own Google Cloud project, so your mail never passes through anyone else's servers.
• Slack: messages in the channels and DMs your app is in, over Socket Mode on your machine or the Events API in a web app, with reply, react and post.
• Twitch: chat in your own channel or your users', read as the signed-in account, and any public chat with no sign-in. Actions: timeout, ban, deleteMessage, warn, reply, say and clip.
• CLI: watch for every source, auth google, auth slack and auth twitch, and key.
• Docs: a builder on each integration's page that writes the code for what you pick, and a prompt for your coding agent.
• Benchmarks: a labeled chat dataset and an open runner.

In developmentCopy Anchor Link

Outlook mail, Outlook Calendar, Microsoft Teams, Discord, GitHub, Linear, Notion, Google Drive and YouTube. Each ships with its own guide and builder, and moves up to Available when it's done.

PlannedCopy Anchor Link

Push for Gmail and Google Calendar: Google tells your app about new mail and events as they happen, instead of your app checking every few minutes.

Suggest oneCopy Anchor Link

Missing a platform? Open an issue with what you'd monitor and which actions you need.