[isehgal]

Fair concern. We don't have true E2EE yet because our service needs access to message content for cross-device sync, notifications, and agent execution. Everything is encrypted in transit and at rest, and all repo operations happen locally on your machine.

We've heard this from other users and it's on our roadmap. The challenge is we're building features like voice coding agents and hosted sandboxes that require plaintext inputs, so we'd need two execution models. Doable, but adds complexity for our team size.

That said, it's something we're prioritizing as we grow. No promises on timing, but it's coming.

If you want to discuss specific requirements or a local-only mode, happy to chat: https://discord.gg/Dc46sYk6e3

[sneak]

> We don't have true E2EE yet because our service needs access to message content

That means you don't have E2EE, period. Implying that there is such a thing as "true E2EE" (as opposed to "E2EE") either indicates that you don't know what E2EE means, or that you're scammily trying to do what Apple does with iMessage and say that something that isn't E2EE is, for marketing purposes.

E2EE means that nobody except the endpoints has keys. There is no such thing as "true E2EE" any more than there is such a thing as "true pregnancy".

[kmansm27]

Yep, you're right, we don't have E2EE period (and we don't claim to have it anywhere), for the reasons I mention above (our cloud sandbox agent and voice agent need plaintext messages, so we'd need access to the keys, which defeats the purpose of E2EE). Apologies for the incorrect wording!

[unsupp0rted]

Hysterical E2EE

[kovek]

https://happy.engineering/ says that they have E2E encryption. Is that true?

[kmansm27]

Yes, they have E2EE, but it comes with some limitations in the features they're able to provide.