# Desktop app and device management

Use desktop approvals and manage devices without confusing the daemon with hook enforcement.

Updated: 2026-09-22

Canonical: https://docs.kastra.ai/edge/desktop

## Choose the correct app

The [download page](https://kastra.ai/edge/download.html) offers Apple Silicon macOS and Windows x64 installers. Native Windows ARM64 CLI users can use Scoop; there is no native ARM64 desktop installer. See the [support matrix](https://docs.kastra.ai/start/platform-support).

## Sign in and connect an agent

Open Kastra Edge, complete device login, and confirm the workspace. Install the desired agent hook and run `kastra-edge doctor`. The desktop interface and the command-line tools share the local device configuration.

## Approvals and background work

The desktop app surfaces pending approvals and device status. Review the action and policy before approving. The console remains the place to inspect history and resolve supported approvals without the desktop app.

The daemon supports background features and notifications. The one-shot `kastrahook` process can govern an agent without the daemon because it calls the API directly. Conversely, a running daemon does not prove that a particular agent hook is installed.

## Manage the fleet

In the console's device settings, check the selected workspace, last activity, device version, and reporting coverage. Revoking a device changes its Kastra authorization; it does not uninstall the app or create an operating-system restriction. Verify the device's subsequent behavior and failure posture.

## Updates

Desktop updates can replace bundled binaries. If Homebrew and desktop versions differ, inspect which copy is on PATH before troubleshooting policy behavior. The app is not an MDM service, an offline policy engine, or a general endpoint sandbox.