Regarding what #2 said about glitching, im super satisfied with Aider AI CLI Tool v0.70.0. It works well with DeepSeek and saves a fortune on tokens by being way more precise.

> Continue is easier to set up but its glitching Be careful, Roo drains tokens fast. I would suggest Cline VS Code Extension v2.10.0 for granular context control or Double.bot AI Coding Assistant for more stable DeepSeek API streaming.

> Continue is easier to set up but its glitching on the DeepSeek API and i cant figure it out. Ive been using both for a while and honestly, the glitching youre seeing with Continue IDE Extension for VS Code is usually just a tiny misconfiguration in the config.json file. For a Tuesday deadline, you probably dont want to spend hours learning the Roo Code workflow because it acts more like an autonomous agent. It is way more powerful, sure, but the learning curve is real and it can be a bit overwhelming at first. If youre using the DeepSeek Coder V2 API, make sure your base URL in Continue is set exactly to the official endpoint. People often forget to add the /v1 suffix or accidentally leave out the provider field in the json. If you want something rock solid for a low budget setup, stick with Continue for now. It uses less overhead than Roo Code AI Agent VS Code Extension which can get pretty resource-heavy when it starts indexing your whole workspace or running its internal logic loops. Roo Code is fantastic when you need it to actually create files and run terminal commands for you, but it burns through tokens way faster. If you just need code completion and a chat sidebar to help with logic, Continue is the way to go. Just double check your API key and provider settings... usually solves the glitching instantly. Let me know if you need the specific config snippet, I can dig mine up and post it here if youre still stuck.

Saw this earlier but just getting back to it! ^ This. Also, please be so careful with those autonomous agent tools when you are on a tight deadline! Roo is absolutely amazing but it can be a total nightmare if it starts hallucinating file changes right before Tuesday. I love the power it gives you, but for a budget setup, it is just so risky and can burn through your credits so fast! If the extensions are acting up, honestly just use the official web interface as a fallback. It is way more reliable than fighting with buggy API integrations when youre stressed. It might not be as cool as having it right in your editor, but at least it wont crash or mess up your config. Better to be safe and get that project finished on time!

Gonna try this over the weekend. Will report back if it works!