zlacker

>>net01+(OP)
I love Copilot in VSCode. I have it set to use Claude most of the time, but it let's you pick your fav LLM, for it to use. I just open the files I'm going to refactor, type into the chat window what I want done, click 'accept' on every code change it recommends in it's answer, causing VSCode to auto-merge the changes into my code. Couldn't possibly be simpler. Then I scrutinize and test. If anything went wrong I just use GitLens to rollback the change, but that's very rare.

Especially now that Copilot supports MCP I can plug in my own custom "Tools" (i.e. Function calling done by the AI Agent), and I have everything I need. Never even bothered trying Cursor or Windsurf, which i'm sure are great too, but _mainly_ since they're just forks of VSCode, as the IDE.

>>quanta+IK
Try doing https://taoofmac.com/space/blog/2025/05/13/2230, you’ll have some fun,

>>rcarmo+ZR1
I've come to the same conclusions mentioned in most of that and done most of that already. I was an early-adopter of LLM tech, and have my own coding agent system, written in python. Soon I'm about to port those tools over to MCP so that I can just use VSCode for most everything, and never even need my Gradio Chatbot that I wrote to learn how to write tools, and use tools.

My favorite tool that I've written is one that simply lets me specify named blocks by name, in a prompt, and AI figures out how to use the tool to read each block. A named block is defined like:

# block_begin MyBlock ...lines of code # block_end

So I can just embed those blocks around the code rather change pasting into prompts.