Skip to main content

​
Runtime overview

Beacon supports Devin CLI through native Devin hook payloads sent to beacon-hooks, and by reading Devin CLI’s committed session database for history and per-message detail the hooks do not carry.

​
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, either by beacon endpoint install when it detects Devin CLI (or with --harness devin-cli) or 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. Beacon can also read Devin CLI’s committed SQLite session store:
Sync Devin CLI sessions
The sync path reads sessions.db locally, offline and read-only. It writes mapped events with harness.collection_method=poll, so it can recover historical sessions or sessions that ran before hooks were installed, but it cannot hold, approve, deny, or delay tool calls. See Session database sync.

​
Discovery and status

Beacon detects Devin CLI through the devin executable, ~/.config/devin, ./.devin, or the session database, then checks Beacon hook configuration. Use beacon endpoint hooks status --harness devin-cli to inspect Devin CLI hook status. Use beacon endpoint devin status to inspect committed local sessions and how much Beacon has synced.

​
Install or configuration support

beacon endpoint install prepares shared endpoint config and runtime log paths, and installs the user-level Devin CLI hooks when it detects Devin CLI (or when run with --harness devin-cli). To install, refresh, or manage the hooks on their own, run:
Install runtime hooks
For project-level Devin CLI hooks, run:
Install project-level Devin CLI hooks

​
Telemetry coverage

​
Session database sync

beacon endpoint devin sync reads the session store Devin CLI commits locally:
  • macOS and Linux: ~/.local/share/devin/cli/sessions.db ($XDG_DATA_HOME/devin/cli/sessions.db when it exists)
  • Windows: %APPDATA%\devin\cli\sessions.db
The macOS path is verified against Devin CLI 3000.11.92; the Linux and Windows paths follow Devin’s documented CLI data directory but are best effort, not yet verified. The store is read read-only, in pages, never loaded whole. A cursor in ~/.beacon/endpoint/state/devin.json (beside the system runtime log as devin-state.json in system mode) advances by message_nodes.row_id, so repeated sweeps read only new rows. beacon endpoint devin sync --print previews the mapped events without writing them or advancing the cursor, and --watch sweeps continuously on --interval. Over the hooks the sync adds assistant replies (agent.message), reasoning (agent.reasoning), per-message token usage (token.usage), the per-turn model on every event plus session.context model-change events, compaction summaries (session.compacted), and approval.denied when a tool call was rejected. When the runtime log shows live hook coverage for a session, the sync skips the prompts, tool calls and results and session start the hooks already recorded and adds only what the hook payload cannot carry, so nothing is counted twice; sessions from before hooks were installed are collected whole. Devin re-inserts history on resume and compaction, which the sync dedupes by message id and request id. For large stores, the runtime log’s retention guard and --rotate-bytes behave as for beacon endpoint claude sync. A system-mode install backfill copies SQLite stores only up to 512 MiB; a larger Devin store is skipped there and named in the report, so run beacon endpoint devin sync as the user. The install backfill includes Devin CLI like the other session stores (30-day window, shared byte budget).

​
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.