ET Ducky changelog, November 12, 2026
These changes cover running a suggested command from a Live Session answer, running commands as root in the Linux Live Session shell, health checks for patch rings, a ticket scope for organization API tokens, and fixes to remote control. Items marked with an agent version reach a machine when it runs that release or a later one.
New
- When a Live Session answer suggests a command, you can run it on that device from the answer and read the output under it. A command that passes the read-only check runs on the first click. Any other command shows the device and the account it runs as, and runs only after a second click (see Live Sessions).
- A command that the command checks block can be sent for approval from the answer. The request opens a Command Approval ticket, which a workspace owner or organization administrator approves or rejects on the Tickets page.
- The Live Session shell can run a command as root on a Linux agent. It needs the per-member privilege, the host opt-in, and agent 2.8.5.4 installed from the .deb or .rpm package. When Run as root is refused, the message says how to enable it and links the setup steps (see Linux Agent Guide).
- Each patch ring can set its own verify window, crash-loop count, required services, required processes, and a check script that must exit 0. The checks run on each host at the end of the verify window at every verification level. Changing them needs the technician role (see Patch Management).
- Organization API tokens have a new Tickets: write scope. A token with this scope can open native tickets, add link notes, and read a ticket's status through
/api/v1/tickets. It can't read agents or alerts. Only an organization owner or admin can create one (see Public API and MCP Server). - Automated Troubleshooting can run a step in the signed-in user's session on Windows, so an app it opens appears on the user's desktop. Every such step needs your approval. Each result names the account the command ran as. This needs agent 2.8.5.7 (see Troubleshooting Workflows).
Improved
- A patch ring promotes only when every host in it is verified. Each ring sets what happens to a host with an inconclusive verdict (hold the rollout for a person, leave the host out with one verified host still required, or treat it as a regression). Only an organization owner or admin can change that setting.
- A rollout held by an inconclusive host shows the reason in the rollout list and notifies the organization. You can still promote or abandon it.
- Patch notification emails name the device and the target version.
- The Configure form for an agent shows whether patch scanning and patch installs are turned on at the agent. It warns when they differ from the settings ET Ducky pushed. ET Ducky then pushes the settings to the agent again. This needs agent 2.8.5.6 (see Remote Configuration).
- On Windows, a winget upgrade with nothing to install counts as a success with no reboot. A patch job asks for a reboot only when winget reports that the machine needs a restart. This needs agent 2.8.5.6.
- A Linux agent picks up configuration changes made while it was offline when it reconnects. This needs agent 2.8.5.6.
- Linux remote control asks the screen-sharing portal to remember your approval, so later sessions can start without a new prompt where the desktop supports it. This needs agent 2.8.5.4.
Fixed
- Linux remote control works on screens whose width or height is an odd number of pixels. A session that hits a capture error ends with an error message and no longer shows a blank screen. This needs agent 2.8.5.4.
- The Linux agent stops cleanly when its service is stopped or restarted. This needs agent 2.8.5.4.
- Remote control on the Windows sign-in screen no longer freezes at the sign-in prompt on some connections. This needs agent 2.8.5.5.
- When Automated Troubleshooting stops a process and the follow-up check finds no matching process, the run reports the stop as a success.
Try it on one server
One Windows or Linux server costs $5 a month with no query subscription.
See pricing