This Claude front end skill is now soon to be slop.
DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost
81–90 of 325 posts
Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost
#82I specifically use multiple different models and providers, so this wouldn't be useful for me.
And it contributes to the problem of each person vibe-coding their own, incompatible, half-baked tool in a space, instead of contributing to a small set of tools and expanding them.
It'd be better to just extend an existing tool.
Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost
#83Earlier quoted context omitted.
> I wrote a tiny little bridge so I could use DeepSeek V4 Pro via Codex Can you share the bridge. DeepSeek v4 is awesome paired with claude-code or opencode. I found that claude code costs me less than opencode and I am presuming this is due to a better engineered harness.
I’m feeling more a novice every day, but how isn’t this just handing over your code to team deepseek for whatever they might want
Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost
#84Earlier quoted context omitted.
That'd be really easy to spot and also fix, most likely. Any open issue you could point us to, must surely been reported already?
Opencode (and other coding agents) have hundreds of open issues reported. It is quite discouraging when they are not being closed/fixed.
Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost
#85It's pretty funny, i'm a $200/m Claude subscriber and i've had little need to use anything else. However the more Claude has been restricting my workflow (notably around the recent IDE/-p usage change) the more i've been wanting to go elsehwere. I'm concerned since i really want SOTA reasoning, but DeepSeek still has me interested.
Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost
#86Not a fan of that page. The animated typing and resulting continuous resize of the example keeps moving the content beneath it down and up. Such bad UX.
Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost
#87I'm not sure you need a "DeepSeek native coding agent" to take advantage of DeepSeeks cache, yesterday as the Codex quota usage issue still wasn't solved for me, I wrote a tiny little bridge so I could use DeepSeek V4 Pro via Codex, and seems most of everything I did was basically cached as far as I can tell: https://i.imgur.com/7eKn6wN.png (2026-05-23 Input (Cache hit): 39,123,200 tokens, Input (Cache miss) 1,692,28…
Opencode has really bad cache stability issues that they seem uninterested in fixing at the moment.
> tool call pruning breaks cache and people will tell you this is horrible and expensive
> except i looked at some anthropic data and real user behavior ends up with better cache hits and 30% less spend
> even this is needs to be analyzed further, it's just not simple
> for openai data it's inverted! cache hit ratio is actually better [sic: I think he meant worse based on the screenshot] with tool call pruning turned on
> but the net $ saved is only 5%
> kimi is a funny one - it has better cache hits with pruning on...but is also more expensive!
There was also another thread recently where he discussed that pruning improves user experience (models are smarter with less context) but I can't find it.
This can also be disabled in the config: https://opencode.ai/docs/config/#compaction
Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost
#88Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost
#89High caching rates for coding agents can drastically reduce latency and API costs. I am curious to see how the caching strategy handles context invalidation across multiple files.
Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost
#90"Independent open-source project · not affiliated with DeepSeek" "Reasonix only targets DeepSeek because..." "Why DeepSeek only? Can I swap to Claude / GPT? It's a design choice, not a limitation"
The lady doth protest too much, methinks?
Nicely timed shortly after the making the rebate permanent anouncement.
Could just be Chinese devs trying to help western devs with some software and a western facing marketing campaign to raise awareness. Could be DeepSeek astroturfing. Could be "someone" in China trying to get more access to western data.
Who knows?