Analyze reports with Jev
Find recurring problems in agent work and choose what to improve next.
Jev sorts agent reports by the problems they describe: confusing instructions, broken tooling, difficult code and other recurring obstacles. Use those patterns to choose what to improve next.
Turn it on
Get a key from the TypeSafe dashboard. Add it to .env.local in your project's root, then run PhaseDrift from that project:
TYPESAFE_API_KEY=your-key-herephasedrift init --analysisIf your tracker is already running, run phasedrift restart after adding the key. Keep .env.local out of Git.
Analysis runs automatically as reports arrive, with a default limit of 10 requests a day. It sends saved report text to TypeSafe; provider billing applies.
See what it finds
Open your local dashboard:
- Agent work → Reports: open a report's Analysis tab to see its classification.
- Improvements: inspect suggestions and choose a change to try.
Track the change and compare the results to see whether it helps. A classified report gives you a lead; the follow-up work provides the evidence.
Check setup or change the request limit
Run phasedrift learning status to check whether your key is loaded, analysis is enabled and reports have saved classifications.
For budget controls, older CLI versions and troubleshooting, use the Jev reference.
Reports and tracked improvements also work without Jev. Privacy and costs.