If you've spent any significant time working with AI assistants, you've probably experienced the frustration: you're deep into a productive conversation when a tangential question pops into your head — maybe even a "dumb" question you need answered but don't want cluttering your main thread. You ask it. The AI answers. And suddenly, your carefully constructed context is polluted with information you only needed for a moment.
I wanted a way to ask these questions with the context I'd already built, but without polluting the main branch context. That's when the idea for stepback.dev clicked — what if conversations could branch like git branches?
You shouldn't have to choose between continuing down a derailed path or starting a new chat and losing all the context you'd built up. Neither option is good.
The Git Epiphany
As developers, we've solved this problem before. Version control systems like Git give us the power to branch off, explore, and merge back. We can try risky experiments without affecting main. We can pursue parallel threads of thought and bring them together when we're ready.
Why shouldn't AI conversations work the same way?
"The best interface for AI isn't new — it's the one developers already understand."
Building in the Open
stepback.dev is open source from day one. We believe the best tools are built with the community, not just for it. If you're interested in contributing, the repository is open and we welcome pull requests.
We're currently in private beta, rolling out access gradually as we refine the experience. If you'd like to try it out, request access or reach out to us directly.
What's Next
This is just the beginning. We have ambitious plans for stepback.dev — check out our roadmap to see where we're headed.
Thanks for reading. If this resonates with you, we'd love to hear your thoughts.
— The stepback.dev team