I have a UI I developed from first principles about 10 years ago, I use it to replace my os, its like my personal do everything emacs os but not at all emacs, and its funny to see other Uis iteratively convergence on it as context finally gets its due.
Is there a link anywhere for a docs site for this? Really curious to know what "deep data sources" they have set up for the Native Global Market Data feature.
For the past 3 years, many software engineers were coping that AI (particularly LLMs) was only going after juniors. Given the documented history of mass layoffs related to AI from 2024 to today, it is clear that everyone including seniors and staff level folks are just as affected.
So let's just say, if your whole identity is for being a typical software engineer no matter the seniority and nothing else, perhaps it is time for you to reconsider options as of course 100% avoiding AI is futile at this point.
There will still be new jobs, but there will be no need for more excess people, even under Jevon's paradox. Software engineers were just the test bed for this and now there is an oversupply of SWEs without jobs in the market and will have to use AI tools like Kimi Work and Claude Cowork to be employable.
It rubs me the wrong way that they have to copy everything, the UI is almost exact copy of Codex. The entire mind set of just copy the best is holding them back.
I wish they had some kind of US hosted option, NDR policy, or something like that. I love the price and power, but I have concerns around data sovereignty and leaking IP to an overseas company.
kimi has been particularly shameless in copying codex 1:1, wow.
Like, I get it, before condex there was conductor and a ton of other guis but this looks like they just copied the code.
Also, their privacy disclosure is incredibly misleading:
> How does Kimi Work protect my privacy when accessing local files?
You have absolute control over your files. The built-in Ask before acting safeguard means Kimi will prompt you for explicit authorization before it modifies, overwrites, or runs code within your local directories. Nothing happens without your consent.
They fail to mention that is has unfettered read access to your files. ie, without your consent.
They all are pretty similar. And if it was copying anything, I would say more inspiration from claude desktop then codex. The Zcode is more like codex.
Looks like this can use webBridge, run Python and shell code in the background. Cowork can take over application UI as well which is still a differentiator (and a higher security risk) unless kimi offers it elsewhere.
It's a mistake to make this such an obvious copy. It will feed the narrative that Chinese entities cannot be trusted by the West. They could have varied it even slightly. It's one thing with hardware because customers don't need to trust suppliers any further than they can throw the box. But these labs seem to be battling for enterprise knowledge work-share. Trust is paramount, and they're already behind on that front. Own goal.
Though it's ever so slightly broken (the sub-agent tracking stop button does nothing, some toggles in the Settings are not toggleable and so on, really slows down with long conversations to the point where keyboard input lags by seconds, think 600+ turns).
Personally, I still liked ZCode better and will probably write a blog post about my experience with K3 too, the harness might need some more work, but the model is really, really good.
> Kimi Work is a Local Agent designed for deep workflows. It mounts your local folders, navigates the web autonomously via WebBridge, runs Python code in the background, and executes scheduled tasks.
It's clearly a dupe of Claude/Codex products (Codex especially, styling-wise), but I think Kimi's goal here is simply to appear on feature-parity with bigger labs. I doubt they'd want to invest much into designing a UI for "the future of agentic work" from the ground up.
Their bread and butter and claim-to-fame will continue to be low-cost, near-frontier models, for which they need to at least appear to have some app layer to plug into.
And, in some ways, duping is a great way to show people that even the app layer can be commoditized.
I want to believe I work on something creative in this space (even though, the current UI was never "meant to be" and (d?)evolved from a substrate of cheaply available UI components and laziness). THen again, much of the unorthodoxy actually comes from all the small(and big) usability nightmares that I can not bring myself to tolerate while working in a desktop environment(so, created new ones - like bitmap-based context trees ;)
60 comments
[ 0.25 ms ] story [ 13.3 ms ] threadAlso this was released about a month ago
https://tech.yahoo.com/ai/meta-ai/articles/moonshot-ais-kimi...
Hoping to find something on a creek with a Mountain View and fairly remote.
So let's just say, if your whole identity is for being a typical software engineer no matter the seniority and nothing else, perhaps it is time for you to reconsider options as of course 100% avoiding AI is futile at this point.
There will still be new jobs, but there will be no need for more excess people, even under Jevon's paradox. Software engineers were just the test bed for this and now there is an oversupply of SWEs without jobs in the market and will have to use AI tools like Kimi Work and Claude Cowork to be employable.
What could go wrong?
Like, I get it, before condex there was conductor and a ton of other guis but this looks like they just copied the code.
Also, their privacy disclosure is incredibly misleading:
> How does Kimi Work protect my privacy when accessing local files? You have absolute control over your files. The built-in Ask before acting safeguard means Kimi will prompt you for explicit authorization before it modifies, overwrites, or runs code within your local directories. Nothing happens without your consent.
They fail to mention that is has unfettered read access to your files. ie, without your consent.
https://drive.google.com/file/d/1JFfgfMO0nO7HR0WHwEqEEjXIIQj...
And it is above the fold in their hero image!
Guess where the models are gonna be hosted? Hint, not China.
There's really no real reason for those tools to be separate and for them not to give me something a bit nicer than just a TUI in the terminal.
They already have a locally runnable web UI when you have Kimi (the CLI) installed: https://www.kimi.com/help/kimi-code/cli-getting-started
Though it's ever so slightly broken (the sub-agent tracking stop button does nothing, some toggles in the Settings are not toggleable and so on, really slows down with long conversations to the point where keyboard input lags by seconds, think 600+ turns).Personally, I still liked ZCode better and will probably write a blog post about my experience with K3 too, the harness might need some more work, but the model is really, really good.
It's clearly a dupe of Claude/Codex products (Codex especially, styling-wise), but I think Kimi's goal here is simply to appear on feature-parity with bigger labs. I doubt they'd want to invest much into designing a UI for "the future of agentic work" from the ground up.
Their bread and butter and claim-to-fame will continue to be low-cost, near-frontier models, for which they need to at least appear to have some app layer to plug into.
And, in some ways, duping is a great way to show people that even the app layer can be commoditized.