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

How to probe a brand-new session before a long task with Is GPT Nerfed

Run the Fresh session probe to see which model a new Codex session gets right now.

Who it is forA developer about to start a long or costly Codex task who wants to confirm the model before committing to it.

The problemA session that is already running may have been served differently earlier, and you want to know what a new session gets at this moment.

The outcomeA fingerprint verdict for a brand-new session that tells you whether the model you selected is answering now.

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. Open the menu bar panel and find the Fresh session row.
  3. Click Probe on the Fresh session row to probe a brand-new session.
  4. Read the verdict. Match means the model you selected answered.
  5. Start the long task only after the verdict is Match, or after you have decided how to handle a mismatch.

Prompt for your agent

In the kiyoakii/is-gpt-nerfed repo, trigger a probe of the Fresh session from the menu bar app or with `nerfed probe now`, then report the verdict and the model you selected. Verify that the verdict is one of Match, Suspicious, Downgrade, Upgrade, Rerouted, Downgraded, Upgraded, Unlisted, or Invalid.

Caveat. A probe costs three short answers on your account, and a model outside the fingerprint bank is only mapped to its nearest look-alike.

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