I just made a short video showing how to do this with the CLIProxyAPI tool. It's a very useful and easy-to-use tool, but it can be hard for people who have never used it before. In this video, I showed you how to use any OAuth subscription in Cursor AI.
Links below β¬οΈ
hey @cursor_ai iβd love to be able to use my openai codex sub in cursorβs native agent window
you could even make it available only to active cursor subscribers so people donβt just free-ride
cursor ux + codex sub usage limits would be elite
Tested several open models on their frontend capabilities: same prompt, same harness, same infrastructure... surprised with the results! Would like to know your thoughts. Big thanks to the @gmi_cloud team for the credits! π§΅
I'm just uninstalling all agents'/AI-related coding stuff from my laptop and going to do a fresh start with Cursor (Cursor subscription) and OpenCode (OpenCode Go subscription) and stick to them.
As for skills, it's only mine and Matt's; those are all I need for day-to-day work.
@shamikv@biraj21_@amay_bakshi 2. The interviewee passed the interview presented for the pay. Isn't that enough to qualify the person? Or should the interviewers conduct easier/harder interviews for less/more pay based on the last CTC?
> found a new tool for codebase sanitization
> too lazy to run it locally and watch over it
> go to claude and make it write a long recurisve prompt
> put it in .@cursor_ai cloud agent with grind mode on
> plans it start to end, i approve
mfw when i realise i'm addicted
trying opus 4.8 + minimax m3 combo in claude code (opusplan mode) and seeing m3 error out a lot in cc, where as it worked just fine in opencode and pi
weird
@bridgebench agreed. to truly use it effectively you need to pair with either opus 4.8 or gpt 5.5 and make them plan the whole thing out start to end and then execute with m3.
that's what i did here and got better results:
https://t.co/ZTTxHgwlpY
like here's an exploration:
natural text to resume with editable fields
opus 4.8 did all the planning, and m3 wrote every single line of code; none were written by opus, only planning.
explaination below:
overall, m3 is an excellent worker model, like composer 2.5 is, but it needs a co-ordinator who can take the user inputs and transform them into detailed specs...
that's all! thanks for reading (if you did)
like here's an exploration:
natural text to resume with editable fields
opus 4.8 did all the planning, and m3 wrote every single line of code; none were written by opus, only planning.
explaination below:
ngl minimax m3 is a nice model but as a worker, on its own i found it quite weak in terms of agentic use. Iβd describe a bug lightly and itβd make a bad fix, where as pair it with opus and have opus write a plan for the fix and then m3 executes it perfectly
re-explained the same thing with same prompt and element from react grab, opus understood immediately made a plan, executed via m3 and voila bug fixed, repeated that few more times and got what you see in the video. i didn't make it integrate ai fully because i didn't have time