Summary

Warp shows a macOS spinning-wait cursor (beach ball) for a few seconds on every cold launch before the UI becomes interactive.

Problem

On every fresh launch of the Warp app, the macOS beach ball appears and the UI is unresponsive for under ~5 seconds before the first window/tab is usable. This happens consistently on every launch, not just after updates or reboots.

Expected behavior

Warp launches and presents an interactive prompt without the OS-level beach ball appearing on the main thread.

Actual behavior

On every launch, the beach ball appears for a few seconds (under ~5s) before the UI responds to input. After that brief stall, Warp behaves normally.

Reproduction steps or desired workflow

1. Quit Warp fully.
2. Launch Warp from the Dock / Applications / Spotlight.
3. Observe the macOS spinning-wait cursor (beach ball) for a few seconds before the window becomes interactive.
4. Repeat — the stall reproduces on every launch.

Artifacts

None attached. A spindump or sample of the Warp process captured during the stall (e.g. sample Warp 5 -file /tmp/warp-startup.txt immediately after launching) would likely help pinpoint what is blocking the main thread during init.

Warp version

v0.2026.04.27.15.32.03

Operating system

macOS 26.5 (Tahoe), Apple Silicon (arm64)

Possible source references

• Issue Warp freezes at 100%+ CPU on startup with macOS 26.2 (Tahoe) #8912 ("Warp freezes at 100%+ CPU on startup with macOS 26.2 (Tahoe)") — closed, but describes a similar startup-stall pattern on Tahoe; the residual sub-5s beach ball on 26.5 may be a milder remnant of the same code path.
• Issue Intermittent spinning beachball when typing commands #6551 ("Intermittent spinning beachball when typing commands") — open, unrelated trigger but may share the same main-thread blocking surface area.