Your own receipts

Where does your agent lose you?

Point Emulo at your agent logs. It finds the moments you sent the same ask again, re-explained context, rephrased the same request, or opened with a correction.

The files stay on this machine. This page reads the folder in your browser, runs the checks here, and makes no network request. Closing the tab clears the result.

Emulo scanready
01

Choose your log folder

Pick the folder itself. Emulo searches its subfolders for JSONL sessions.

Copy one, then paste it into the folder dialog. Both folders are hidden by default, so typing the path is faster than browsing for it.

Chrome and Edge use direct folder access. The browser fallback works without it.

02

Reading your side of the conversation

Finding JSONL session files…

0 / 0 files0.0s
03

Your scan

These checks only read messages you typed. They cannot see model quality, token cost, tool calls, or whether a correction was justified.

The obvious next move, and whether it works

Most people answer a scan like this by writing the agent a rules file. I tested that properly before recommending it: the same tasks on this repo, run with the rules loaded and without them, scored blind. One of the two things I was sure would help made the agent measurably worse.

Read what the harness found, or six failures my own agents shipped with every check green.

If you want that harness pointed at your repo and your rules, write to founder@viberaven.dev and say what your agent keeps getting wrong. Ohad reads them.

!

Nothing to scan yet