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

How to port the GPT with Taste recipe to a new coding host with GPT with Taste

Adapt the single recipe to a harness not in the supported list.

Who it is forA developer building or running a coding harness that is not Codex, Claude Code, Kiki, Pi, OMP or dsh.

The problemThe developer wants the same judgment and steering behavior in a host that the repo does not support yet.

The outcomeA working integration in the new host, built from the single English recipe in recipe/ and the porting guide.

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. 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 for your agent

Read docs/harnesses/porting.md and docs/authoring.md in the gpt-with-taste repository at <repo-path>. Produce a short plan for adapting the recipe in recipe/ to <target-host>, 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.

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