Claude for one task, Copilot for another, a local model for the stuff you don't want leaving your machine — CortexMesh lets you run them all against the same repo without switching tools. https://t.co/TkI6k9zaPB
The thing I care most about in CortexMesh: agents propose changes, you approve before anything touches your repo. No surprise commits, no "wait, it did what?" moments. https://t.co/s32r4OJNo7
Been building with CortexMesh: a local desktop workbench that runs Claude, Copilot, Cursor, and local models against your own repos — one place to run multiple coding agents instead of juggling tabs. https://t.co/TkI6k9yD03
@N_and_ni well, you're asking the wrong channel. but if you pay me 100 dollars, i'll write you a prompt that will get claude to give you some good ideas.
A friend of mine put this together. I believe he's got a free trial available. Works with #Cursor and #Claude, among a lot more.
https://t.co/r79oUYPRbY
#AI
@md_kasif_uddin It would depend on which one helps you as a developer achieve what you're trying to do. The tool is only as good as the developer/engineer using it.
@UnknownWorlds I just submitted my resume to your open job postings, let me take care of your website. Judging the 2024 copyright date, I'd say It needs some love.
@thdxr I understand having a .env file for the different stages of the pipeline. I do that myself to ensure that I can test and debug different scenarios. However, I think the big issue here is why they are being checked into the repo. There are no excuses for that.
@dev_chip@thdxr I only use Vercel as a dev/test platform. I put my next.js projects on Amplify in AWS, they've been expanding their support for it's features there.