Who it is forA developer or researcher who wants to see how an evolved harness changed decisions before building one.
The problemReading harness code alone does not show how it behaved in actual games.
The outcomeA local viewer showing the archived run, the evolution tree, and complete decision records with synchronized Jev answers.
What you need first
- Claude Code or Codex installed
- Git, and Node.js for the local archive viewer
- Access to Jev model calls, since plugin installation does not configure model keys
- A Python environment if you plan to build and run a harness yourself
Steps
- Run
git clone https://github.com/TianyuCodings/JevHarness.git. - Run
cd JevHarness. - Run
node website/build.mjs. - Run
node website/preview.mjs --port 8768. - Open http://localhost:8768 in a modern browser.
Prompt for your agent
Clone https://github.com/TianyuCodings/JevHarness, build and preview the website with Node.js on port 8768, then report the number of archived Eval games shown on the page. Expected output: the viewer loads at localhost:8768. Verify that browsing makes no model requests and starts no games.
Caveat. Battle animations download assets from the official Pokémon Showdown renderer, so the viewer needs network access for them.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page