Just noodling with an idea for a debugger for Elixir and Phoenix. The initial 39 tests are passing, and there are plenty of dreams.
Is this worth pursuing? What functionality is most important to you?
For me, I’m dreaming of an innovative HITL-debugger integrated into an agentic workflow. This noodling from today is primarily slop-storming with Claude/Grok/Gemini/Cursor to flesh out the ideas. I even tried Jules but it wasn’t up to the task. The slop-of-consciousness is included in the repo via quasi-organized markdown files.
Per the README:
ElixirScope is a state-of-the-art introspection and debugging system for Elixir applications, with special focus on Phoenix web applications. It enables comprehensive tracking of processes, message passing, state changes, and function calls, with AI-assisted analysis capabilities.
Any feedback, especially critical feedback whether in terms of the ideas within, or redundancy/irrelevancy as such, is very much welcomed.
This is a fairly complex project. Is anyone else interested in working on it? I’m flexible on the product requirements. Development started only three days ago, thus major changes to features/arch are okay at this time.
The scope has expanded to include Graph Generators for CFG, DFG, CPG.Tests are passing for these features. >1,000 passing tests thus far.
Please see current docs on the github.
Next up is a broad stabilization effort via code review, cleanup, refactoring, warning analysis, runtime error fixes, and significant expansion of all AST-related tests, including CPG components. This milestone will mark the v0.0.2 release.
Once stable, CPG formalization efforts will commence (per docs on github:
“./CPG_*.md”)
As a mere mortal, collaboration would certainly help to accelerate the project. It’s a chance to build an innovative tool in Elixir. LMK! I lt would be a pleasure to formalize tasks for your convenience.
The mockup from the last post had over 1,000 passing tests, but lib was over 40,000 LOC. The project became disorganized and unwieldly, thus reviewing new structures for the code base became necessary.
Here’s the revised structure:
I am kindly requesting that a seasoned Elixir engineer review this proposed structure, and provide critical feedback.
Still iterating on the foundation. Learning so much. This is my first attempt to write a non trivial OTP application, so bear with me.
Humbly requesting for a seasoned OTP engineer to review the plans for building the infrastructure layer into the foundation. The ServiceRegistry and ProcessRegistry implementations are done but need test coverage. And the Infrastructure component implementation has not yet commenced. Here’s the proposed design (this link may break down the road):
The original project idea, which was a smaller scale development debugger, wouldn’t need all this infrastructure. So, this project has turned into an educational project more than anything. A reusable foundation for a large scale Elixir app would be nice, too, if possible.
I’d be super humbled if someone with relevant experience could review the above Infrastructure plan and provide constructive critical feedback. So far, all design has been the result of some googling, but mostly prompting Claude/Gemini/Grok.
