Live data from Hacker News

Kimi K3-256k

kimi.com

61–70 of 172 posts

Re: Kimi K3-256k

#61

LLMs is quickly became commodities. US AI labs like OpenAI is losing their moat. Hyperscalers and data center owners who can sell cheap token will win

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

Re: Kimi K3-256k

#63

A bit of topic. But how likely is it that the US will restrict Chinese open weight models and also force Euro countries to do the same? I think it will be effective within 6 months. The US is having a hard time staying competitive.

It isn't legally possible for them to do this at the EU level. The EU parliament would never vote for it. For pressure at the country level leading to this kind of thing I think it's very unlikely. Here in Sweden it wouldn't just require a vote in the Swedish parliament and before this there'd have to be förarbeten and you can't just brazenly push things through with insane arguments, Swedish social convention goes a…

It happened with ASML. What's your thought on it? The US forbid dutch company to export.

Re: Kimi K3-256k

#65
post #15

Earlier quoted context omitted.

Since the model is open-weights, you can get from other providers, for example see https://openrouter.ai/moonshotai/kimi-k3#providers

The only downside with third party providers is that you have to trust that the provider have setup and configured it correctly, and is not secretly quantizing it. See Kimi Vendor Verifier.

[deleted]

Re: Kimi K3-256k

#66

Earlier quoted context omitted.

I'm always curious what you guys are working on; every git repo I've run a local model on and stick below <100k to increase speed seems effective enough to scope patches and changes.

Try doing a refactoring of some sort or larger new feature using just an agent on a moderately sized codebase, 256k will be compacting every few minutes, and result will be unusable.

I do essentially all of my work with auto compact set to 250k and it's fine. It may be due to the way the project tooling is set up and the use of sub agents?

Re: Kimi K3-256k

#67

Wow. So kimi is suddenly half the price for all users until they hit 256k of context? Thats massive.

I don't think so. This is a separate model, so I assume that if you just use this and switch to the 1 million context model when you reach 256k, your cache will be invalidated, so you'll re-pay the 256k tokens on the 1 million context model pricing.

Edit: I was wrong, thanks to longwave for pointing this out. It's absolutely possible to start out on the 256k model and then switch to the 1 million model when you get close to the context limit without invalidating the cache:

"When switching from k3-256k to k3 (1M), if k3-256k is close to the 256k limit and you don't want compact to lose information, you can switch directly to 1M. The current version switching from 256k to 1M does not affect the cache."

Re: Kimi K3-256k

#69

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…

Once you have the plan you don't need to keep the 2hrs of research in the context (which is most of it) you can drop that plan into a file and start fresh for implementation.

That is true, but I feel like sometimes if the conversation contains useful rational it can help to keep it. I think sometimes it is a judgement call, I will sometimes compress the context first.

If I feel like the model and I explored a lot of options I won't want to keep context as it might be confusing.

I think the more you use it the better judge you are of whether you should purge, compress, or just keep the context before executing the plan.

Re: Kimi K3-256k

#70
post #61

LLMs is quickly became commodities. US AI labs like OpenAI is losing their moat. Hyperscalers and data center owners who can sell cheap token will win

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

Their harness is indeed nice, but we're using it against our own AI Gateway at work. Right now we only expose GPT models on it, but I imagine it's possible to add our own models eventually
Post reply on HN