jev-inbox-queue
Turns an inbox into a short action queue: seven Jev questions per thread decide what needs you, urgency and next step.
Overview
Jev Inbox Queue reads each email thread once and shows only the ones that need you, so you stop re-reading newsletters and receipts. Each thread gets seven questions in one request: whether you still need to act, whether a person is waiting, whether it is promotional or bulk, what kind of message it is (new request, follow-up, acknowledgement, information or promotional), which workflow it belongs to, what the next step is (reply, send document, pay, schedule, review, task or none) and how urgent it is.
Plain Python rules in policy.py turn the answers into To do, Check these and Filtered out lists, for example queuing threads with needs_action of at least 0.6 and filtering those with is_promotional of at least 0.5. Answers are cached so changing a rule needs no new calls. On a 47-email hand-written, hand-labelled demo inbox, the README reports no missed actionable emails, no irrelevant ones shown and 1.4 seconds to sort all 47, while noting the author wrote the emails and labels and adjusted a rule.
What the decision model decides
| Type | Question | Answers |
|---|---|---|
| Yes / no | Do I still need to do something about this thread? | — |
| Yes / no | Is a person waiting on me? | — |
| Choice | What is the next step? | reply · send document · pay · schedule · review · task · none |
| Score | How urgent is it? | — |
How it works
- Load email threads
- Ask Jev seven questions per thread in one request
- policy.py sorts into To do, Check these or Filtered out
- Change rules without new API calls thanks to caching
Strengths
- Seven judgements per thread in one call
- Rules in plain readable Python
- Cached answers
Caveats
- Demo inbox written and labelled by the author
- One rule adjusted after seeing results
At a glance
- Type
- Project
- Status
- prototype
- Language
- Python
- Runtime
- CLI / local app
- Has code
- yes
- License
- MIT
Use cases and integrations
How curated lists describe it
Turn an inbox into a short action queue with Jev (TypeSafe System One)
logicrw/awesome-jev-projects
Frequently asked questions
What does Jev decide?
Whether a thread needs action, who is waiting, its type, workflow, next step and urgency.
Where do the rules live?
In plain Python in policy.py.
How well does it work?
On a 47-email demo inbox it missed nothing, with caveats noted by the author.
Related projects
Open-source AI email assistant; listed as using Jev as an optional classifier for email intent and triage.
ProjectproductionTypeScriptTriage for DingTalk mail and chats where Jev sorts messages into needs-reply, updates, promo, sales or spam with attention flags.
ProjectbetaPythonGoogle Apps Script that labels, archives or trashes Gmail conversations based on Jev answers to your plain-English yes/no questions.
ProjectbetaJavaScriptGmail classifier running on Google Apps Script where Jev decides action-needed, importance and category for each thread.
ProjectbetaTypeScriptAndroid and Windows message-priority assistant where Jev scores urgency and reply-now for each message and sorts them by colour.
ProjectbetaKotlinLocal-first work-message classifier that uses Jev to sort chat messages into urgent, to-do, worth reading and skip, with cross-chat to-dos.
ProjectbetaJavaScript