@joshalbrecht@JustinMurray@ghostdotbuild Looks like lots of people are playing in this space. I built git-treeline with similar goals and open sourced it.
https://t.co/u8osdaLLyc
@BrockHerion@arvidkahl I’d love your opinion on https://t.co/u8osdaLLyc
It’s early and I’ve mostly built it initially for my workflow needs but it’s changing how I work.
I’m a 39-year-old entrepreneur,. I’ve worked with all sorts of clientele and have been in more awkward situations than I can count.
That said, I will bend over backwards, and jump through every hoop thrown at me to not say “Thank You to a Chick-Fil-A employee.
@mntruell not sure if this is already on the roadmap, but there’s a workflow I use in Cursor that feels like it could be formalized into a UX pattern: collaborative refactor sessions with automatic sub-task spinouts.
Example: I’m refactoring authorization across all controllers. I outline a process for the main refactor, and the AI audits the current state, proposes changes, and waits for my confirmation before moving to the next controller. Along the way, I often find out-of-scope issues. When that happens, we create a markdown file describing the problem and hand it off to a separate agent to build its own plan. This keeps the primary agent focused and prevents derailing the main workflow.
It would be great if Cursor could support this kind of structured, dynamic workflow. Happy to chat with anyone on the team if you want to dig into it!
Thanks for Cursor and all your team is doing! If you looking for UX people hit me up!
I get it, there are many people with no development training “vibe-coding” ideas, but for principal and senior engineers, vibe-coding is so far from being an accurate term.
Seasoned engineers are wielding AI agents & frameworks within their workflows to build quality code with efficiency, performance, security, and more in mind. That is not vibe coding, but what is it?