‹ BackHN Continuity

Thread

What Meta got right with Muse

138 points · 189 comments · young_mete

  1. egl2020 · · focus · HN ↗
    The privacy issue blocks me from adopting this or other personal assistants: do I want to give muse my identity data and access to my mail, calendar, and phone so it can do even basic tasks like make appointments or pay bills?

    It will be interesting to see if muse's privacy features can get users over this.

    1. rienbdj · · focus · HN ↗
      There will come a point where the local models are good enough (and iPhones powerful enough) for this to be possible without privacy downsides.
      1. raz32dust · · focus · HN ↗
        A lot of use cases for agents require long running sessions. And you're likely to have many agent sessions running in parallel. These aren't going to be running on your personal devices
        1. wren6991 · · focus · HN ↗
          My personal solution to this is to run DSH in an Incus VM on a local machine, then expose the web UI to the internet through my VPS (with some extra auth). I also made a couple of UI tweaks so it works better as a PWA.

          Now I have persistent chats and a persistent environment that I can talk to from any device, including my phone. Even have X11 + CUA + Chromium inside the VM so the agent can use a real browser for sites that require it. DSH bwrap is the first layer of containment, VM is the second layer. I can swap between API models and local inference with a drop-down in the UI.

          I realise this is way more setup than Meta's customers would tolerate, but the HN crowd could slap something together quite quickly. Using a coding agent with a nice chat UI as your general chat client is surprisingly smooth: just create an empty workspace.

          I think Muse is the right shape in a lot of ways but I come unstuck at the point where my personal details and credentials are inside the VM.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.