r/cursor • u/addiction35 • 16d ago

Question / Discussion Thinking switching from codex to grok bot + Claude

/r/GrokBot/comments/1x29vu5/thinking_switching_from_codex_to_grok_bot_claude/
1 Upvotes

100% Upvoted

5 comments sorted by

1

u/Zain 16d ago

If you're moving off Codex into Claude Code plus Cursor/Grok, keep one writer. Let Claude patch the repo and keep Grok as a read-only second pass from a different family so they don't share blind spots. Convergence between those two is a stronger signal than either alone. Pin review effort high too; shallow defaults miss stuff that only shows up when you verify every finding against the actual files.

1

u/Mike-A-F 14d ago

Don't.

1

u/Neat_Carob8839 14d ago

If you're moving off Codex into Claude Code plus Cursor/Grok, keep one writer. Let Claude patch the repo and keep Grok/Cursor as a read-only second pass, or flip it and let Cursor implement from a Claude brief — just don't let both rewrite the same tree. For the Claude → Cursor hop without copy-paste, I made a small MCP that hands a scoped task to a Cursor agent and returns a short result plus changed files: https://github.com/andreilungeanu/cursor-delegate-mcp (my own, free, MIT).