NomiJ

Fair 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?

Helix watches your error tracker (Sentry or Rollbar). When a bug hits production, a pipeline of agents kicks off automatically: 1. Crash Handler agent parses the webhook and extracts context 2. QA Agent follows test driven development approach and writes a failing test then opens a GitHub Issue 3. Dev Agent clones the repo, writes a fix for failing test, and creates a PR. 4. Notifier sends the issue + suggestion to Slack for human review with "Approve PR" or "Reject PR" options.

Built with Python, Redis pub/sub for the event bus, and Claude (or Ollama if you prefer local). Self-hostable via Docker Compose.

GitHub: https://github.com/88hours/helix-community

Happy to answer questions about the agent architecture or how the fix suggestions are generated.

It also ship Helix as a Claude skill, so if you are already using Claude Code or Cowork you can get the whole pipeline running in one install with no manual config.

100% this. I have used support multiple times, there were times when calls took more than 12 hours. We used basic and Whenever I needed support I turned on to "Business" - from memory it costed 100 bucks a month.

chatGPT at backend?