DeskChord support view showing a connected Windows laptop and Android tablet with local diagnostics — Check the device, network, and permission

TERMINAL

A terminal with typed edges.

DeskChord can expose a bounded Windows terminal session when you deliberately grant Terminal. The host stays in the signed-in user session; Android is a client, not a shell host.

Check availability See how it works

Direct private LAN path. Every capability starts denied.

PLATFORM: Windows 10/11 + Android 10+
NETWORK: Private LAN, no relay
PERMISSIONS: Denied by default
ACCOUNT: Purchases, licenses and recovery

CAPABILITY DETAIL

Follow one lane in depth.

The feature index keeps the three specialised paths visible without merging their permissions or readiness status.

01 / CHAPTER

Windows hosts the session.

The terminal lane starts a current-user ConPTY session on Windows. Android receives typed session state and output; it never starts a shell locally.

The profile is selected from a closed allowlist, not arbitrary shell text.
No service, elevation helper, UAC or lock-screen path is added.
The current-user boundary remains in force for the whole session.

DeskChord setup view pairing a Windows laptop and Android tablet on a private local network — Pairing, screen placement, and permission choices

02 / CHAPTER

Every operation has a type.

The peer protocol exposes start, input, read, resize and stop operations with bounded payloads. The terminal grant, transport session and generation are checked before each operation.

There is no generic execute(command) endpoint or shell-text injection path.
Output is bounded and rendered as a session transcript, not an unbounded log stream.
Resize and close are explicit lifecycle operations rather than hidden side effects.

DeskChord cursor crossing from a Windows laptop to an Android tablet over a local connection — The cursor crosses the shared edge

03 / CHAPTER

A grant is not a permanent shell.

Terminal is an independent default-deny capability. Revoking it, losing the authenticated session, or crossing a generation boundary closes the affected route and leaves the local Windows session usable.

Pairing proves peer identity but does not grant Terminal.
Late input and output from a revoked generation are rejected.
Input, clipboard, files, view, Stylus and Remote Devices remain separate decisions.

DeskChord permission controls showing independent local access for cursor, files, pen, and screen view — Every capability has its own permission

04 / CHAPTER

Source support is not device acceptance.

The typed terminal path exists in the source, but its current Windows-to-Android end-to-end and physical acceptance matrix is still pending. The public page keeps that status visible.

Do not treat the browser preview or a unit test as a real terminal session.
A release candidate needs the current physical baseline, revoke and reconnect checks.
Until those gates pass, Terminal remains an explicitly bounded alpha path.

FAQ

Clear answers before you install.

Can Android host a DeskChord shell?

No. Windows hosts the current-user ConPTY session and Android is a typed client. DeskChord never exposes a generic command endpoint.

Does pairing enable terminal access?

No. Pairing establishes identity only. Terminal is an independent grant, denied by default, and each operation is bound to the authenticated session and generation.

Is the terminal path production-ready?

Not yet. The typed source path exists, but current physical end-to-end, revoke and reconnect acceptance is still pending.

DESKCHORD

One desk. Every device.

Start with the local path you already trust.

Check availability