refactor: replace Bun.sleep with node:timers/promises sleep

[thdxr]

Summary

• Replace all Bun.sleep() calls with portable sleep from node:timers/promises in two files
• Removes dependency on Bun-specific APIs where a Node.js standard equivalent exists

[greptile-apps]

Greptile Summary

This PR is a targeted portability refactor that replaces three Bun.sleep() calls with sleep aliased from node:timers/promises's setTimeout, removing a dependency on the Bun-specific global API in favour of a Node.js-standard equivalent that Bun also supports.

Key points:

• The replacement (import { setTimeout as sleep } from "node:timers/promises") is behaviourally identical to Bun.sleep for the one-argument sleep(ms) usage here.
• Both changed files — the TUI workspace-list dialog and the control-plane SSE event loop — use the new import consistently.
• The node:timers/promises setTimeout accepts an optional AbortSignal (3rd argument) that Bun.sleep lacks; this opens the door to making the workspaceEventLoop in workspace.ts more responsive to stop.abort() without any extra error-handling overhead, since the existing catch at the call site already handles AbortError.

Confidence Score: 5/5

• Safe to merge — the replacement is functionally equivalent and the only actionable note is an additive improvement.
• The diff is minimal (3 call-sites, 2 import lines), the two APIs are semantically identical for the sleep(ms) single-argument usage, and node:timers/promises is available in Bun. The sole observation is a style-level suggestion to forward the existing AbortSignal to sleep() now that the API supports it, which would improve graceful shutdown responsiveness but is not a correctness issue.
• No files require special attention.

Important Files Changed

Filename	Overview
packages/opencode/src/cli/cmd/tui/component/dialog-workspace-list.tsx	Replaces Bun.sleep(1000) with sleep aliased from node:timers/promises's setTimeout; single-line change with no behavioural difference.
packages/opencode/src/control-plane/workspace.ts	Replaces two Bun.sleep calls in the SSE event-loop retry path with setTimeout as sleep from node:timers/promises; functionally equivalent, but the stop AbortSignal is not forwarded to the new sleep calls, leaving a small window where the loop continues sleeping after abort is requested.

Sequence Diagram

sequenceDiagram
    participant Caller
    participant workspaceEventLoop
    participant Adaptor
    participant sleep as sleep (node:timers/promises)

    Caller->>workspaceEventLoop: startSyncing(project) — AbortSignal stop
    loop while !stop.aborted
        workspaceEventLoop->>Adaptor: fetch(space, "/event", { signal: stop })
        alt fetch fails / non-OK / no body
            workspaceEventLoop->>sleep: await sleep(1000)
            sleep-->>workspaceEventLoop: resolves after 1 s
            workspaceEventLoop->>workspaceEventLoop: continue (retry)
        else SSE body received
            workspaceEventLoop->>workspaceEventLoop: parseSSE(res.body, stop, cb)
            workspaceEventLoop->>sleep: await sleep(250)
            sleep-->>workspaceEventLoop: resolves after 250 ms
        end
    end
    workspaceEventLoop-->>Caller: loop exits

Loading

_{Last reviewed commit: "refactor: replace Bu..."}

[greptile-apps]

Opportunity to pass AbortSignal to sleep

Since node:timers/promises's setTimeout natively accepts an AbortSignal via its third argument (unlike Bun.sleep), this refactor is a good opportunity to make the event loop more responsive to cancellation. Without passing stop, if stop.abort() is called mid-sleep the loop can take up to 1 second to actually exit — only the next while (!stop.aborted) check ends it.

Suggested change

	await sleep(1000)
	await sleep(1000, undefined, { signal: stop })

Similarly the sleep(250) on line 131 could also receive the signal:

await sleep(250, undefined, { signal: stop })

Note: wrapping the workspaceEventLoop call in a try/catch (already done at line 140) will naturally swallow the resulting AbortError, so no additional error handling is needed.