Workstations
Windows 10 and 11 laptops and desktops
- My computer is so slow.
- I'm out of disk space.
- Outlook keeps crashing.
- OneDrive stopped syncing.
- The printer says it's offline.
The Squash Endpoint Agent is an AI-native agent that runs on your endpoints. It lets Squash take action on those machines to resolve issues and handle work like patching, within the guardrails you set.
Illustrative client
Ticket
Set up Priya Shah for Monday
Set up a new user in Active Directory. Restart the print spooler. Find what's filling the disk. Log off a frozen RDS session. Each one means finding the machine, opening a session, running the same checks, and writing it up. Your RMM can run a script, but a technician still has to pick it, run it, and read the result.
Built-in tools for the tickets MSP technicians handle every day. Fixes wait for a technician's approval unless you set that tool to Always allow.
Windows 10 and 11 laptops and desktops
Windows Update, winget, MSI installers, and printer drivers
Active Directory and Entra Connect
On-premises Exchange
Session hosts and brokers
Shares, folder permissions, and home folders
Now you can delegate the work on the machine to Squash: regular health checks, fixes, patches, and confirming each one worked.
01
Put the agent on the Windows machines you choose. It runs next to the RMM you already use.
02
Squash checks services, event logs, disk, CPU, and permissions on the machine. Checks run on their own.
03
Squash runs the built-in tool for the job. Fixes wait for a technician's approval unless you set that tool to Always allow.
04
Squash checks that the fix worked and records every command, what it returned, and who approved it.
Checks run on their own, so a technician who picks up the ticket starts with answers, not a blank remote session.
Which processes are using the CPU, memory pressure, disk speed, and a timeline of the slowdown.
Entries from the System, Application, and Security event logs around the time it happened.
Free space on each drive, and the biggest folders and files.
Remote access tools, unsigned startup items, browser extensions, and Defender detections.
Who's signed in, network settings, internet access, recent installs, and whether a restart is pending.
The agent stays out of the way, connects out only, and runs only jobs Squash has signed.
About 50 MB of memory and almost no CPU when it's idle.
Connects out over HTTPS. There are no inbound ports to open.
Squash signs every job, and the agent checks the signature before anything runs.
Each device belongs to one client from the moment it's installed, and can't be moved.
The installer and every update are code-signed and checked. A failed update rolls back.
Each command, what it returned, and who approved it stay with the ticket. Secrets stay out of the logs.
See how Squash gathers context, plans, acts, and checks its work on every ticket.