Letter from the Founder
Hi, I’m Janos, the creator of TryYourPrompt. The idea came while working on multi-agent AI applications, where even a tiny prompt adjustment meant re-running the entire system. I’d spend more time waiting for API calls and debugging orchestration than actually improving the logic. That constant friction made me realize how much creative and technical energy was being wasted.
I wanted to change that - to create a space where I could focus purely on the prompt itself, test in isolation, and immediately see the outcome. TryYourPrompt was my solution: a tool built to eliminate the clutter between idea and execution.
Over time, my approach evolved from solving my own workflow pain to building something for the whole community of prompt engineers and AI builders. The vision became clearer - not just to make testing faster, but to make prompt engineering feel like real engineering: precise, iterative, and deeply creative.
Hi everyone, Janos here, the creator of TryYourPrompt.
New release is live!
I’ve just shipped a fresh update with two big improvements:
Token usage & cost display – You can now see exactly how many tokens your request used and what it costs, right inside the app.
Dynamic variables in prompts – Inject custom variables into your prompts and make them more flexible, dynamic, and context-aware.
These updates make it easier to experiment, track, and fine-tune your workflow.
I’d love to hear what you think - what’s the first variable you’re planning to inject? 👀
you’ve built exactly what prompt engineers needed. I use a simple 5-step prompt framework (Role, Task, Audience, Tone, Goal) to speed up my work but testing still eats time. A tool like TryYourPrompt could make that whole iteration loop way smoother.
Thank you for your valuation! :) What do you think I should add to the project?
You’ve nailed the iteration pain, but a few extra boosts could be: context-aware prompt suggestions, dynamic variable injection for multi-scenario testing, AI alerts for hallucinations or bias, and a mini dashboard showing token usage and API cost per run. Small features, huge workflow gains
I've just released a new version, worth to checkout ;)
These are excellent features, I've already thought about a few idea. Thank you for your support! :)
Great write-up. The bit about “real engineering” in prompt work hit home, so true that debugging orchestration often overshadows creative iteration. Have you experimented with chaining summarised test logs to track changes over time?
I've not YET, but great idea! :)