4 ms·

I've also had the exact opposite experience with tone. Claude Code wants to build with me, and Codex wants to go off on its own for a while before returning wit

by xd1936 8mo ago

I've also had the exact opposite experience with tone. Claude Code wants to build with me, and Codex wants to go off on its own for a while before returning with opinions.

mrkstu 8mo ago
Its likely that both are steering towards the middle from their current relative extremes and converging to nearly the same place.
- gervwyk 8mo ago
  also my experience in using these two models. they are trying to recover from oversteer perhaps.
mercnz 8mo ago
well with the recent delays i can easily find claude code going off on it's own for 20 minutes and have no idea what it's going to come back with. but one time it overflowed it's context on a simple question, and then used up the rest of my session window. in a way a lot of ai assistants have ime have this awkward thing where they complicate something in a non-visible and think about it for a long time burning up context before coming up with a summary based upon some misconception.
- esperent 8mo ago
  The key is a well defined task with strong guardrails. You can add these to your agents file over time or you can probably just find someone's online to copy the basics from. Any time you find it doing something you didn't expect or don't like, add guardrails to prevent that in future. Claude hooks are also useful here, along with the hookify plugin to create them for you based on the current conversation.
  - vorticalbox 8mo ago
    I have started using openspec for this. I find it works far better to have a proposal and a list of tasks the ai stays more focused. https://openspec.dev/ https://openspec.dev/
- zen4ttitude 8mo ago
  For complex tasks I ask ChatGPT or Grok to define context then I take it to Claude for accurate execution. I also created a complete pipeline to use locally and enrich with skills, agents, RAG, profiles. It is slower but very good. There is no magic, the richer the context window the more precise and contained the execution.
kamban 8mo ago
Same here, CC gives me options to pick direction after the planning stage.
PeterStuer 8mo ago
In terms of 'tone', I have been very impressed with Qwen-code-next over the last 2 days, especially as I have it running locally on a single modest 4090.
- turtle4 8mo ago
  Did you set that up following a guide or anything you could share?
  - mathrawka 8mo ago
    not OP, but I got it running on my 4090 (and RAM) by following this guide: https://unsloth.ai/docs/models/qwen3-coder-next https://unsloth.ai/docs/models/qwen3-coder-next I see around 30 t/s
  - PeterStuer 8mo ago
    Easiest way I know is to just use LMStudio. Just download and press play :). Optional, but recommended, increase the context length to 262144 if you have the DRAM available. It will definitely get slower as your interaction prolongs, but (at least for me) still tolerable speed.

by xd1936 8mo ago

I've also had the exact opposite experience with tone. Claude Code wants to build with me, and Codex wants to go off on its own for a while before returning with opinions.

mrkstu 8mo ago

Its likely that both are steering towards the middle from their current relative extremes and converging to nearly the same place.

gervwyk 8mo ago
also my experience in using these two models. they are trying to recover from oversteer perhaps.

mercnz 8mo ago

well with the recent delays i can easily find claude code going off on it's own for 20 minutes and have no idea what it's going to come back with. but one time it overflowed it's context on a simple question, and then used up the rest of my session window. in a way a lot of ai assistants have ime have this awkward thing where they complicate something in a non-visible and think about it for a long time burning up context before coming up with a summary based upon some misconception.

esperent 8mo ago
The key is a well defined task with strong guardrails. You can add these to your agents file over time or you can probably just find someone's online to copy the basics from. Any time you find it doing something you didn't expect or don't like, add guardrails to prevent that in future. Claude hooks are also useful here, along with the hookify plugin to create them for you based on the current conversation.
- vorticalbox 8mo ago
  I have started using openspec for this. I find it works far better to have a proposal and a list of tasks the ai stays more focused. https://openspec.dev/ https://openspec.dev/
zen4ttitude 8mo ago
For complex tasks I ask ChatGPT or Grok to define context then I take it to Claude for accurate execution. I also created a complete pipeline to use locally and enrich with skills, agents, RAG, profiles. It is slower but very good. There is no magic, the richer the context window the more precise and contained the execution.

kamban 8mo ago

Same here, CC gives me options to pick direction after the planning stage.

PeterStuer 8mo ago

In terms of 'tone', I have been very impressed with Qwen-code-next over the last 2 days, especially as I have it running locally on a single modest 4090.

turtle4 8mo ago
Did you set that up following a guide or anything you could share?
- mathrawka 8mo ago
  not OP, but I got it running on my 4090 (and RAM) by following this guide: https://unsloth.ai/docs/models/qwen3-coder-next https://unsloth.ai/docs/models/qwen3-coder-next I see around 30 t/s
- PeterStuer 8mo ago
  Easiest way I know is to just use LMStudio. Just download and press play :). Optional, but recommended, increase the context length to 262144 if you have the DRAM available. It will definitely get slower as your interaction prolongs, but (at least for me) still tolerable speed.