Live data from Hacker News

Kimi Work

kimi.com

241–250 of 305 posts

Re: Kimi Work

#241
post #109

Earlier quoted context omitted.

This is false. Apple’s UI/UX is the reason why they are adored from a physical attraction perspective.

Apple UI/UX sucks though, but all the other alternatives also suck.

BeOS didn't suck. It's UX stood out and was utilitarian.

Re: Kimi Work

#244
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…

Copying and reinterpreting/reimplementing successful technologies and processes is the bedrock of human civilization

Re: Kimi Work

#245
post #221

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!

Out of curiosity, what are your favourite features that are unique to your implementation?

Not parent, but favorite feature of my own harness I haven't seen somewhere else, is the ability for the agent to execute code on different hosts in a transparent and easy way. Fairly simple and probably could prompt the agent + set things up with ssh, but was doing other stuff related to a serverclient model, so figured why not add it as a couple of tools. Now the agent can build cross-platform applications while I'm mostly on Linux and actually verify it works, without me manually switching between three OSes.

Re: Kimi Work

#246

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.

The problem of the sota models clamping down on third party harnesses should be stated upfront. Getting a SOTA model in a custom harness requires API pricing or risking an account ban, correct? This preliminary change in cost may not make it worth it for people depending on which is their "favorite agent". Especially as the default harnesses for said agents continue to improve...

> The problem of the sota models clamping down on third party harnesses should be stated upfront. Getting a SOTA model in a custom harness requires API pricing or risking an account ban, correct?

The opposite, how easy it is nowadays should be clarified. Codex's app-server quite literally is built to be integrated with, authentication is a breeze and it's quite stable, compared to the TUIs that are around.

It's a real shame Codex is moving in the direction of hiding stuff on local disks from users, hopefully they're revert the decision of encrypting the agent>sub-agent prompts so we get back introspection again...

Re: Kimi Work

#247
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…

weird to all it a dupe, these are new paradigms, it's like saying BMW duped Mercedes Benz cause they both make stuff on 4 wheels

Re: Kimi Work

#248
post #97

Earlier quoted context omitted.

Yup they have a cost advantage. They just need to be good enough and just copy. Sorry american labs - it’s the beginning of the end.

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

Re: Kimi Work

#249
post #221

Earlier quoted context omitted.

Out of curiosity, what are your favourite features that are unique to your implementation?

Not parent, but favorite feature of my own harness I haven't seen somewhere else, is the ability for the agent to execute code on different hosts in a transparent and easy way. Fairly simple and probably could prompt the agent + set things up with ssh, but was doing other stuff related to a server client model, so figured why not add it as a couple of tools. Now the agent can build cross-platform applications while I…

When I tell Claude or open code using Kimi or codex to fix something on my raspberry pi, they all go to ssh right away.

I found that most things that are “features” in harnesses and tools that don’t relate to UI and UX in those harnesses themselves can be done through skills or just prompts.

A nice features of Claude’s is the remote control through the mobile app. That isn’t just a skill.

Post reply on HN