JevMade Sign in
← Back to experiments

Agent tooling

jevbrief

jevbrief fixes the least glamorous part of a Jev integration: what the model actually gets to read. Adapters for CI runs, pull requests, OpenTelemetry exports, and other noisy sources cut state down to what matters, and every dropped line gets a reason.

Bookmark: jevbrief Keep this in your collection.
Leave a noteWhat would you try with this? : jevbrief

Only you can see your notes.

Source screenshot of jevbrief
SOURCE SCREENSHOTFull screenshot ↗

What it does

The project's own benchmark makes the case with a failure story: given a deploy incident whose single config error had scrolled out of the most recent 254 log lines, the raw-logs arm missed it every time while the briefed arm went 18 for 18. Median input fell from 29,678 tokens to 1,070. The data is synthetic and the README says so; inspect mode costs nothing.

How you can use it

To give your AI assistant fewer choices, have a developer try this project's way of sorting its tools. Tools are the actions it can take. Start with a task and keep only tools that fit that goal. This sorting happens on your computer without paying an AI service.

Maker-reported (not independently measured by JevMade): Author-reported (synthetic benchmark): briefed arm 18/18 correct vs 15/18 for raw recent logs, median input 1,070 vs 29,678 tokens, median options 5 vs 254

Primitives
choice, noul
Platform
Python
Added
Project created

Keep this for later

Sign in to bookmark experiments, guides and videos, and keep notes only you can see.

Continue to sign in

We’ll bring you back to this listing.