Every developer knows the loop: write code, run it, it breaks, paste the error into ChatGPT, fix, repeat. AI tools haven't solved this. They've just moved the chat window closer. NOVA kills that loop. Build: Describe your goal, NOVA writes the files. Auto-Heal: Run your code, NOVA fixes errors automatically. Janitor: Refactor any file on demand. Git: Commit, push, pull inside the terminal. pip install nova-bridgeye What would make this irreplaceable for you?
Hey PH!
Team Bridgeye here, makers of NOVA.
We built this because we kept running into the same wall, AI tools give you suggestions but you're still the one running code, reading errors, and manually fixing things. NOVA is our answer to that.
A few things I'd love your thoughts on:
What would make Auto-Heal actually irreplaceable in your workflow?
Are there languages or environments you'd want us to prioritise next?
To get started: pip install nova-bridgeye
For docs and full command reference, check out our documentation at https://nova.bridgeye.com/docume.... We're early, actively shipping, and genuinely reading every comment. Roast us if you need to, it only makes NOVA better. 🙏
Auto-healing is a great DX improvement. Curious — how are you thinking about user acquisition for a dev tool like this? Paid search has been interesting for that category.
Curious how NOVA handles workspace isolation when multiple developers are running agents concurrently do you spin up separate environments per session or share a runtime context? That architecture decision tends to have some interesting downstream effects on both performance and consistency.
The Auto-Heal feature is the real hook here. Most of us waste 40% of our dev time just acting as a human clipboard between the terminal and a LLM. If Nova can intercept a traceback and just apply the fix, it moves the AI from a consultant to a co-pilot.
very cool! We're doing something similar, but focused on Web3. All the best!
Bridgeye