3 ms·
Man, I'm not so sure if I'd use something like this because the way I prompt already changes based upon what model I am using. I'm not convinced it would route
by g00k 3mo ago
Man, I'm not so sure if I'd use something like this because the way I prompt already changes based upon what model I am using. I'm not convinced it would route to the right model based on my diction or whatever.
- alansaber 3mo agoYep this was always the reason to avoid "auto" mode in cursor.
- adchurch 3mo agoYeah that's a really interesting point, tbh I think the more relevant variable here is the harness you're using rather than the specific model? i.e. GPT 5.5 in the Claude harness behaves a lot more like Claude than Codex if that makes sense. Hard to quantify this ofc but that's what I've felt vibes wise from using this for the last month.
- devmor 3mo agoI have the same general feeling as well. Like you, I can’t prove it’s not just personal feeling - but e.x. Opus via Copilot CLI behaves entirely different than Opus via Claude Code, which behaves differently than Opus via OpenCode or Pi.
- ValentineC 3mo agoI have the same feeling. I've been trying Claude Code directly ever since Copilot nerfed their request-based system, and Opus just seems to perform "better" in Claude Code. It's also possible that it's the 1m context versus the 200k context (Copilot's limit) doing some of the work here.
- stronglikedan 3mo ago> Man, I'm not so sure if I'd use something like this because the way I prompt already changes based upon what model I am using. Perhaps you're just not the best use case. It may work better when Average Joe is the one prompting.