Hacker News Reader

Comment by egorfine | Hacker News Reader

Can you confirm that Warp is NOT initiating any connection to any service whatsoever unless explicitly enabled in Settings?

Warp had an account requirement in the beginning which spoke volumes about the misalignment of values. Now the terminal is not called a terminal, it is "the agentic development environment" (whatever that means) which also lowkey implies that it might have some kind of online features. But at the same time I understand that it is now an absolute requirement to mention AI on any web page for any product.

Does it call home?

View on HN

> Does it call home?

Absolutely, in heaps. The very moment you start Warp, it sends 5 HTTP requests, (1 version check, 1 LLM model list, 3 telemetry events). The former two go to app.warp.dev, the latter 3 go to warpianwzlfqdq.dataplane.rudderstack.com and include a persistent UUID, your operating system and version, Warp version, and the tracked event name and its properties.

All of this happens before you even see the window. After you're done clicking 'No' to all the SaaS nags, you can turn off telemetry in the settings, but for some reason it gets turned back on when you restart the terminal.

While the terminal is running, it calls home whenever you trip one of the events listed in this 7000-line long file: https://github.com/warpdotdev/warp/blob/d0f045c01bacbd845a63.... Besides all the hosts listed earlier, it also makes requests to o540343.ingest.sentry.io.

All in all, a privacy nightmare.

This is incredible, really. I am impressed. Thank you for the explanation.

See @alokedesai himself confirming this in an answer below.

For transparency, the issue with telemetry turning back on after an app restart was a very bad bug introduced yesterday that only affected new users; this is P0 for us to fix and we’ll have a new release out in the next few hours with a fix. The PR is here https://github.com/warpdotdev/warp/pull/9438/ if you want to follow along.

To add more color to some of your points in the post above:

* We give users the option to disable telemetry before sending any back to our servers.

* We use Sentry for crash reporting, this can be disabled.

* Yes, we record telemetry with the option to disable. The events are in our source code (as you point out) and also on our website.

* We have a network log in app that you can open and view _any_ request we make, including requests to send telemetry.

* If you compile the OSS build it has no telemetry or crash reporting.

Our motivation with open sourcing is to build more trust with our community, not less. Happy to discuss more and, of course, the codebase is available to audit.

> build more trust

At this point I'm not sure we share the same understanding of what constitutes trust.

To me any connection initiated by a terminal app itself is terminal (pun intended) for its reputation, leave alone hideous things like online login or telemetry.

But that's just me: I'm old fashioned. And I'm sure plenty of people will continue to enjoy Warp.

Reply on news.ycombinator.com