All guides › By use case
By use caseDesktop apps: Electron, macOS and Windows apps on the same canvas
Kaloko opens Electron apps through Playwright with every web check, captures macOS app windows with their accessibility tree, drives Windows apps through UI Automation, and imports screens from any other tool, so desktop flows get the same review as web and mobile.
Desktop apps are often the product nobody walks through before a release: the web version gets the review, the Electron wrapper gets a smoke test. Kaloko treats a desktop window like any other screen.
The problem
Desktop releases are checked by opening the app and clicking around. Nothing is recorded, nothing is compared with the last release, and localized menus or dialogs are seen by customers first.
What changes with Kaloko
platform: electron opens the app through Playwright. Its window is a web page to Kaloko, so selectors, accessibility checks, console errors and semantic questions all work unchanged. platform: desktop captures a macOS app's window with its accessibility tree (or the text on it). platform: windows drives a Windows app through UI Automation with the PowerShell every Windows has: it clicks and types by selector and reads the controls' names and values. Every screen is framed as a window on the canvas, next to the web and mobile runs of the same feature.
How it works
- Name the app
app.electron.main: dist/main.js(or the packaged executable),app.desktop.name: Notesfor a macOS app, orapp.windows: { name: contoso, path: dist/Contoso.exe }for a Windows app (a Store app by itsaumid). - Script the steps
Electron steps get a Playwright
page, soapp.tap('#new')or any Playwright code works. Windows steps useapp.tap('button[name="Save"]')andapp.type(). macOS steps are driven by your tool, by AppleScript or by a person, and Kaloko captures the window. - Check
packs
a11yandconsoleapply to Electron as on the web. Theapppack checks labels, sizes and truncated texts in macOS and Windows windows. Electron also takes the run's colour schemes: a dark capture is the window in dark mode. - Review and compare
the canvas shows each step in a window frame. The next release's run compares screen by screen against the accepted baseline.
Skills and prompts
Walk our Electron app in en and cs: the empty state, creating a note and the settings dialog. Use the a11y pack and share the run for review.Capture the preferences window of our macOS app after each change in this PR, and tell me which labels got truncated in Czech.Expected outcome: window-framed screens per locale with their checks, console errors from the renderer and a comparison with the previous release.
What you get
- Desktop releases go through the same review as the web, with versions and sign-off.
- For Electron, the complete web toolset: DOM checks, accessibility and console, with no extra driver.
- For native macOS and Windows apps, the accessibility tree: missing labels and cut-off texts found without reading code.
FAQ
Windows and Linux apps?
Windows apps are walked on Windows: a person's machine or a windows-latest CI runner, with a signed-in desktop. Nothing extra to install; WinAppDriver and FlaUI are not needed. On Linux, drive the app with your own tool and import the screenshot (and the UI dump if you have one) with kaloko capture --image.
Does it click on my desktop?
On Windows, yes: clicks and typing go to the real screen, so walk on a machine nobody is using at that moment. On macOS Kaloko only takes screenshots and reads the tree.
Which macOS permissions does it need?
Screen Recording for window screenshots and Accessibility for the UI tree, granted to the terminal or the agent app. Without Accessibility, Kaloko falls back to text recognition.