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

How to stop tool use when a session shows a mismatch with Is GPT Nerfed

Turn on halt_on_mismatch so Codex blocks tools until you say resume after a mismatch.

Who it is forA team lead or careful solo developer who would rather pause an agent than let it keep working on a possibly wrong model.

The problemAn agent running tools keeps going after the model has changed, and the work done after that point may not be what you asked for.

The outcomeAfter a mismatch, tools stay blocked in that session until you say resume.

What you need first

  • A Mac running macOS 15 or newer
  • Codex with plugin hooks (the README says it was tested on 0.154), desktop app or CLI
  • The system python3
  • Terminal access for the install line

Steps

  1. Install the app with curl -fsSL https://raw.githubusercontent.com/kiyoakii/is-gpt-nerfed/main/install-app.sh | sh if it is not already installed.
  2. Run nerfed config set halt_on_mismatch true, or change the setting to on in the app's Settings. (inferred, check the README)
  3. Work in Codex as usual and let the scheduled probes run.
  4. When a mismatch appears, read the evidence in the session report with nerfed explain <session>. (inferred, check the README)
  5. Say resume in the session only after you have confirmed the model is acceptable.

Prompt for your agent

In the kiyoakii/is-gpt-nerfed repo, set halt_on_mismatch to true, then confirm the setting is saved with `nerfed config` output or the app Settings. Report the current value and whether a mismatch has blocked tools in any session.

Caveat. The exact syntax for setting values from the terminal is not shown in the README, so confirm it with the app Settings before relying on it.

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