CommandCode

“We ran a study with like 70 plus developers in the number of times that they had to go edit files because their LLM made a different, you know, the scene took a different turn, or steer their LLM like, yeah, don't do this, don't use this, don't use TRPC or som…”

“What we saw is the moment you send the result with the repair logic, right after that, the third tool call is fixed. Instead of, you know, it all of a sudden becomes super smart. It understands like, okay, I got the result, what I was looking for, and I'm gonn…”

“But they will only be for deep seek when to 3.7 max is the second most used model on command code right now. It's just two or three days old.”

“A lot of people, what they're doing is they're building one project with a really high quality LLM, like Opus or GPT, 5.5, right? They're building a taste file, and then they're using, you know, super cheap models to continuously build on that more.”

“So we are going to open source command code very, very soon. I'm hoping we can announce that on the AI engineering conference, NSF.”

“There's only one type of agent, and that is a coding agent. It can do it all, right?”

“We launched a Go plan with just dollar one per month to, where you can do like, six hundred million tokens of DeepSQL for Pro in it, just to prove like, open models are actually really, really good, and they are catching up, right?”

“And now we have like 16,000 different repair, you know, variations across hundreds of billions of tokens. We are doing anywhere from six hundred billion tokens right now.”

“Matt is actually one of our angels now. When he heard that we are open sourcing command code, he reached out.”