Rendered at 20:25:45 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
illithid0 19 minutes ago [-]
This was posted 38 minutes ago, and as of 20 minutes ago, several Anthropic services are now designated as having a "major outage".
Doubt these are related, but it made me laugh a little.
madihaa 48 minutes ago [-]
That's actually nice! I usually try to stay below 200k context anyway.
giancarlostoro 44 minutes ago [-]
For me the sweet spot is somewhere under 500k depending on how extensive I want to get. You can build up a sizable effort project in half a million tokens with Claude, with Claude having all the context from ground 0 to wherever you're off at.
cyanydeez 39 minutes ago [-]
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.
KronisLV 15 minutes ago [-]
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 and tests pass (including coverage requirements). You do need to poke it in a slightly different direction every few hours, though. Not even any novel work, just some refactoring and SSE notification hardening, bug fixes, alongside environment tuning and getting rid of some bottlenecks (also migrated from Oracle to PostgreSQL but that's mostly done).
That said, Kimi somehow manages to use less context in the main thread than Anthropic's models (even when you use sub-agents and also dynamic workflows in Claude Code), might have something to do with either how the model is tuned or their Kimi Code harness - because even in most of the longer form sessions it doesn't seem to fill up quite as quickly (note: because the kimi vis tool doesn't have a full summary view across all agents, these are the main long running agent stats across some sessions, not sub-agents):
I could see 256k context being sufficient for all sorts of work, even if intermediate progress/plan tracking files and docs might have to be used along the way, in addition to whatever plan support the harness has (for example, if you document something that will be relevant for load testing you might need that in 10 turns but not during the ones before then).
jdoe1337halo 18 minutes ago [-]
They are just talking to the model in CC, while staying in a single thread. Doubt they have any actual coding knowledge to compartmentalize different problems in the codebase.
giancarlostoro 3 minutes ago [-]
Depends on the programming language I'm using for a given project, and the domain I'm working with. I've been coding as a hobbyist for nearly two decades now (since my teens), professionally for 9 years, and was a TA before that for roughly 3 years at one of the best colleges for this field in the state (at least back then it was) where I taught other students about programming, in some cases I was their primary learning resource.
But yeah, I have no idea about anything about software because you made an assumption off very little to go by.
hawtads 41 minutes ago [-]
This is just an API level change right? The model itself should be the same I think.
dgritsko 33 minutes ago [-]
This isn't quantized, right? Just a smaller context?
DSingularity 23 minutes ago [-]
Its 256k context window. Quantization is orthogonal. We cant really tell directly so it could be quantized.
wxw 33 minutes ago [-]
> k3-256k is now available. Within 256k context, it delivers the same results. k3 (1M) consumes about twice as much quota as k3-256k.
lukan 20 minutes ago [-]
Since Claude is the first time for me really, really out (TIL against my wished about https://status.claude.com/), I am now interested enough to see what else works. But ... when I click pricing, I see "Join a waitlist". Wtf? Are they really that good, so were totally surprised and overwhelmed by the requests, is this a marketing stunt, or do they just don't have the hardware being in china?
KronisLV 9 minutes ago [-]
> Are they really that good,
They did exceed the expecations of pretty much everyone! I've also blogged about using the model, it's a bit on the slow side but pretty good!
> so were totally surprised and overwhelmed by the requests ... or do they just don't have the hardware being in china?
As a user, I much prefer that to service disruptions or severely degraded or secretly quantized performance. However if I didn't have an account, I'd be pretty pissed off about not being able to give them money and become a user.
Alifatisk 6 minutes ago [-]
No, the waiting list is true.
Kimi had become that popular. I was a subscriber of Kimi back when latest version was Kimi K2. Later I unsubscribed because I jumped over to GLM subscription (they had amazing deal). Now when I wanted to try out Kimi K3 to find out what the fuzz was all about, I couldn’t subscribe to them.
I remember reading a post from Moonshot team about this, they are doing this because they are almost at peak capacity and want to reserve it to keep the quality for their current customers.
We are actually witnessing an open-weight model catching up at catching mainstream users attention. And instead of behaving like Anthropic, they actually care about their users experience.
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.
InsideOutSanta 6 minutes ago [-]
It's an extremely popular model hosted by a company affected by hardware export bans. I doubt they'd voluntarily prevent people from subscribing if they didn't absolutely have to to maintain service quality.
sergiotapia 6 minutes ago [-]
I can't seem to find pricing for this model. Since the context size is just a quarter of the full size K3, is the price also much cheaper?
I usually keep my context in chats below 256k anyways so this would be tremendous honestly.
daemonologist 2 minutes ago [-]
It seems to only be available in Kimi Code, via subscription, no there's no API pricing. The linked page says it consumes about half as much quota as the 1M version though.
ibuildproducts 30 minutes ago [-]
omg! new model!!
Alifatisk 2 minutes ago [-]
Same model, new configuration
superloika 47 minutes ago [-]
The bells tolled today, but nobody came to church.
Doubt these are related, but it made me laugh a little.
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 and tests pass (including coverage requirements). You do need to poke it in a slightly different direction every few hours, though. Not even any novel work, just some refactoring and SSE notification hardening, bug fixes, alongside environment tuning and getting rid of some bottlenecks (also migrated from Oracle to PostgreSQL but that's mostly done).
That said, Kimi somehow manages to use less context in the main thread than Anthropic's models (even when you use sub-agents and also dynamic workflows in Claude Code), might have something to do with either how the model is tuned or their Kimi Code harness - because even in most of the longer form sessions it doesn't seem to fill up quite as quickly (note: because the kimi vis tool doesn't have a full summary view across all agents, these are the main long running agent stats across some sessions, not sub-agents):
I could see 256k context being sufficient for all sorts of work, even if intermediate progress/plan tracking files and docs might have to be used along the way, in addition to whatever plan support the harness has (for example, if you document something that will be relevant for load testing you might need that in 10 turns but not during the ones before then).But yeah, I have no idea about anything about software because you made an assumption off very little to go by.
They did exceed the expecations of pretty much everyone! I've also blogged about using the model, it's a bit on the slow side but pretty good!
> so were totally surprised and overwhelmed by the requests ... or do they just don't have the hardware being in china?
Yes, this is mostly the case: https://x.com/Kimi_Moonshot/status/2078855608565207130
As a user, I much prefer that to service disruptions or severely degraded or secretly quantized performance. However if I didn't have an account, I'd be pretty pissed off about not being able to give them money and become a user.
Kimi had become that popular. I was a subscriber of Kimi back when latest version was Kimi K2. Later I unsubscribed because I jumped over to GLM subscription (they had amazing deal). Now when I wanted to try out Kimi K3 to find out what the fuzz was all about, I couldn’t subscribe to them.
I remember reading a post from Moonshot team about this, they are doing this because they are almost at peak capacity and want to reserve it to keep the quality for their current customers.
We are actually witnessing an open-weight model catching up at catching mainstream users attention. And instead of behaving like Anthropic, they actually care about their users experience.
See Kimi Vendor Verifier.
I usually keep my context in chats below 256k anyways so this would be tremendous honestly.