3 ms·
Show HN: Helix – open-source self-healing back end for production crashes
Six months ago I got tired of being woken up at 3am for bugs I already knew how to fix.
So I built Helix. Bug hits Sentry. A multi-agent pipeline kicks off. QA agent writes the failing test first (TDD). Dev agent writes the minimum fix, runs the full suite, opens a PR. You get a Slack message with one button to approve.
Crash to merged PR in under 10 minutes.
- NomiJ 6mo ago[dead]
- grimmai143 6mo agoI wonder how it handles a codebase so large it doesn't fit in the context window.
- NomiJ 6mo ago[dead]
- pentaphobe 6mo agoOff topic, but whilst we've clearly got to accept name collisions in such a large word - it'd be ideal if there was _a modicum_ of care around not using names on other actively maintained projects https://helix-editor.com/ https://helix-editor.com/
- NomiJ 6mo agoFair point. I was not aware of Helix Editor when I named the project. That is my mistake. The project is early enough that renaming is still possible if it becomes a real issue. Would you recommend a rename now or wait to see if the name collision actually causes confusion?
- pentaphobe 6mo agoFair question! I've no idea, but good on you for pondering If it were me I'd rip the band-aid off, but might just be me being grey-beard. Name Collisions are inevitable these days I guess, and equally one could argue that no project should be able to camp out on a dictionary term :) Either way, best of luck with your project (which looks super interesting) - I neglected to say that bit :facepalm: