Earlier quoted context omitted.
Aren’t there all chat interfaces? Same goes for Claude Work, ChatGPT Work, etc
That's precisely the problem. People are building UI/UX for a paradigm that is so utterly new that they miss the mark entirely. Everyone defaults to a big chat input because that's all they know. It's the expectation, so it's safer, faster, and cheaper to not deviate. It's also wrong and bad for work.
Kimi Work
51–60 of 305 posts
Re: Kimi Work
#52Re: Kimi Work
#53Earlier quoted context omitted.
>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".
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.”
In light of the recent grok build snafu, "Nothing happens without your consent" seems like an upgrade. Moreover what are they supposed to do here? By that logic should any sort of non e2e email/storage provider not be able to put "How does [product] protect my privacy" in their faq?
Looking through their privacy policy, it looks like the bigger issue is that they are (or refuse to refute) training on your data/prompts. That's probably what people should be complaining about rather than complaining about how it "has unfettered access to your files", when that describes all coding harnesses.
Re: Kimi Work
#54Re: Kimi Work
#55Re: Kimi Work
#56Earlier quoted context omitted.
>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".
The repo you’re working on, sure. But all files?
Yes, any tool, including any coding agent, has access to all files $USER has access to.
Sandbox it explicitly to give access to only the current directory - https://github.com/ashishb/amazing-sandbox
Re: Kimi Work
#57Guess where the models are gonna be hosted? Hint, not China.
Re: Kimi Work
#58I 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.
It'll most likely land on Bedrock when the K3 weights are released.
Re: Kimi Work
#59Earlier quoted context omitted.
if your model ever touches bash, it has unfettered acess to all your files.
Not if the harness applies an OS-level sandbox to the process, as Codex does. https://learn.chatgpt.com/docs/sandboxing?surface=cli