Cursor has replaced most of my goose use cases atm

Reply to this note

Please Login to reply.

Discussion

Same, I gave it another shot today and prefer Cline over goose

The competition is insane. Most people have no idea what is happening right now

Nothing stands still. I actually converted someone from Cursor to goose not too long ago. What's working better in Cursor and Line for you guys?

The tools seem to work better and the interactivity is more intuitive

Getting the most out of goose does require a different mindset 🤔 But it's more important that you're using something than that it's goose. This wave is too important.

Stay buoyant 🤙

The edits in Cline are more visible than in goose. I'm cool with being in the loop since I'll be responsible for the code anyway

Have you tried asking goose to write focused PR's?

goose is just cursor YOLO mode without change accept/deny. goose is better for vibe coding if you just want it to go off without much supervision.

I just like being able to select functions to add it to the context. With goose it seems to try to read the whole file to get the functions which floods the context. Maybe once LSP MCP tools are there this will be less of an issue.

People love the term "vibe coding". I prefer "integration tests"