Appearance
Turbo Client 25.7.32.1814
The July 2025 update to Turbo Client includes the following new features and improvements:
New! Turbo Scan (Beta) command allows scanning images or the desktop for known vulnerabilities. The scan command can generate reports in CycloneDX JSON format and allows for customization of scan depth and paths.
New! Turbo Mirror provides real-time, bidirectional file synchronization between running sessions, or between a session and the host. This is the recommended method for keeping folders in sync, such as a downloads folder in a browser session and a local development environment. The feature can be used with the new
turbo mirror
command or with the--mirror
flag onturbo run
andturbo start
and is designed to work seamlessly with remote sandboxes.The
turbo copy
andturbo cp
commands have been updated to be more intuitive, now conforming to standardrsync
style directory arguments and providing clear feedback on the destination of copied files.The
turbo run --mount
command has been significantly improved to allow mounting a directory from another session's sandbox as a one-way folder share. This allows one session to access the files of another, and can be used to create a shared intermediate storage session. This feature now works reliably with both local and remote sandboxes. For example, to create a shared downloads folder between Chrome and VS Code sessions:# Create a session to act as the shared storage turbo new google/chrome -n=storage --remote-sandbox # Mount the storage session's download folder into a new Chrome session turbo new google/chrome --remote-sandbox --mount=storage:@DOWNLOADS@=@DOWNLOADS@ # Mount the same storage session's download folder into a new VS Code session turbo new google/vscode --remote-sandbox --mount=storage:@DOWNLOADS@=@DOWNLOADS@
The visual appearance of application windows can now be customized with the
--skin-border-color
flag, replacing the previous+skin()
syntax.The legacy
turbosh
(Turbo Shell) command has been removed.
This update includes fixes for the following issues:
- A critical error could occur in the Sandbox Manager log when accessing a specific path.
- The
Turbo Sandbox Manager
service failed to start or restart in certain conditions. - An error could occur during the installation process.
- The
copy
command did not copy the contents of a remote sandbox.