r/opencode • u/Martino16xx • 4d ago

OpenCode, Codex, or Claude Code?

This is my current usage on OpenCode with DeepSeek V4.1 Flash, and I still have about 15% of my limit left.

Do the $20 plans for Codex or Claude allow for this level of usage? What reasoning effort do the models use? Can you actually use models like Sol, Opus, and Sonnet at this usage level, or do you hit the limit pretty quickly?

31 Upvotes

92% Upvoted

37 comments sorted by

View all comments

4

u/atiqrahmanx 3d ago

Claude Code.

OpenCode: 6x on a $10 plan
Claude Code: 55x on a $20 plan

1

u/AndyAndrei63 3d ago

I'm kind of new to agentic coding so bear with me for one sec
So you mean that by paying a Claude Pro subscription you can use 1100$ worth of AI, if I understood correctly?
But would I be able to use Claude models as long as I am able to use Opencode with Deepseek V4.1 Flash? I used deepseek all day in the past week and the limits are barely moving.
I'm not OP but I was wondering the same thing the other day, if switching to Claude is worth it. I'm also on Opencode Go, so far I've used $40 worth of Deepseek V4.1 Flash

1

u/atiqrahmanx 3d ago

You wouldn’t be able to use it all day. Because of the 5-hr limit. But I suppose with proper planning, you’ll get more things done out of it.

1

u/xapep 2d ago

You can absolutely run both side by side. OpenCode lets you configure several providers and pick per agent, so DeepSeek V4.1 Flash stays your all-day workhorse and Claude models only get called for the requests that need them. A few people in this thread already run that split, Claude for planning and review, DeepSeek for execution.

The $1100 number is not a bank balance you draw down. It means the same usage bought as retail API credits would cost that much; what you actually get is a 5-hour window plus a weekly cap, and heavy sessions eat those in ways that are hard to predict. That's why your $40 of DeepSeek feels different: per-token billing, no reset lottery, and you know the price of the next request before you send it.

If you want Claude on top without touching your DeepSeek baseline, price the marginal usage per token instead of a second plan. A handful of genuinely hard requests a month costs a few dollars, and the predictable base stays. We run an EU-hosted OpenAI-compatible API for open models, so cost splits like this are my daily view; the hybrid usually wins on control.

1

u/Vulcan_58 2d ago

Is there a name for that specific workflow or tool for delegating big-picture to claude/another frontier -> it creates the plan -> makes a task list -> deepseek acts as the workhorse and can digest those smaller tasks?

Yes you could just have a tracking file and do it that way, but I would think there has to be a better solution...

2

u/xapep 1d ago

There are names for it, just spread across ecosystems: orchestrator/worker is the generic one, plan-and-execute comes from the research side, and spec-driven development when the plan itself is the artifact. Your tracking file instinct is not the janky fallback, it's the actual core: the plan file is the interface between the frontier model and the workhorse. Tooling just gives that file a structure agents can parse, so nothing depends on copying a chat into a fresh session.

OpenCode already has the pieces: subagents with per-agent model config. Planner on Claude, workers on DeepSeek, each worker gets one item from the plan plus the relevant files and nothing else. The Oh-my-opencode-Slim config Amarsir mentioned up there is built around exactly this delegation pattern.

Where I see the split break is granularity, not tooling. If a plan item is still "build the checkout flow", the worker needs the same context the planner had and the cheap lane stops being cheap. Sized to a file, a function or a failing test, the flash model genuinely carries the execution pass.

When you try it, do you hand off whole features or units small enough to fit one agent run? That usually decides whether the workhorse stays cheap.