I love the focus on cache hit efficiency. Hats off to the deekseek team for creating a great product that maximizes cost efficiency for the user.
> Hats off to the deekseek team for creating a great product I have been using it for a while, and I wholeheartedly agree. imo, it is as good as codex or claude which I also use. It is a winner in the cost-sensitive tier, and if some startup could put it together with data-retention in mind, it could be a great product sold to the enterprise, as data-retention and privacy are the main issues for the coding-assistant…
DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost
41–50 of 325 posts
Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost
#42Okay, I'm curious. From the FAQ, I see: >Can I point it at a self-hosted / private DeepSeek endpoint? >Yes. Since 0.30 we accept non-standard key prefixes for self-hosted DeepSeek endpoints. Just point `baseUrl` at your internal address — the loop, cache strategy, and tool protocol are unchanged. But my question is: If I use Reasonix to talk to a deepseek endpoint through openrouter, am I still getting the cache-hit…
Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost
#43Earlier quoted context omitted.
How can you have cache hit efficiency? Isn't it just a matter of not changing the previous context? I don't understand what knobs there are to tweak on this.
> Isn't it just a matter of not changing the previous context? Yes, but a lot of harnesses change previous context. E.g. the system prompt injects the current time/date, working directory, files in the working directory, etc. Compaction also changes the whole previous context. I _think_ changing the list of tools also invalidates cache, so invoking a subagent with different tools would invalidate the cache. My vague…
Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost
#44Earlier quoted context omitted.
Say you put the current time down to the second in the system prompt, which is the message that goes in front of the entire conversation, then basically nothing will be cached, every agent turn needs to ingest the entire session over and over. Contrast to not doing that, and the backend can leverage caching all the way up to the latest message, as nothing until then changed.
Surely other agent CLIs are not dumb enough to invalidate cache on every turn over something so obvious?
Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost
#45Not 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.
Agents or no agents, people still need to test their websites on different resolutions or at least window width, but seems this is becoming a lost art.
Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost
#46Earlier 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
Obviously, if you do deal with any sort of secrets, then using local LLMs over OpenAI, Anthropic, DeepSeek or whoever is obviously preferred, and in the case of personal data of users, probably a requirement.
Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost
#47Earlier quoted context omitted.
Say you put the current time down to the second in the system prompt, which is the message that goes in front of the entire conversation, then basically nothing will be cached, every agent turn needs to ingest the entire session over and over. Contrast to not doing that, and the backend can leverage caching all the way up to the latest message, as nothing until then changed.
Surely other agent CLIs are not dumb enough to invalidate cache on every turn over something so obvious?
Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost
#48I'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.
Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost
#49I'm concerned since i really want SOTA reasoning, but DeepSeek still has me interested.