[oersted]

Man, it's such a shame that you pivoted away from the canvas-based editor concept, it was such a pleasure to use, it's so much better than tabs.

https://github.com/haystackeditor/haystack-editor

It's still probably the best tool to navigate, visualize and understand complex codebases, which is particularly important now with AI coded repos. I keep looking for alternatives but they are all notably worse.

About a month ago I spent a few frustrating hours building it from source for my system and making it work, and I've enjoyed using it as my main IDE since.

I wish I had the time to make a fork and bring in a newer version of VSCode. If anyone takes it up I might help at least.

[akshaysg]

Yeah I agree it's a shame. Unfortunately coding has changed fast and I was not confident that the editor was in the correct direction with AI coding becoming so prevalent.

I think there is a lot of value with "reconnecting" with your codebase, so I do have some plans to bring the core concept of Haystack back in one form or another.

[wsve]

I am very confident that editor is the direction I want coding to go. I really encourage you to consider picking it up again. Debugging complex graphs of function calls is not going away quite yet.

[akshaysg]

If you see my reply, I would absolutely love it if you could email [e-mail] with some details about your desired use cases!

[srigbok]

This looks like a great project! If you're expecting a lot of inbound emails for your use case research, it might be worth running them through an email verification service. This helps ensure you're only contacting valid addresses and reduces bounce rates.

[visekr]

100% - tried forking VSCode too, scratched it. Way too much work to restyle, and I started wondering if IDEs should even be code-focused anymore. Built https://getmesa.dev instead, a canvas-based IDE for Claude Code & other CLI Agents. Kinda stuck on direction though - lmk if you've got ideas or wanna help out : )

[tikimcfee]

I'd certainly love to help! I've also been working on a canvas for building agentic flows and workspaces, and I'm actually at an intersection to what you're doing with that application you're showing off. I have a simpler node based stream system for flight control of arbitrary agent actions, meant to be operated by one or more orchestrating agents. Eg, the agent understands the surface it can create nodes with, generate dynamic tools and functions within the node specs, and then write graphs of them together so it's live and observable. Extremely intersectional, haha.

Happy to chat whenever you'd like, I can stalk a contact for ya or vice versa!