Skip to main content

​
Runtime overview

Beacon supports Devin CLI through native Devin hook payloads sent to beacon-hooks.

​
Prerequisites

Before enabling Devin CLI hooks, make sure:
  • Devin CLI is installed for the user or configured in the project 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-cli. The legacy devin harness name still maps to Devin CLI.
  • For project-level collection, install hooks from the target project with --level project.
  • Devin CLI is restarted after hook install or removal so new sessions load the updated hook configuration.

​
Collection path

Devin CLI invokes Beacon’s hook adapter from hook entries in Devin configuration. The adapter writes normalized endpoint events to the configured runtime JSONL log.

​
Discovery and status

Beacon detects Devin CLI through the devin executable, ~/.config/devin, or ./.devin, then checks Beacon hook configuration. Use beacon endpoint hooks status --harness devin-cli to inspect Devin CLI hook status.

​
Install or configuration support

beacon endpoint install prepares shared endpoint config and runtime log paths. Install Devin CLI hooks separately:
Install runtime hooks
For project-level Devin CLI hooks, run:
Install project-level Devin CLI hooks

​
Telemetry coverage

​
Deployment notes

Beacon writes Devin CLI user-level hooks under the hooks key in ~/.config/devin/config.json. Devin CLI project-level installs write the standalone hook map to ./.devin/hooks.v1.json. Install and uninstall preserve unrelated Devin settings and non-Beacon hook commands. Restart Devin CLI after installing or removing hooks so new sessions pick up the updated hook configuration.

Supported agent harnesses

Return to the runtime support overview.

Devin Desktop

Configure Devin Desktop through Cascade/Windsurf hooks.

Hooks

Install, inspect, and uninstall runtime hook integrations.