Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost

esengine.github.io

Post reply on HN
Print view View original

141–150 of 325 posts

Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost

#141

Post by bobkb »

metalspot wrote: post #127
3uler wrote: post #31

Earlier quoted context omitted.

Opencode has really bad cache stability issues that they seem uninterested in fixing at the moment.

I am getting 98.6% cache hit ratio on deepseek-v4-flash with opencode

That’s impressive!

On the sheer performance it’s comparable to Opus ?

Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost

#142

Post by adi_kurian »

There is an uncanny valley effect to websites where FE is created in full via an AI.

These sites have the immediate scent of 'high design', with errors that no 'high designer' would dare make.

The italics give me nausea. Text promoted with orange fill is seemingly random. There is no thought behind the combination of art and copy. Random smattering of Title Case and Sentence case and lower case. A lack of commitment to a full stop Widowed H1s. H1s with random spaces .

At the same time, if I hammer CMD - to 25%, it looks fancy. Perhaps nobody gives a fuck.

That said, I'm excited to try this tool!

Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost

#143

Post by gopher_space »

franknord23 wrote: post #111
criemen wrote: post #74

Earlier quoted context omitted.

> Ah, reminds me of good old "There are only 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors." You quip, but LLM KV caching (from the harness side) is quite easy: You get a cache hit on stable prompt prefixes, period. That means you want to keep the prefix stable, and only append at the end of the conversation. Made up example: Don't put the git branch name into the system…

That sounds like the experience of writing Containerfiles; since steps are cached you want to pull the thing you are iterating on as far down as possible.

All of this work has been done before in different contexts. Memory management with bigger blocks and weaker definitions that change whenever some grad student gets a bright idea.

Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost

#145

Post by peheje »

peheje wrote: post #144
imagetic wrote: post #75

https://shittycodingagent.ai

having issues with truncated output from deepseek v4 pro through openrouter via pi-harness on ptyxis-terminal using ubuntu trying reasonix with direct api..

first impression: the tui flickers a lot, unpleasent. very laggy to write in.

Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost

#147

Post by soerxpso »

dathery wrote: post #87
3uler wrote: post #31

Earlier quoted context omitted.

Opencode has really bad cache stability issues that they seem uninterested in fixing at the moment.

The OpenCode devs talk about this on Twitter a lot, e.g. https://xcancel.com/thdxr/status/2048268697790300343 > 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 hi…

My understanding of caching with most models/providers is that a prefix substring of the context has to be reused for a cache hit, but not necessarily the whole entire context window. So if you prune tool calls from the history, you're going to get one cache miss on the newly-pruned history, and then you're going to be getting cache hits on every subsequent turn, with a lower number of input tokens. If you prune subsequent tool calls after that, you would still get a cache hit for the already-pruned portion of the context, just not the full context.

Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost

#148

Post by upcoming-sesame »

metalspot wrote: post #127
3uler wrote: post #31

Earlier quoted context omitted.

Opencode has really bad cache stability issues that they seem uninterested in fixing at the moment.

I am getting 98.6% cache hit ratio on deepseek-v4-flash with opencode

out of curiosity, how do you measure cache hit rate in opencode ?

Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost

#149

Post by locknitpicker »

agrippanux wrote: post #123

This website seems to have been generated by Codex - I asked Codex to create an HTML overview of a feature for my team and it made an overly produced monstrosity - complete with the same large stat boxes that were for the most part devoid of meaningful information - using the same font, colors, layout, hero section, etc. It was also terrible on mobile just like this is. In the end I had Claude produce a one-page html…

> In the end I had Claude produce a one-page html file that was 95% of the way there and it took minor editing to clearly explain the intent of the feature.

That doesn't say much about any model though. For starters, any software engineer can tell you that leaving out features can drastically simplify any project.

Re: DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost

#150

Post by andai »

Alifatisk wrote: post #95
andai wrote: post #93

But Claude made the website?

What conclusion are you drawing from that?

If Deepseek can't even make a static site, why would I want to use it for anything else? (Not saying it can't, just that it's a weird choice to present your Deepseek-oriented product.)
Post reply on HN