Constant background traffic to collab.zed.dev

[raggi]

Summary

On both Windows (dev) and macOS (production) a running instance of Zed was constantly exchanging small (like keepalive sized) packets to/from addresses that resolved to llm.zed.dev.

Steps to trigger the problem:
(I'm making assumptions as restarting Zed on both platforms the issue did not return immediately)

1. Open Zed
2. Do some stuff
3. Put the machine to sleep for a while (maybe overnight?)
4. Wake machine
5. Observe constant round-trip traffic to llm.zed.dev

Actual Behavior:

"Lots" of traffic (not high bandwidth, but constant - was every ~0.5s on Windows, and even faster on macOS) - enough that it's keeping the wifi powered up constantly, aka draining battery.

Expected Behavior:

No need for traffic unless it's doing something useful.

Zed Version and System Specs

Zed: v0.180.0 (Zed Dev e048add)
OS: Windows 10.0.26100
Memory: 63.9 GiB
Architecture: x86_64
GPU: NVIDIA GeForce RTX 4090 || NVIDIA || 572.83

--

Zed: v0.179.2 (Zed)
OS: macOS 15.3.2
Memory: 24 GiB
Architecture: aarch64

[notpeter]

I cannot reproduce the background traffic to llm.zed.dev, but on macOS I can see to steady traffic to collab.zed.dev. Can you confirm whether your traffic is to collab.zed.dev? (they are both behind cloudflare so share the same IPs)

With an empty project open, logged into Zed, I see a continuous 3KB/sec in / 3 KB/sec out to collab.zed.dev

This is likely unintentional behavior.
Thanks for reporting.

[github-actions]

Hi there! 👋
We're working to clean up our issue tracker by closing older bugs that might not be relevant anymore. If you are able to reproduce this issue in the latest version of Zed, please let us know by commenting on this issue, and it will be kept open. If you can't reproduce it, feel free to close the issue yourself. Otherwise, it will close automatically in 14 days.
Thanks for your help!

[github-actions]

This issue was closed due to inactivity. If you're still experiencing this problem, please leave a comment with your Zed version so that we can reopen the issue.