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

Kimi Work

kimi.com

Post reply on HN
Print view View original

271–280 of 305 posts

Re: Kimi Work

#271

Post by gf000 »

WhyNotHugo wrote: post #182
ajross wrote: post #141

Earlier quoted context omitted.

> the last 20 or so years of US/Chinese economic competition Only with some industries, mostly electronics and light manufacturing. The rest of the history of software products doesn't look like this at all. China cloned Amazon and Meta fairly well (but only within their local/captured markets) but not Microsoft or Google and absolutely not Apple. Entertainment and culture exports are still effectively zero (like, wh…

> Entertainment and culture exports are still effectively zero (like, what, three blockbuster films?) where the US, Japan and Korea define pop across the globe. And this is really sad, because they have thousands of years of cultural heritage and also plenty of great films. Somehow, they've failed at exporting this completely.

Well, another way to put it is that the western markets managed to keep it out via propaganda and other soft influences on people.

Re: Kimi Work

#272

Post by gf000 »

jascha_eng wrote: post #173
CookieCrisp wrote: post #160

Earlier quoted context omitted.

I highly recommend to anyone that uses them a lot - try to clone your own. I’ve got mine fully formed into how I want it, with features I haven’t seen anywhere else yet and with integration into everything I work with. We’ve lived in a world where every app had to fit enough people well enough - but now we live in a world where an app can be molded to be absolutely perfect for just you!

How did you build your own coding agent? What language/framework did you use?

Not the parent commenter, but most of it is surprisingly simple. You basically start with a "chat app" where you have a list of messages, send the whole conversation to an LLM and it replies back, which also gets added to the same list.

And you add a small twist, that instead of a 1-to-1 back and forth, you instead put it into a loop, where the LLM reply can itself "have a turn", e.g. a tool invocation, where your system is the one that replies (e.g. with the tool invocation's result). That's pretty much it, you have a 1 to potentially many "chat".

The harder part is getting all the "soft" parts right, like how to have well-behaving tool calls, timeouts, prevent huge cycles eating up tokens, but there are no one way to solve these, it's a fundamentally heuristic-heavy area.

Re: Kimi Work

#273

Post by [deleted] »

abdullahkhalids wrote: post #127
postalcoder wrote: post #31

Earlier quoted context omitted.

Yes, but the answer is an indirection. “How does Kimi Work protect my privacy when accessing local files?” It doesn’t protect your privacy. It’s like asking, “how do I know you’re not spying on me?” And getting the reply “we cannot physically enter your house.”

"How does Kimi Work protect my privacy" can be interpreted in two ways. The first is "How does Kimi Work protect my privacy from Moonshot?" They did not answer this question. The second is "How does Kimi Work protect my privacy from other third parties?" They are answering this question by saying, we won't upload your files to some third party server without your consent.

[deleted]

Re: Kimi Work

#274

Post by JSR_FDED »

jmacd wrote: post #269

Everyone calling this a copy is willfully overlooking that the major labs are nakedly copying each other AND smaller vendors constantly. Codex and Claude Code didn't just materialize at the same time. And frankly, they both copied Aider in the beginning. Then there is reasoning itself. Agent SDKs. On and on. This isn't a game of hide and seek. It's a race. The fact that Kimi is Chinese doesn't make their stride any m…

To me all these coding tools look indistinguishable from each other. If you changed the logo on one I wouldn’t notice.

Re: Kimi Work

#276

Post by OutOfHere »

PunchTornado wrote: post #248
OutOfHere wrote: post #169

Earlier quoted context omitted.

American labs will do fine with monthly subscriptions costing $20-300/month. They will not do fine for heavy basic LLM API calls -- it is for this that the cheap API produces substantial savings. Specialized niche provisions, e.g. excellent tool use, reliable structured output, reliable long context, cached and uncached web search, document reads, computer use, integrations, etc. also will take time for the foreign s…

you are not a trillion company if you just get 20$ a month. if that's the case, the valuation will drop 10x

I did note $20-300. In particular, domestic employers would surely still spend the upper end of it for each of their engineer staff. If there are 4 million software developers in the US of any job title, and if the employer of each spends $200 per month for the developer, that's $800M per month in revenue.

Re: Kimi Work

#277

Post by taytus »

wasfgwp wrote: post #224
crystal_revenge wrote: post #180

Earlier quoted context omitted.

This comment is a great example of how large and strange the skills gap in AI is right now. Curious why your first impulse is not simply to point your favorite agent at a few examples and start brainstorming/planning from there? Multiple times I’ve built a purpose specific bespoke tool starting this way. In fact, it’s a great way to learn how specialized tools are built.

Presumably people want to hear the opinions of other people and still believe that they might learn more from the their experience than by exclusively interacting with AI models? The alternative of that first impulse should be what exactly? Telling AI to research Medium AI drivel articles (since nobody seems to be posting long/medium form content anywhere else these days) to figure out what’s the best approach to bui…

This was my first thought as well. I can read online review about a product but I rather ask my friends their experience with it. Same thing here.

Re: Kimi Work

#278

Post by deepvibrations »

OutOfHere wrote: post #276
PunchTornado wrote: post #248

Earlier quoted context omitted.

you are not a trillion company if you just get 20$ a month. if that's the case, the valuation will drop 10x

I did note $20-300. In particular, domestic employers would surely still spend the upper end of it for each of their engineer staff. If there are 4 million software developers in the US of any job title, and if the employer of each spends $200 per month for the developer, that's $800M per month in revenue.

[dead]

Re: Kimi Work

#279

Post by preg_match »

gruez wrote: post #29
postalcoder wrote: post #25

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…

>They fail to mention that is has unfettered read access to your files. Isn't that totally expected of a coding agent? Otherwise it's like complaining dropbox "has unfettered access to your files".

This is why I run CC under podman.

Re: Kimi Work

#280

Post by mh- »

cadamsdotcom wrote: post #209
wxw wrote: post #80

> 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 f…

Some paradigms are simply ergonomic. Sometimes there's only one UX people will accept. No one would buy a car steered with pedals; even if that is better (hey planes do it!) - every car maker is "copying" steering wheels and putting them on their cars. Is it controversial? If not why not?

It wasn't controversial because there was about 200 years of prior art from sailing ships.

(Before the wheel, ships were steered with tillers - which early cars also tried, interface-wise.)

Post reply on HN