Skip to main content

​
Devin Desktop

Beacon supports Devin Desktop through Cascade/Windsurf-compatible hook payloads sent to beacon-hooks.

​
Prerequisites

Before enabling Devin Desktop hooks, make sure:
  • Devin Desktop is installed for the user or available in the workspace where hooks will run.
  • beacon endpoint install has run so shared endpoint config and runtime log paths exist.
  • Beacon hooks are installed with beacon endpoint hooks install --harness devin-desktop.
  • For project-level collection, install hooks from the target workspace with --level project.
  • Devin Desktop is restarted after hook install or removal so new sessions load the updated hook configuration.

​
Collection path

Devin Desktop invokes Beacon’s hook adapter through Cascade/Windsurf hook files. The adapter writes normalized endpoint events to the configured runtime JSONL log.

​
Discovery and status

Beacon detects Devin Desktop through Cascade/Windsurf hook paths such as ~/.codeium/windsurf/hooks.json or ./.windsurf/hooks.json. Use beacon endpoint hooks status --harness devin-desktop to inspect Devin Desktop hook status.

​
Install or configuration support

beacon endpoint install prepares shared endpoint config and runtime log paths. Install Devin Desktop hooks separately: 
beacon endpoint hooks install --harness devin-desktop
For project-level Devin Desktop hooks, run from the target workspace: 
beacon endpoint hooks install --harness devin-desktop --level project
You can also configure Devin Desktop hooks alongside default OTLP harnesses: 
beacon endpoint install --harness claude,codex,devin-desktop

​
Telemetry coverage

AreaSupport
Prompt telemetrySupported through Cascade prompt hooks
Command, tool, and file telemetrySupported for prompt, command, MCP tool, file read, and file write telemetry where Cascade/Windsurf hook payloads are available
Local JSONL and dashboardSupported
MDM deploymentSupported for the endpoint agent; Devin Desktop hooks are installed separately in the logged-in user’s context or project context

​
Deployment notes

Beacon writes Devin Desktop user-level hooks to ~/.codeium/windsurf/hooks.json. Project-level Devin Desktop installs write ./.windsurf/hooks.json, which can also affect Windsurf/Cascade in that workspace. Beacon installs visibility-only hooks for prompt submission, file writes, command execution, MCP tool use, and file reads. The hooks do not block or enforce policy. After installation, generate a Devin Desktop event and check the Beacon runtime log to validate that the Desktop app executed the hook file. Install and uninstall preserve unrelated settings and non-Beacon hook commands. Restart Devin Desktop after installing or removing hooks so new sessions pick up the updated hook configuration.

Supported agent harnesses

Return to the runtime support overview.

Devin CLI

Configure Devin CLI through native Devin hooks.

Hooks

Install, inspect, and uninstall runtime hook integrations.