Summary
Paseo desktop UI appears stuck with a persistent yellow activity/spinner indicator. Reinstalling Paseo did not fix it.
The app sometimes appears to connect to the daemon in logs, but the UI remains stuck / unusable. The daemon and CLI state also seem inconsistent.
Environment
- macOS: 26.5.2, build 25F84
- Paseo version in daemon logs: 0.2.5
- Machine: MacBook Pro
- Workspace path involved:
/Users/igor/carasent/asma-modules
What I Tried
- Restarted Paseo daemon several times.
- Quit and reopened the desktop app.
- Uninstalled and reinstalled Paseo.
- Issue still persists.
Current Symptoms
curl -s http://127.0.0.1:6767/api/health
# exit code 7 / connection failed
Earlier CLI State Before Reinstall
Before reinstall, paseo daemon status repeatedly showed:
Local Daemon unresponsive
Connected Daemon unreachable
Listen 127.0.0.1:6767
Note Local daemon PID is running but websocket at 127.0.0.1:6767 is not reachable
Relevant Log Observations
~/.paseo/daemon.log shows the daemon starting and the app connecting, but then there are repeated disconnect/reconnect events and slow websocket requests. Examples from the log:
{"daemonVersion":"0.2.5","msg":"Client connected via hello"}
{"daemonVersion":"0.2.5","msg":"Client disconnected; waiting for reconnect"}
{"daemonVersion":"0.2.5","requestType":"fetch_agent_timeline_request","msg":"ws_slow_request"}
{"daemonVersion":"0.2.5","requestType":"checkout_status_request","msg":"ws_slow_request"}
{"daemonVersion":"0.2.5","requestType":"checkout_pr_status_request","msg":"ws_slow_request"}
There are also log entries showing Codex turns starting, even while the desktop UI appears stuck:
{"daemonVersion":"0.2.5","provider":"codex","model":"gpt-5.5","msg":"Starting Codex app-server turn"}
Expected Behavior
After reinstall and daemon restart, the desktop app should connect cleanly and the spinner/activity indicator should disappear when no work is running.
Actual Behavior
The desktop app remains visually stuck with the spinner/activity indicator. Reinstalling the app did not resolve it.
Summary
Paseo desktop UI appears stuck with a persistent yellow activity/spinner indicator. Reinstalling Paseo did not fix it.
The app sometimes appears to connect to the daemon in logs, but the UI remains stuck / unusable. The daemon and CLI state also seem inconsistent.
Environment
/Users/igor/carasent/asma-modulesWhat I Tried
Current Symptoms
Desktop app shows a persistent yellow spinner/activity indicator.
UI does not recover after reinstall.
Health check fails:
curl -s http://127.0.0.1:6767/api/health # exit code 7 / connection failedEarlier CLI State Before Reinstall
Before reinstall,
paseo daemon statusrepeatedly showed:Relevant Log Observations
~/.paseo/daemon.logshows the daemon starting and the app connecting, but then there are repeated disconnect/reconnect events and slow websocket requests. Examples from the log:{"daemonVersion":"0.2.5","msg":"Client connected via hello"} {"daemonVersion":"0.2.5","msg":"Client disconnected; waiting for reconnect"} {"daemonVersion":"0.2.5","requestType":"fetch_agent_timeline_request","msg":"ws_slow_request"} {"daemonVersion":"0.2.5","requestType":"checkout_status_request","msg":"ws_slow_request"} {"daemonVersion":"0.2.5","requestType":"checkout_pr_status_request","msg":"ws_slow_request"}There are also log entries showing Codex turns starting, even while the desktop UI appears stuck:
{"daemonVersion":"0.2.5","provider":"codex","model":"gpt-5.5","msg":"Starting Codex app-server turn"}Expected Behavior
After reinstall and daemon restart, the desktop app should connect cleanly and the spinner/activity indicator should disappear when no work is running.
Actual Behavior
The desktop app remains visually stuck with the spinner/activity indicator. Reinstalling the app did not resolve it.