The Scenario
Someone on the IT security team flagged that two machines are still reporting VS Code version 1.78 — an editor version that predates the security patch your team rolled out six months ago. You need to know which machines are still on unsupported editors, and which developers they belong to.
You have access to the WakaTime admin account for the team. There are 15 developers. You are not going to message each one individually.
The bad version:
- You log into WakaTime, navigate to the user agents section, and try to read machine and editor data off a dashboard not built for bulk review.
- You screenshot the relevant rows, paste them into a Slack message for the security team, realize you forgot three machines, and have to go back.
- WakaTime does not let you export machine data as a CSV directly from the UI, so you end up copying rows manually.
The security audit deadline is end of week. You have 12 other tickets open. This should not be a half-day task.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent that lives inside your Google Sheet. It reads the sheet, understands what you are looking at, and through its built-in WakaTime integration it pulls machine and editor data directly — no dashboard screenshotting, no manual row copying.
Open a new sheet and paste this:
Fetch my WakaTime machine list and editor/plugin list, then fill this sheet with columns: Machine Name, Last Seen, Editors Used — one row per machine
What You Get
- One row per machine WakaTime has seen on the account.
- Machine Name as WakaTime recorded it (usually the hostname).
- Last Seen as a date, so you can sort by staleness immediately.
- Editors Used as a comma-separated list of editor names and plugin versions detected on that machine.
- Machines with no recent activity appear at the bottom once you sort by Last Seen ascending.
What If the Data Is Not Quite Ready
You want to flag machines inactive for more than 90 days
Your team decommissions machines after 90 days of no activity. You want those flagged automatically:
Fetch my WakaTime machine list. For each machine, if Last Seen is more than 90 days before today, write "STALE" in a Status column. Otherwise write "Active." Fill this sheet with Machine Name, Last Seen, Editors Used, Status.
You need to split editor name and version into separate columns
The security audit form requires editor name and version in distinct fields:
Fetch WakaTime user agents and machines. For each machine, list the primary editor name in one column and the plugin version in the next column. Fill this sheet with Machine Name, Last Seen, Editor Name, Plugin Version, Last Active Date.
You only want machines that match a specific editor
You need to isolate machines running VS Code specifically for the patch audit:
Fetch WakaTime user agents. Filter to only machines where the editor name contains VS Code. Fill this sheet with Machine Name, Last Seen, Plugin Version — sorted by Plugin Version ascending so oldest versions appear first.
Full audit table with staleness flags and editor filtering in one pass
Fetch all WakaTime machines and user agents. Keep only rows where the editor is VS Code. Add a Patch Status column: write "OUTDATED" if Plugin Version is below 1.79.0, otherwise "Current." Add a Staleness column: "STALE" if Last Seen is more than 90 days ago, otherwise "Active." Sort by Patch Status then Staleness. Fill this sheet starting at row 2 with Machine Name, Last Seen, Plugin Version, Patch Status, Staleness.
The security team gets a single table they can filter without asking you to re-run anything.
Try It
Get the 7-day free trial of SheetXAI and open a new sheet in your toolchain audit workbook — ask it to pull your team's WakaTime machine and editor list, flag stale machines, and sort by plugin version so the oldest installs surface first. See also how to analyze developer productivity patterns from WakaTime, or return to the WakaTime integration overview.