[elie222]

Why

Cancelling a desktop computer command can leave the client waiting on its response stream. Stop pending reads and buffered events as soon as the request is cancelled, so cancellation reliably reaches the host process.

What changed

• Keep the combined request signal alive while consuming the response and explicitly cancel its reader on abort.
• Check cancellation before yielding buffered frames and release the reader without waiting on stalled abort cleanup.
• Preserve command deadlines and never retry a cancelled command.

Validation

Native computer transport and command suites pass locally, including a deterministic stream that ignores fetch cancellation and stalls cleanup. The real-process abort test also verifies that the child exits. Adapter type checking passes. Windows coverage runs in CI.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
rakazo-www	Skipped		Oct 23, 2026 1:46pm UTC

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; no actionable issues were found.

Summary

Desktop computer requests now stop pending reads and buffered events when the caller cancels or the deadline expires.

• Cancelling a desktop command now stops the response stream promptly.

No actionable issues were found. The full test suites were not run during this review.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Caller cancels or deadline expires] --> B[Cancel response reader]
  B --> C[Pending read finishes]
  C --> D[Check cancellation before delivering events]
  D --> E[Skip waiting for stalled cleanup]
  E --> F[Release reader and reject request]

Loading

_{Reviews (1) · Last reviewed commit: "Cancel desktop computer response reads p..." · Reviewed by Greptile}

[github-actions]

Playwright screenshots

No new feature frames; gallery is suite-vs-main drift.

Open screenshot gallery · Dashboard · CI run

Updated for commit 62d8772.