User repository on GitHub
A Magic Jev (8) Ball for pull requests.
- Forks
- 0
- Last pushed
- Updated Sep 2026
Repo stats from the GitHub API, cached Oct 2026.
CommunityJev Agents & MCP
Magic Jev
Chrome extension that puts a Magic 8 Ball on GitHub pull requests: nine signals from the GitHub API go to a small server, Jev picks one of four verdicts, and the ball answers with a phrase plus its reasoning. It never approves, comments or reads code.
- Stars
- 2
- Language
- TypeScript
- License
- MIT
- Published by
- Community
- Author
- acharyaanusha
- Last verified
- Oct 2026
About this project
A Magic 8 Ball for pull requests. Open a PR, click the ball, and it answers "should I approve this?" with one of the 20 classic phrases. The answer isn't random: the PR's real signals go to Jev, a typed-decision model that answers in about 200 ms, which is fast enough to land while the ball is still shaking. It's a toy with a real point. Jev doesn't write text. It gets structured state and picks one option from a short list, so it can sit inside an interaction that a chat model would make you wait for.
Quoted from the project's README. Read the full README.
Works forJev for Classification
Used inJev for Software & DevTools
- Languages
- TypeScript
Highlights
- Nine signals come off the GitHub API: CI state, lines and files changed, docs-only, tests touched, approvals, changes requested, draft, bot author.
- Jev picks one of four verdicts from plain-English criteria; the extension picks a random phrase from that verdict's five, so the variety is cosmetic.
- The criteria also exist as code, and a verify script pushes 42 synthetic pull requests across the thresholds to check Jev against the rule.
- The server receives the nine signals and nothing else: no repo name, no title, no code, no login. A GitHub token only goes to api.github.com.
Watch out
Out of the box the extension calls a shared server the author runs and pays for, capped at 20 asks a minute per address and a few dollars of Gateway spend a month, with no uptime promise; when that budget is gone the ball goes hazy until the month turns over. Anonymous GitHub reads cover roughly a dozen asks an hour on public pull requests, and a token needs the classic repo scope because fine-grained tokens will not read checks on a private repository. Jev itself fails to answer on roughly one call in thirty, in bursts, costing a few seconds and a hazy reply. On a repository with no CI every pull request comes back unclear, which the README frames as the rule working. The Server URL must be a vercel.app address or localhost unless you rebuild the extension. Copy reviewed against the repository README on 2026-10-04, not from running it.
Questions about this entry
Short answers drawn from the linked project or page.
Counting, and the README is upfront about it. It never reads your code; it answers whether a pull request can be approved on a light read from nine signals and shows which ones drove the verdict. It also never acts — no approve, no comment, no merge — so the worst case is a bad joke sitting next to your diff.
Both, which is why the criteria get checked. They live as plain English and as code, and the verify script sends 42 made-up pull requests clustered around the line thresholds — 49, 50, 51 lines and so on — to compare Jev's verdicts against the coded rule; the author's five runs all matched, at roughly 200 to 250 ms each. Reword the criteria and that check means nothing until you re-run it.
The nine signals and nothing else: no repository name, no pull request title, no code, no GitHub login. It does see your IP address like any web server, and Vercel's own request logs keep it for as long as Vercel keeps logs. A GitHub token, if you add one, stays in extension storage and is only ever sent to api.github.com; the script that draws the button never sees it. There are no analytics.
Yes, and it is a documented path: clone it, deploy to Vercel with Node 22+, set a passphrase so the server rejects requests without it, then point the options page at your own deployment. Note that the Gateway authenticates itself on a Vercel deployment, so there is no key to set — but the team still needs Gateway credits, since free-tier calls were rate-limited until a few dollars were added.
yes when CI is passing and the change is docs-only or at most 50 lines. lean_yes when CI passes and the diff is 51 to 300 lines. unclear when CI is pending or missing, or the diff is 301 to 800 lines, because that needs a real read. no when CI is failing, the PR is a draft, changes are requested, or the diff is over 800 lines. Jev picks the verdict and the extension picks one of that verdict's five phrases, so the 8 Ball variety is cosmetic.
The line under the ball names the failure: a private PR needing a token, GitHub's hourly anonymous limit used up, a token that cannot see the repository or read checks on a private one, a revoked token, too many asks against the 20-per-minute-per-address server cap, the shared server's monthly Gateway budget running out, or Jev not answering in time. Jev itself failed to return on roughly one call in thirty in the author's runs; the server allows 1.5 seconds and asks once more, so a bad moment costs about three seconds and one hazy reply.
One ask is one Jev call costing a small fraction of a cent, reached through Vercel AI Gateway as typesafe-ai/jev. The shared server caps at 20 asks a minute per address and a few dollars of Gateway spend a month, after which the ball goes hazy until the month turns over. The project is MIT licensed, is not affiliated with TypeSafe, Vercel, GitHub or Mattel, and Magic 8 Ball is a Mattel trademark, so this is a fan-made homage.
More Jev resources like this
20GitHub stars
TypeScript SDK and CLI coding agent where Jev only picks options while your code runs effects, building programs as syntax trees.
Jev Agents & MCP#community#awesomejev#catalog-import
Community
rhighs/jev-codeTypeScript
rhighs/jev-codeTypeScript22GitHub stars
Runnable agent harness that moves pick, score and yes-no loop choices to Jev or Laya in milliseconds while reserving the language model for writing, compiling DECISION.md into executable questions.
Jev Agents & MCP#community#jevbest#catalog-import
Community
zjunlp/JevLoopTypeScript
zjunlp/JevLoopTypeScript35GitHub stars
Diff-aware test selector that sends the git diff to Jev with one question per test, then prints the native filter flags and hands them to vitest, jest, node, bun, Playwright, cargo, or go test.
Jev Agents & MCP#community#jevbest#catalog-import
Community
mizchi/jev-test-filterTypeScript
mizchi/jev-test-filterTypeScript13GitHub stars
Pi extension that classifies each task with Jev over OpenRouter and routes it to a Pareto-optimal model balancing measured quality, cost, and latency under a role policy.
Jev Agents & MCP#community#jevbest#catalog-import
15GitHub stars
Node CLI that lints a file tree against fuzzy natural-language rules in one Markdown file, judging each matched file with a swappable TypeSafe-backed judge.
Jev Agents & MCP#community#jevbest#catalog-import
Community
tyler-dot-earth/patdownTypeScript
tyler-dot-earth/patdownTypeScript106GitHub stars
Decision layer exposing Jev's typed yes-no, choice, and score answers to DeepSeek Harness and MCP hosts, offline by default with every network transmission disclosed per feature.
Jev Agents & MCP#community#jevbest#catalog-import
Community
PerryLink/jevcoreTypeScript
PerryLink/jevcoreTypeScriptFrom the Jev community
Posts from builders shipping with Jev right now.