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

How to add the recipe to Codex with prompt files only with GPT with Taste

Install the system instructions in Codex without hook reminders.

Who it is forA Codex user who wants the behavioral recipe but does not want hooks enabled.

The problemThe user wants a lighter setup that changes only the model instructions and leaves hook events alone.

The outcomeThe two managed prompt files are written, model_instructions_file points to the main one, and no hooks are installed.

What you need first

  • Node.js 22 or newer installed
  • OpenAI Codex (Codex Desktop or the interactive terminal) with access to a GPT model
  • A terminal and a local clone of the NB-Corp/gpt-with-taste repository

Steps

  1. Run git clone https://github.com/NB-Corp/gpt-with-taste.git
  2. Run cd gpt-with-taste
  3. Run node scripts/install.mjs
  4. Open a new Codex session after installation

Prompt for your agent

In the repository at <repo-path>, run `node scripts/install.mjs` and confirm that the two managed prompt files were written to the active CODEX_HOME. Verify that the installed config still uses the same model, provider and permissions as before.

Caveat. The README describes the prompt-only route as an option, and you lose the hook reminders that the --hooks route adds for multi-turn work.

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