Each provided an identity in the first turn, something that they won't do as readily if asked in plain English, and in each case the answer matched the model ID as disclosed by arena.ai after voting -- except in cases where the model ID was a masked/hidden one and then I just had to take it on faith that the model was what it said. (I didn't have much to vote on, but I ended up voting for the answers I felt provided the style, content, and length I was expecting.)

I'm still looking through your docs, but I'm curious how e.g., you'd prevent my job you run on your idle agent from contaminating your agent's memory or history, or in the opposite direction how you'd guarantee that your idle agent's memory or skills or system prompts or whatever aren't corrupting or impacting my job?

(Edit: future is only spelled with one f)

Keep your hands on the wheel, y'all. :-(

Homepage is cool too.

Oh, for the simpler days when not everything required an app.

-- https://about.fb.com/news/2026/09/introducing-muse-personal-...

I'm sure there are other examples of repos that move this quickly out there, but I guess this is the first one that I've become aware of. On one hand it feels good that opensource software gets this much attention; on the other hand it seems like it must (at times) feel like a Sisyphean task to keep up both on the dev side and to keep the client-side software up-to-date.

Comments URL: https://news.ycombinator.com/item?id=49424643

Points: 3

# Comments: 1

I know it's more complicated than that, with economics and privacy factors involved. But if I operate on the assumption that real privacy is real hard I'd rather just be guarded and careful with my prompts and whatever output I give to the LLM and expect that it will be training on that, rather than spill all my darkest secrets to some other LLM provider that pinkie-promises privacy only to leak it publicly later, anyway.