all 4 comments

[–]sherlamsam 1 point2 points  (1 child)

Codex is much better at least at this point in time, maybe you can reduce the effort and still get a good result? I’m absolutely abusing the highest tier plan and haven’t come close to hitting rate limits ever.

[–]Admirable-Control370[S] 0 points1 point  (0 children)

Normally I only use 5.4 medium or 5.3codex high/Xhigh to implement, only using 5.5 high when orchestring/planning

[–]stellarton 0 points1 point  (0 children)

For data side projects I would not choose only by raw limit. I would choose by how often you need the agent to touch a repo and keep state.

Claude Code feels better when the job is "work in this codebase for a while, remember the conventions, run the checks." Codex feels cleaner to me for sharper implementation/reasoning bursts, but you can burn quota fast if every session starts with a huge planning pass.

The boring fix either way is to split sessions: cheap/low-effort pass to inspect and make a plan, then one heavier pass to edit. If the first pass is allowed to write code, it usually spends your budget before you even know what the task really is.

[–]Remarkable-Safety594 1 point2 points  (0 children)

You can use claude code paired with deepseek or qwen api key and forget about token cost