Warp: Background Computer Use Reaches Production

WarpJul 22, 2026

Warp promoted background computer use from internal rollout to production for all users, expanding on the Computer Use capability first launched earlier in 2026. Agents can now drive a target application's window without stealing keyboard focus from the user's active Warp session, and a new teardown path restores focus to Warp automatically once the background session ends. The change closes out a batch of stability fixes, including one that previously left users locked out of their own keyboard after a background session on macOS.

Key Takeaways

Background computer use is now GA, letting Warp agents control other application windows without pulling focus away from the user's terminal session.
A macOS-specific bug where keyboard focus could get permanently stuck on a driven window after a session ended has been fixed with a formal teardown routine.
The teardown path is idempotent and covers every exit case: normal completion, user cancellation, and failed launches all correctly restore focus.
Recording fidelity improved alongside the rollout, with more accurate click/drag trail rendering and duration reporting for computer-use sessions.
This promotion follows Warp's original Computer Use for Agents in Sandboxed Desktops launch earlier in 2026, extending it into a background-capable mode.
The rollout reflects Warp's pattern of shipping a feature to a limited internal channel first, then hardening it through fixes before a production-wide promotion.

Background Computer Use Goes Live

Warp has enabled background computer use in production, moving the capability out of internal dogfood testing and into general availability. Background computer use lets a Warp agent control another application's window (clicking, typing, navigating) while the user continues working uninterrupted in their own Warp session.

Previously, this mode of operation existed only behind an internal flag while Warp hardened its behavior. This release finalizes that work and turns it on for everyone.

Focus No Longer Gets Stuck

The most impactful fix underpinning this promotion addressed a macOS-specific bug where, once a background computer-use session ended, the operating system could leave focus-suppression event taps running indefinitely. In practice, this meant a user's keystrokes could stay silently routed to the driven application (for example, a browser window an agent had been controlling) instead of returning to Warp, sometimes requiring the affected windows to be closed and reopened to recover.

Warp introduced a formal session-end teardown routine that drains the internal activation registry, stops the focus-suppression taps, deactivates the driven window, and re-activates whichever application was in the foreground before the session started. The fix is idempotent and applies whether a session ends normally, is cancelled by the user, or fails partway through, so every exit path now returns keyboard control cleanly.

Supporting Polish

Alongside the production rollout, Warp shipped smaller refinements to the surrounding computer-use recording experience: click ripples and drag trails now render more accurately in captured recordings, overlays stay visible through the "smart speedcut" that trims dead time out of long recordings, and recording durations are now reported accurately after post-processing rather than reflecting an in-progress estimate.

Why It Matters

For users relying on Computer Use to automate GUI-based workflows (browser testing, cross-application automation, and similar tasks), this update removes a category of session-ending glitches and confirms the feature is now considered stable enough for everyone, not just early testers.