# Keryn Desktop

> The desktop app for macOS, Windows and Linux, and the Workbench mode for teams.

Source: https://keryn.dev/docs/guides/desktop/

## Goal

Run the same scanner as Keryn Web in a native window, Deep included, with no browser required, and know what the team mode adds.

## Before you start

- macOS first; other platforms follow the [install page](https://keryn.dev/docs/start/install/), which lists the status of each artifact straight from the registry. The desktop app is built (`dev.keryn.desktop`, version 0.5.2) but not yet published: the app zip is ad-hoc signed, release 0.5.2 shipped the sites and the Keryn Cloud API only, and the Homebrew cask and the Mac App Store need Apple signing and an Apple Developer Program account that are not done.
- The app installed under a regular folder path (see the note at the end).

The desktop app also shows an **AI agents on this machine** card: an audit of the MCP configurations of the AI clients installed for your user (Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Gemini CLI, Continue). It reads those files and lists the servers each would start and their configuration risks; it writes nothing and starts nothing. The CLI does the same with [`keryn mcp audit`](https://keryn.dev/docs/guides/mcp-guard/).

**Keryn Workbench** is the same app in Workbench mode, for teams. It adds a local server that runs scheduled scans of your repositories, policy gates over their AI-BOMs, signed outputs and audit evidence, and sandboxed reproduction of findings (**Verify**, which needs Docker). Workbench (`dev.keryn.workbench`) is in development: its server sidecar is not in the release build yet, so there is no download. Its window may reach only its own local server at `127.0.0.1:8778`; the plain desktop window's content security policy allows connections to itself only.

Install the app under a regular folder path: the Workbench server refuses to start when the app's own path contains a symbolic link.

## What you just proved

Desktop is the same engine in a different shell: the findings, the proof levels and the evidence bundle match the CLI's, so a result produced here can be checked with `keryn verify-bundle` elsewhere. The Workbench mode runs a **local** server on your machine; scheduled scans, signed outputs and sandboxed reproduction happen there, and Verify needs Docker. Workbench is in development, so treat it as such.

## Next

- The same task in a terminal: [CI](https://keryn.dev/docs/guides/ci/).
- Check what Desktop produced: [evidence for auditors](https://keryn.dev/docs/guides/auditors/).
- What runs where: [local by design](https://keryn.dev/docs/concepts/local-only/).
