Incidents and maintenance reported on status page for Lilac https://status.heysurf.dev/ en https://status.heysurf.dev/incident/1115958 Thu, 05 Nov 2026 00:38:00 -0000 https://status.heysurf.dev/incident/1115958#15aaa07beb97ea273e889167691e98e7c657a7fdc57cc49f98e0b6b1525860f7 Incident Resolved: Between 07:08 and 07:28 MMT, the agent service lost its database connection. Chats, scheduled tasks and background deliveries could fail during this time. We finished a pending database migration and the service is running normally again. Tasks that failed in that window may need to be retried. We're sorry for the disruption. https://status.heysurf.dev/incident/1099767 Fri, 23 Oct 2026 06:15:30 -0000 https://status.heysurf.dev/incident/1099767#cfc6fac55d2263c0a0b95f8e5ab70f61ea77429aeacd1d5edf4916be9fb44ee3 Incident We have identified the root cause of the issue and the services will return to normal. https://status.heysurf.dev/incident/1099767 Fri, 23 Oct 2026 01:33:11 -0000 https://status.heysurf.dev/incident/1099767#662181fc5c0252e41b8084b0c2226235ff400eaa45b9c0c3616b2694883ca415 Incident We are continuing to investigate the reason why the Web Search API is down. The agents are currently following back to the browser use. https://status.heysurf.dev/incident/1098238 Thu, 22 Oct 2026 00:54:24 -0000 https://status.heysurf.dev/incident/1098238#2654d72238f3251e7ce50b09e5f822cd3344160ff2f2b748a1ad5887e34d4d3b Incident **Postmortem: Desk sandbox failures and stuck conversations** We investigated reports of file and command tools returning “Sandbox is unavailable” and conversations repeatedly showing “An agent is already running on this thread.” Affected users could not complete tasks requiring computer access. Some conversations also rejected follow-up messages. The sandbox failure came from how we handled Desk startup. Installing the Desk’s preset Node or Python dependencies was treated as a requirement for making the entire computer available. When installation timed out or failed, that error blocked shell and file tools—even though production logs showed the computer had started and remained reachable. Our logs did not preserve the installer’s diagnostic output, so we cannot determine the underlying reason it exited with status 1. We also found a recovery gap in conversation admission. A Redis marker records that a thread has an active agent. If cleanup failed, that marker could continue blocking messages after the queue job had ended. The frontend then displayed the rejection as an assistant reply instead of recovering the conversation. We have merged fixes that: - Keep computer tools available when preset dependency installation fails. - Bound installation timeouts and preserve useful failure diagnostics. - Clear stale busy markers when the queue confirms a job completed or failed, while protecting active jobs and retries. - Restore rejected messages to the composer and reconnect the frontend to the active task. Both fixes passed their automated checks before merging. Production recovery has not yet been verified. We’re sorry for the interruption and the misleading error messages. https://status.heysurf.dev/incident/1098238 Thu, 22 Oct 2026 00:54:11 -0000 https://status.heysurf.dev/incident/1098238#8029b99bb8fb1f000f51864afa2ddf683e8070f65ed8568c121ea4094196b729 Incident The sandbox and agent is having issues.