DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to compare a judge in shadow mode before trusting it with Mu

Log what the judge would do without letting it change anything, then read the verdicts.

Who it is forA developer who wants evidence that a judge makes good calls before relying on it for permissions or context.

The problemSwitching on an unfamiliar judge changes agent behavior with no preview of its decisions.

The outcomeA ledger of judge verdicts, with probabilities and timings, for decision points that changed nothing.

What you need first

  • Node.js 22.19 or newer for the command line, or the desktop installer for macOS, Windows or Linux
  • An API key or a supported ChatGPT, Claude, Grok or Google subscription (the free Jev on OpenCode Zen answers until you set a judge key)
  • A project folder to work in

Steps

  1. Install Mu with npm i -g mu-agent and run mu setup.
  2. Open ~/.mu/agent/mu.json and set the content to {"modes": {"default": "shadow"}}.
  3. Run mu on a small task in your project folder.
  4. Run mu ledger to read each verdict, its probabilities and its timing.
  5. Once you have seen enough, remove the shadow setting so the decision points return to their default of active. (inferred, check the README)

Prompt for your agent

Set up the mu coding agent (github.com/qybaihe/mu) in shadow mode by writing `{"modes": {"default": "shadow"}}` to ~/.mu/agent/mu.json, then run a small task with `mu` in <project path>. Expected output: a ledger of verdicts that changed no behavior. Verify with `mu ledger` that the entries show probabilities and timing.

Caveat. The README only describes shadow mode as a per-decision-point setting, so check the default config before relying on the exact JSON shape.

Share: 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