A fresh build dropped on Reddit this week, and the real surprise shows up in step two. It solves a problem anyone shipping AI prompts at scale already knows well: you can’t sit there editing one prompt by hand forever. Kai_ThoughtArchitect is the Redditor who shared it. They call the tool Titration, and it’s been running quietly in their own stack for months before going public.
I remember doing the manual version of this. Open a sandbox. Change a line. Run it. Read the output. Change it again. That works fine when you’re the only one touching a single prompt. Multiply that by a growing team of prompts, and the busywork swallows the day. It stops working the moment “AI product” means dozens of prompts, each one needing constant small fixes nobody has time for.
What’s new
Titration automates that entire back-and-forth. You tell it the style or behavior you have now, and the style or behavior you want instead. It takes those two reference points and builds a custom harness around your exact use case, a dedicated testing setup, not a generic one. Once the harness exists, Titration runs its own loop inside it. It works on any prompt, in any AI system, which is the part that makes this more than a personal workbench script.
Harness and loop are two words everyone in AI tooling throws around now, and Titration is built from both. The harness is the custom test rig Titration builds for your specific prompt and goal. The loop is what runs inside that harness: make a small change, see what happened, and decide the next move. Repeat.
The twist
Here’s what caught me off guard. Titration doesn’t just rewrite the prompt and hope for the best. It makes one small change, checks the result, and measures how that change shifted the output. Then it decides the next move from that feedback. It’s a closed loop, not a single guess.
The creator shared two cases that show the range. First, style matching: say your agent generates narration or copy that’s close but not quite right. You tell Titration “this is the style I have now, this is the style I want” and hand over a reference sample. It builds a baseline and keeps iterating until the output actually lands in that voice.
Second, something gnarlier: a prompt buried deep inside a RAG system with lots of moving parts, quietly misbehaving. You describe how it should work. Titration measures where it sits today, builds the harness, and iterates toward the goal. The creator noted it can even surface issues you’d never have spotted yourself.
If you’ve used a prompt playground or a manual A/B testing sheet before, this is the automated version of that same instinct. The difference is that nobody has to sit there clicking “regenerate” for the fiftieth time.
Try it yourself
Here’s a mini-workflow if you want to run this against your own prompts:
- 🎯 Pick one prompt that’s clearly underperforming, something with an obvious gap between what it should do and what it’s actually doing.
- 📝 Write down the current output and the output you actually want, side by side, as your reference pair.
- 🔁 Hand both to Titration, let it build the harness, and watch the iteration log pass by pass.
- ✅ Stop once the result holds steady across a few different test inputs, not just the one you started with.
Each pass in that log shows what changed and why, which is honestly the most useful part. You get to see the reasoning behind every small edit instead of just a final diff.
Pro tip
Hand Titration a reference sample with enough length to show real rhythm, not three sentences. The more texture it has to measure against, the fewer iterations it needs to lock the style in. A thin sample means more guesswork and more passes before it converges.
If you’re maintaining a RAG prompt that’s drifted from its original intent, don’t wait for a support ticket to notice. Run Titration against it proactively, catching the drift yourself beats hearing about it from a confused user.
This isn’t a one-off trick. It’s a system for the exact thing most AI builders quietly ignore. Prompts rot as models change underneath them, and nobody goes back to retune every one. Any AI app with a prompt inside it, which is basically every AI app, is a candidate for this. That’s the kind of leverage worth stealing.
The original Reddit thread has the full breakdown and the repo link straight from the creator. Go check it out, steal the workflow, and let your prompts fix themselves for once! 🚀
Tell it the style you have and the style you want, and let the AI iterate until it gets there
by u/Kai_ThoughtArchitect in ChatGPTPromptGenius