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

Kimi K3-256k

kimi.com

Post reply on HN
Print view View original

91–100 of 172 posts

Re: Kimi K3-256k

#91

Post by KronisLV »

bkaae wrote: post #27
KronisLV wrote: post #14

Earlier quoted context omitted.

My current Claude Code session has been going on for like 35 hours and has used up around 400 million tokens, thankfully almost all of those being cached (95-98%) - pretty typical for long form agentic work. First you spend like 2-3 hours working on a plan, once you have that you just tell the model to go and implement it, do adversarial sub-agent review loops before each commit and also make sure that all tooling an…

Thanks for sharing - is this a normal feature request you are implementing in this example or is this a project from scratch? Trying to get an idea of how your workflow compares to mine.

Existing project and as usual, a few issues mashed together in one mostly coherent plan. The shorter Kimi sessions I mentioned were singular features, there 256k would be wholly adequate.

A greenfield project would probably allow at least 2x fewer tokens to be used in most of those long tasks, but I was mostly after consistency and bug fixes along the way as needed.

Re: Kimi K3-256k

#92

Post by vidarh »

DelightOne wrote: post #80
vidarh wrote: post #71

Earlier quoted context omitted.

Kimi CLI has a mechanism with checkpoints and the ability for the agent to revert to a checkpoint + a message of how to continue based on what went right/wrong. I don't know if that's the cause of what you've seen, but it's plausible.

With prefix caching, you get checkpoints for free. Do you mean that?

No. Prefix caching is just an optimisation on the server side. What Kimi CLI does is insert tags that include a checkpoint marker with an id.

The model is then given a tool that allows the model to decide to roll back to a checkpoint + a message containing any additional useful information.

It's specifically instructed to use that tool[1] in cases like when it has inadvertendly read a large file where most of the content is not relevant to the task, or after a web search where it's found what it's looking for but most of the content isn't needed, or when it's written code that didn't work as expected, or similar.

It basically lets the model backtrack and "forget" irrelevant details at the end of the context but give itself hints on how it should continue from the checkpoint.

Though, interestingly they seem to be abandoning it in their new CLI (kimi-code), unless it's been folded into other functionality. Not sure if they just feel it's not needed any more with their newer models or if it just didn't work as well as they expected.

[1] named "D-Mail", or "DeLorean Mail" in a reference to Steins;Gate, which again references Back To The Future. See https://github.com/MoonshotAI/kimi-cli/blob/main/src/kimi_cl... and https://steins-gate.fandom.com/wiki/D-Mail

Re: Kimi K3-256k

#94

Post by 1saadcodes »

It feels like we're moving away from "bigger context is always better" toward "right-sized context". I love this not just because my wallet feels safer but because most of my coding sessions never come close to needing 1M tokens anyway

Re: Kimi K3-256k

#96

Post by yeswecatan »

nvarsj wrote: post #73
okrad wrote: post #61

Earlier quoted context omitted.

I believe Codex harness is pretty sticky though I haven’t tried many others. Does anyone else provide a harness of that quality?

Pi harness with subagents is pretty great. I’m using it for everything now.

How are you handling subagents?

Re: Kimi K3-256k

#97

Post by altern8 »

Permit wrote: post #82
chipgap98 wrote: post #64

Earlier quoted context omitted.

This exact same comment is the top comment on the reddit thread for this news https://www.reddit.com/r/kimi/s/BFa1TR9vNg

I searched one other comment of theirs in their history and see the same thing. On mobile so I can’t easily tell if this account is the bot account or if the ones on Reddit are. HN: https://news.ycombinator.com/item?id=47934437 Reddit: https://www.reddit.com/r/worldnews/comments/1sxzzop/comment/...

Karma-farming bot..?

Re: Kimi K3-256k

#100

Post by Tostino »

timcobb wrote: post #88

Codex uses 256k masterfully, 1M is luxurious but still quite expensive and seems not necessary as a default.

I'll have to give it a shot some time soon. I just can't imagine working on any of my serious projects doing a new large feature with that little room. By the time it has looked at half the code required to start planning the work, it'd be out of context. Must use sub agents better or something.
Post reply on HN