# AI use cases for GPT with Taste (NB-Corp/gpt-with-taste) Repo: [NB-Corp/gpt-with-taste](https://github.com/NB-Corp/gpt-with-taste) | Use cases: 5 | Page: https://dedupedai.com/use-cases/nb-corp-gpt-with-taste/ A set of behavioral instructions and event hooks that steer GPT models in OpenAI Codex, Claude Code, and other coding harnesses. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Install GPT with Taste hooks into Codex: https://dedupedai.com/use-cases/nb-corp-gpt-with-taste/install-taste-hooks-in-codex/ - Add the recipe to Codex with prompt files only: https://dedupedai.com/use-cases/nb-corp-gpt-with-taste/install-taste-prompt-only-in-codex/ - Have a coding assistant install and check GPT with Taste: https://dedupedai.com/use-cases/nb-corp-gpt-with-taste/delegate-taste-install-to-ai-assistant/ - Recover GPT with Taste after a broken or changed install: https://dedupedai.com/use-cases/nb-corp-gpt-with-taste/recover-taste-managed-state/ - Port the GPT with Taste recipe to a new coding host: https://dedupedai.com/use-cases/nb-corp-gpt-with-taste/port-taste-recipe-to-another-harness/ ## How to install GPT with Taste hooks into Codex with GPT with Taste Repo: [NB-Corp/gpt-with-taste](https://github.com/NB-Corp/gpt-with-taste) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Add the recipe and scoped hook reminders to Codex for multi-turn work. **Who it is for:** A developer using Codex Desktop for multi-turn coding tasks who wants GPT to keep its standing priorities across turns. **The problem:** Codex answers each request with default behavior, and reminders about judgment and craft fade across a long session. **The outcome:** Codex loads the recipe as its model instructions, and hook reminders fire on user submissions, child startup and supported wait results in a new session. ### 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 --hooks` 4. In Codex Desktop open Settings → Hooks (or run /hooks in the interactive terminal), review and trust the three installed definitions, and enable only the events you want 5. Open a new Codex session after installation ### Prompt to paste into your agent ```text Clone https://github.com/NB-Corp/gpt-with-taste into , run `node scripts/install.mjs --hooks` from that folder, and report the files written under the active CODEX_HOME. Verify that model_instructions_file now points to the main managed prompt file and that your model, provider and AGENTS.md settings were not changed. ``` ### Caveat The README says to review and trust the hook definitions yourself, and that later child-input coverage depends on the client entry point. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/nb-corp-gpt-with-taste/install-taste-hooks-in-codex/ ## How to add the recipe to Codex with prompt files only with GPT with Taste Repo: [NB-Corp/gpt-with-taste](https://github.com/NB-Corp/gpt-with-taste) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Install the system instructions in Codex without hook reminders. **Who it is for:** A Codex user who wants the behavioral recipe but does not want hooks enabled. **The problem:** The user wants a lighter setup that changes only the model instructions and leaves hook events alone. **The outcome:** The two managed prompt files are written, model_instructions_file points to the main one, and no hooks are installed. ### 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 to paste into your agent ```text In the repository at , 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. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/nb-corp-gpt-with-taste/install-taste-prompt-only-in-codex/ ## How to have a coding assistant install and check GPT with Taste with GPT with Taste Repo: [NB-Corp/gpt-with-taste](https://github.com/NB-Corp/gpt-with-taste) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Give a coding agent the repo and install guide so it handles setup. **Who it is for:** A developer who prefers to delegate setup to a coding assistant and wants the install checked against the official metadata. **The problem:** Setup has several options, update checks and config details, and the developer does not want to read them all. **The outcome:** The agent completes the install, runs the update check, and reports what changed in the Codex home. ### Steps 1. Give your coding assistant the GPT with Taste repository 2. Point it to docs/install-for-ai.md 3. Have it run `node scripts/check-updates.mjs` before installation 4. Have it run `node scripts/install.mjs --hooks` (or `node scripts/install.mjs` for prompt-only) 5. Review the summary of written files and the hook trust step before opening a new Codex session ### Prompt to paste into your agent ```text Use the repository at and follow docs/install-for-ai.md. Run `node scripts/check-updates.mjs`, then install with `node scripts/install.mjs --hooks`, and list every file written under the active CODEX_HOME. Verify that the hook definitions are still untrusted until a person reviews them under Settings → Hooks. ``` ### Caveat The README says to skip the update check with --skip-update-check only for offline installs, so the agent should not skip it on a connected machine. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/nb-corp-gpt-with-taste/delegate-taste-install-to-ai-assistant/ ## How to recover GPT with Taste after a broken or changed install with GPT with Taste Repo: [NB-Corp/gpt-with-taste](https://github.com/NB-Corp/gpt-with-taste) | Difficulty: Advanced | Time: 30 minutes | Basis: From the README Restore the managed Codex files using the recovery guide. **Who it is for:** A Codex user whose managed prompt files or hook settings were changed or lost after an update or edit. **The problem:** Codex is no longer picking up the recipe, or the managed state no longer matches the repository. **The outcome:** The managed state is restored to the installed version by following the recovery guide. ### Steps 1. Open docs/recovery.md in the GPT with Taste checkout 2. Follow the recovery steps for the managed prompt files and model_instructions_file 3. Run `node scripts/check-updates.mjs` to confirm the installed components 4. Run `node scripts/install.mjs --hooks` again if hooks are part of your setup 5. Open a new Codex session and confirm the hook definitions are still trusted ### Prompt to paste into your agent ```text In the gpt-with-taste checkout at , follow docs/recovery.md to restore the managed state under the active CODEX_HOME. Report which files were restored and confirm that model_instructions_file points to the main managed prompt file. ``` ### Caveat The README says customized checkouts need the update instructions in docs/install.md, so a recovery can overwrite local edits you wanted to keep. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/nb-corp-gpt-with-taste/recover-taste-managed-state/ ## How to port the GPT with Taste recipe to a new coding host with GPT with Taste Repo: [NB-Corp/gpt-with-taste](https://github.com/NB-Corp/gpt-with-taste) | Difficulty: Advanced | Time: 1 hour | Basis: From the README Adapt the single recipe to a harness not in the supported list. **Who it is for:** A developer building or running a coding harness that is not Codex, Claude Code, Kiki, Pi, OMP or dsh. **The problem:** The developer wants the same judgment and steering behavior in a host that the repo does not support yet. **The outcome:** A working integration in the new host, built from the single English recipe in recipe/ and the porting guide. ### Steps 1. Read docs/harnesses/porting.md in the repository 2. Read docs/authoring.md to understand the single English authoring source in recipe/ 3. Compare the Claude Code or Pi integration docs as examples of supported hosts 4. Write a host-specific adapter that loads the recipe instructions and routes the steering events your host provides (inferred, check the README) 5. Test one multi-turn task and confirm the reminders reach the main agent and delegated agents ### Prompt to paste into your agent ```text Read docs/harnesses/porting.md and docs/authoring.md in the gpt-with-taste repository at . Produce a short plan for adapting the recipe in recipe/ to , listing the instruction loading step and the steering events to hook. Verify the plan against the existing Claude Code and Pi integration docs. ``` ### Caveat The README says maintainers edit recipe/ and compile across targets, so a new host adapter should follow that build flow rather than fork the recipe. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/nb-corp-gpt-with-taste/port-taste-recipe-to-another-harness/