4 pointsby caihongxu8 hours ago5 comments
  • t_messinis2 hours ago
    Curious about the security model here. Giving an agent access to SMS, contacts, and the ability to send email from my phone is a pretty large capability surface — what's the approval flow look like? Is it per-tool-call, per-session, or do you grant broad scopes up front? The MCP tool-use pattern where everything gets pre-approved feels risky for something like "send email," and I'd be interested to know how you're thinking about the difference between "agent reads my calendar" and "agent sends an email as me.
    • Bridgexapi2 hours ago
      this is exactly where it gets tricky

      once you give something the ability to send messages or trigger actions, it’s not just read access anymore, it’s execution on your behalf

      it looks simple from the outside, but there’s usually a lot of hidden behavior underneath (routing, timing, provider handling, etc)

      so the question becomes less about access and more about how controlled and observable that execution actually is

      curious if you’re thinking about exposing that layer, or keeping it abstracted away

  • meetmodi2 hours ago
    curious why you wouldn't want them to exist independently, giving them their own phone numbers. a lot of the things you want to give them access to on our actual phones can be simple integrations. i like having that abstraction (wouldn't want an agent going crazy on my phone which holds my most sensitive information).
  • 2 hours ago
    undefined
  • dhruv30064 hours ago
    What is the difference between this and android use?
  • arjunthazhath6 hours ago
    Isnt hermes doing the same ? Whats the value prop this offers?