Release notes

SpeedDesk is in beta. Newer builds are added at the top. The current build is 68. Creating an account requires agreeing to the terms. No confirmation email is sent until that box is checked.

Build 68

  • The picture keeps up better on a full-motion desktop, including over a relay. On the same network the picture is aimed at under a fifth of a second behind the computer.
  • The Windows key is sent to the computer, including Win+R. Choosing a program brings that window forward.
  • The local page hides emails, names, paths, and addresses until you click them.
  • When no computer is signed in, the computers page has a Download button for the same program.

Build 67

  • Several agents can share one computer. Each agent has its own labelled cursor. The person at the computer still owns the mouse and keyboard.
  • An agent acts through the controls on screen when it can, so it does not have to move the real pointer.
  • A second desktop is offered only on Windows Server with the Remote Desktop Session Host role. Home and Pro stay on this desktop and say so.

Build 66

  • A test copy's picture page stays on this computer. A page from another site cannot open it.
  • The address check on a test copy is not a login. It includes every address on that computer. The picture is protected by the connection's own credentials.
  • Removing one linked account leaves that computer's status until the last account is removed.

Build 65

  • A test copy can use its own folder and port. The installed program is unchanged when those are not set.
  • GET /api/desk/COMPUTER/status still drops its saved answer when that computer is removed.

Build 64

  • GET /api/desk/COMPUTER/status can be read while sharing is off. It still cannot change settings.
  • That status lists sharing, ask-before-connect, Allow programs, and linked account names. It does not list tokens.

Build 63

  • The local page shows sharing, ask-before-connect, Allow programs, and linked account names. It does not show tokens.
  • GET /api/desk/COMPUTER/status reads those same switches. It cannot change them.
  • A hidden viewer tab does not ask for a new picture or reconnect.

Build 62

  • OpenH264 is checked when it first loads, then reused. A file that does not match Cisco's copy is not used.
  • A still desktop is not treated as a frozen picture. If the viewer picture stops, it asks for a new one and then reconnects.
  • If the graphics picture is bad and software video is off, that picture is not sent. The local page says to turn software video on.

Build 61

  • Software video uses OpenH264. It is downloaded from Cisco the first time you turn software video on.

Build 60

  • A green or frozen picture is detected, and the computer switches away from that graphics encoder.

Build 59

  • Automation is faster and cheaper: batch actions, a UI tree, cheaper screenshots, text reading, a window list, wait-for, the clipboard, and a help endpoint.
  • Viewer menus open one at a time. Programs and Files share one design. Back shows only when a folder is open. Type opens the keyboard.
  • Account email is less likely to land in spam. A bad graphics picture can fall back to software video.

Build 58

  • Phone gamepad controls are redesigned. Mouse movement on the picture is steadier.

Build 57

  • The site footer lines up on a phone. Picture rendering is corrected.

Build 56

  • A saved device has a short name you can change. The browser's own description is not stored.
  • Phone controls sit below the picture. Edit layout moves each one onto the picture or back, and that arrangement stays on the device.

Build 55

  • Phone controls are large enough to tap, and they stay on the screen. Settings and computer names fit a phone width.

Build 54

  • Computers lists only computers. Saved phones are in Settings. On a phone, the picture fills the screen and the controls sit in one bar.

Build 53

  • Signing in another account leaves update checks, the relay, local programs, and website control as they were.

Build 52

  • Sharing off stops website control on the server as well as on the computer. The signed-in local page still shows the program address.

Build 51

  • Sharing off stops viewers and website control. The home page footer is grouped, and the local page keeps everyday controls up front.

Build 50

  • A new install asks before a viewer connects. A computer that already saved that choice keeps it.
  • Build 49 and later programs sign out only when the website repeats that the sign-in is unknown. Build 48 programs sign out on the first such answer.

Build 49

  • SpeedDesk runs in the system tray, without a command window. Sharing on the local page and in the tray decides whether remote viewers can connect.
  • Build 49 programs sign out only when the website repeats that the sign-in is unknown. Older programs still get the previous answers.

Build 48

  • Build 48 programs sign out when the website says the sign-in is unknown. A viewer is told when the computer's connection is replaced.

Build 47

  • The same account can reconnect while the previous connection is still open. End all sessions on the computer signs every linked account out of this computer.

Build 46

  • Adding an account to a computer requires the computer itself. Ending one account's sessions closes that account's live viewers.

Build 45

  • A computer can be signed in to more than one account. Each account has its own token. Removing it from one account leaves the others signed in.

Build 39

  • An older plain sign-in file, from before sealing, signs that computer out on the first start. Sign in again once, then remove the old entry on Settings.

Build 38

  • Copying the program folder to another PC does not reuse this computer. A cloned disk needs sysprep, or machine.id and public.json deleted, before sign-in.
  • Signing out of a plain sign-in file tells the website to reject that token, then disconnects.

Build 37

  • Copying the program folder to another PC does not reuse this computer's id. Each PC keeps its own entry.
  • Signing out of a plain sign-in file disconnects that computer now.

Build 36

  • A cached Windows name, including one saved as the previous Windows name, follows the current Windows name. A name chosen on the website still stays.
  • If the sign-in file cannot be sealed, this run stays signed in and the same computer is used next time. A plain file can be removed from the local page.

Build 35

  • A computer renamed on the website before the renamed flag still keeps that name, unless the saved name is a Windows default such as DESKTOP- or WIN-.
  • Copying public.json to another Windows account or another PC signs that computer out. That is expected.
  • Tracked: crypto-bigint 0.5.5 (RUSTSEC-2026-0387), pulled in through p256 and p384 from webrtc, can leak timing. It is hard to exploit. It stays until webrtc updates.

Build 29

  • The website token on the computer stays hidden until you press Show.
  • A full snapshot is GET /api/desk/COMPUTER/snapshot?full=1. Without full, the picture stays at most 1280 wide.
  • The program reports the current Windows computer name.
  • Settings can end every session, and Settings can delete the account. Privacy is linked from the footer.
  • Sign-up stays limited, and the account still needs the email code before a computer can sign in.

Build 28

  • Settings can replace a website token, and it shows the new one once. The program on that computer is not given the token. Sign in again at http://127.0.0.1:18740 so the program learns it.

Build 27

  • New website token on the computer only works if this computer still has the current token. If it does not, the page asks you to sign in again with your password.
  • The Settings button asks once. Reloading that page does not make another token. The new token is shown once.

Build 26

  • New website token, on the computer at http://127.0.0.1:18740 and on Settings, replaces the token immediately. It works while website control is off. The old token does not come back.
  • A wrong password slows the next try, and the real password is still checked after that wait. A remembered browser is not slowed.
  • A program that presents the wrong website token is told the token was refused, instead of being told the computer is offline.

Build 25

  • A sign-in token can no longer replace the website token. The program proves the token it already holds, and a saved token stays until you sign in again.
  • Wrong passwords from one IPv6 network are counted together. Each wrong password also makes the next try a little slower, from any network.
  • If this computer cannot save the website token, the page at http://127.0.0.1:18740 says so instead of asking for another one.

Build 24

  • The website token is its own random value. It is no longer made from the computer's sign-in. After this update, copy the Website token again from http://127.0.0.1:18740.
  • Too many wrong passwords lock that email on that network for 15 minutes. Another network can still sign in.
  • A snapshot that fails repeats what the program reported, such as no screen or a picture that was too large. A still desktop still returns a picture.

Build 23

  • A popped-out program window can be used, not only watched. Hover, click, right click, the wheel, and typing reach that program. A minimized program is restored and brought to the front when you pop it out. Its menus, dropdowns, and dialogs show in that window too.
  • Popping out a second screen no longer moves the main picture onto that screen.
  • The Files window can be popped out and closed again. Bring it back appears on the tile while a computer is in its own window.
  • The Programs list matches Alt+Tab. The desktop, hidden overlays, and tool windows are left out.
  • If the browser blocks a new window, the picture says so instead of doing nothing.
  • Website control is off until you tick “Let bots control this computer through the website” at http://127.0.0.1:18740. The website token on that page changed. The program's own sign-in no longer works as a website token.
  • Safer sign-in and sign-out forms, and a website that keeps running through broken or oversized requests.

Build 22

  • A snapshot works while the desktop is still. It no longer waits on a picture change, and a failed snapshot no longer says the computer is offline.

Build 21

  • Click, type, and key now reach the program. Build 20 accepted the website calls, but the program only answered move and snapshot.

Build 20

  • Click, type, and a single key use the same website token as snapshot and move.
  • POST /api/desk/COMPUTER/click jumps to a point and clicks. Leave out x and y to click where the cursor already is. button is left or right. double is optional.
  • POST /api/desk/COMPUTER/type writes text into whatever has focus. It does not add Enter unless enter is true. At most 500 characters.
  • POST /api/desk/COMPUTER/key presses one key or a simple combo, such as Enter or Ctrl+A.

Build 19

  • Ask a computer for a picture without opening the viewer. The address is /api/desk/COMPUTER/snapshot. The answer is JSON, not an image file, so it is not rewritten as a picture.
  • The JSON includes the screen size, the pointer position, how the computer is connected, the time, and a JPEG. The pointer is drawn on that JPEG.
  • w is how wide the JPEG may be, at most 1280. q from 1 to 100 is the JPEG quality.
  • POST /api/desk/COMPUTER/move still places the cursor with one point and does not click.

Build 18

  • The line under the picture shows the cursor, the screen size, direct or relay, how long the picture took, and the round trip. The cursor cannot cover that line.
  • Add ?agent=1 to a viewer link to fit the picture in a 1280 by 800 window and use a smaller picture.
  • Add ?jump=0.5,0.4 to place the cursor once the picture appears.

Build 17

  • The picture starts sooner. A direct try lasts about 3 seconds, then the secure relay. A blocked UDP port no longer holds the picture.

Build 16

  • The picture has a coordinate grid. The origin is the top-left. x grows right and y grows down, both from 0 to 1.
  • Type a point and press Jump. One pair of numbers places the cursor. It does not drag.

Build 15

  • The computer's cursor is drawn on the picture and follows the mouse. The browser's own arrow stays off the picture.