DeskWink CLI
DeskWink lets the AI you already use (Claude, ChatGPT and other apps that support remote MCP connectors) work with your own Windows PC, Mac or Linux computer. Everything is on by default: the whole computer, commands, your browser and (on Windows) desktop control, with nothing waiting for approval. Limit any of it in your DeskWink settings.
This package is the small program that runs on your computer. It connects out to DeskWink, so your computer needs no open ports.
Requirements
- Windows 10/11, macOS 13+, or Linux (x64 or arm64; a desktop, or a server with no screen)
- Node.js 22 or newer
Get started
npm install -g @deskwink/cli
deskwink launch
The first deskwink launch shows a pairing code and opens app.deskwink.com in your browser. Sign in and confirm that the code matches. DeskWink keeps running in the background.
A new computer starts with everything on, and the first launch asks you nothing: your AI can read and change files anywhere on the computer (except protected places such as SSH keys, saved credentials and password stores), run commands, use your browser through the DeskWink extension, and on Windows use the desktop and read the clipboard. Nothing waits for your approval (approval level 3, with no end). The DeskWink website may change these settings, and DeskWink starts when you sign in. When Chrome or Edge is installed, launch also sets up the link for the DeskWink browser extension, so the extension from the Chrome Web Store connects by itself. At the end launch lists what is on and how to limit it: in your DeskWink settings on the website (Computers), or with deskwink remote-settings off, deskwink autostart disable, deskwink access read folders, deskwink approvals level 0 and deskwink capabilities disable <feature>.
A computer set up with an older version keeps its access, features and approval level. Launch turns on two things for it once: the DeskWink website may change its settings (it prints one line saying so), and DeskWink starts when you sign in, unless you turned that off with deskwink autostart disable. Both decisions are remembered: after deskwink remote-settings off or deskwink autostart disable, launch never turns them back on.
Pairing the same computer again is a fresh start. After deskwink logout, or after you removed the computer on the DeskWink website, the next deskwink launch pairs it as a new computer and turns everything on as above, including the website settings and starting at sign-in (unless you ran deskwink autostart disable). Your earlier settings are not lost: launch keeps a copy as policy.json.bak-<time> next to policy.json in DeskWink's folder and prints where (the three newest copies are kept). Replacing earlier settings with everything on needs you at an interactive terminal: run from a script, a pipe or without a terminal, launch gives the computer the least access instead and prints the commands that turn everything on. Launching a computer that is still paired never changes its settings this way.
The trade-off: with these defaults your AI runs commands and changes files without asking first, and the DeskWink website (and so anyone who took over DeskWink's servers) can change the settings and approve for you. Payment steps in the browser are always refused, the browser still asks you before a new site and before steps such as signing in or sending, desktop control pauses when you move the mouse, and every change is backed up and listed in Activity. Limit what you do not want.
To connect your AI, add https://mcp.deskwink.com/mcp as a custom connector in your AI app, then sign in to DeskWink and allow it. Menu names differ between apps and plans; see deskwink.com/docs.
On a server or over SSH there is no browser to open: deskwink launch prints the link and the short code, and you open the link on your phone or laptop. See "Linux and servers" at deskwink.com/docs/getting-started.
Coding agents such as Claude Code or Codex can install DeskWink for you: point them at deskwink.com/install.md.
Commands
| Command | What it does |
|---|---|
deskwink launch [--passphrase] | Pair (first time), then start DeskWink in the background. --passphrase (Linux) protects the device key with a passphrase |
deskwink status | Show the connection, computer, shared folders and the MCP URL |
deskwink stop | Disconnect now; your AI can no longer reach this computer |
deskwink folders list | add <path> | remove <name> | Manage shared folders (adding needs you at the keyboard) |
deskwink access · deskwink approvals level · deskwink capabilities | How much your AI can reach, which changes go through without asking, which features are on |
deskwink remote-settings on | off | Whether the DeskWink website may change these settings and approve commands for this computer (on by default; off is remembered) |
deskwink autostart enable | disable | Start DeskWink when you sign in (on by default; disable is remembered) |
deskwink restore <execution-id> | Undo a change DeskWink applied |
deskwink logs | Show the local log (metadata only, never file contents) |
deskwink doctor | Check Node, network, clock, credentials and folder access |
deskwink logout | Remove this computer from DeskWink and delete its key; pairing it again later is a fresh start |
Run deskwink help for every option.
How it keeps you in control
- Your AI can reach what you set: the whole computer (the default for a new computer) or only the folders you share. The file tools can't open protected places (system folders, DeskWink itself, SSH keys,
.envfiles and similar secrets). Commands run as you and can reach whatever your account can; turn Commands off or ask for approval to limit that. - Each file change is staged and the previous version is kept for 7 days, whatever the approval level. At a lower level (
deskwink approvals level 0) you review the exact change in the DeskWink console and approve it before anything is written. - Giving DeskWink more access is done here, in your own terminal, or on the DeskWink website while it may change this computer's settings. Each change made on the website needs a recent sign-in and is emailed to you;
deskwink remote-settings offstops the website from making them. Taking access away always works from both. - DeskWink stores your device key in Windows DPAPI, the macOS Keychain, or on Linux in the desktop keyring or a file only your user can read (optionally encrypted with a passphrase). File contents never leave your computer except in answers to your AI.
Links
- Website and docs: deskwink.com
- Privacy: deskwink.com/legal/privacy · Terms: deskwink.com/legal/terms
- Support and security reports: [email protected] (write "Security" in the subject for a security report)
DeskWink is operated by Viva Essence Ltd (England and Wales, company number 16065477). This package is proprietary software, provided under the DeskWink Terms of Service. It bundles open-source components listed in dist/THIRD_PARTY_NOTICES.txt.