Skip to content

The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu

readme updates

Justin D'Souzac2b4f102587d
diff --git a/README.md b/README.md
index 303dc946..b4ca0e4c 100644
--- a/README.md
+++ b/README.md
@@ -34,9 +34,9 @@ Beacon is [Asymptote's open-source endpoint agent](https://justindsouza.substack
need visibility into local AI agent activity.
It runs locally, captures supported activity from local agent harnesses like
-Claude Code, Codex CLI, Gemini CLI, OpenCode, Factory Droid, Claude Cowork, and
-Cursor, then normalizes that activity into endpoint events your team can inspect
-and retain locally.
+Claude Code, Codex CLI, Gemini CLI, OpenCode, Devin, Factory Droid, Claude
+Cowork, and Cursor, then normalizes that activity into endpoint events your team
+can inspect and retain locally.
Beacon is built to be easy to deploy for Security and IT teams through
[MDM deployment](https://docs.asymptotelabs.ai/cli/security-it-teams) and to
@@ -57,6 +57,7 @@ security pipelines.
| Codex CLI | Local OpenTelemetry configuration |
| Gemini CLI | Opt-in local OpenTelemetry configuration |
| OpenCode | Beacon hook adapter |
+| Devin | Beacon hook adapter |
| Factory Droid | Local OpenTelemetry configuration and optional hook adapter |
| Claude Cowork | Admin-configured OpenTelemetry setup |
| Cursor | Beacon hook adapter |
diff --git a/cli/beacon/README.md b/cli/beacon/README.md
index a9f771c5..7c08c1ff 100644
--- a/cli/beacon/README.md
+++ b/cli/beacon/README.md
@@ -69,6 +69,9 @@ that may need review.
./beacon endpoint hooks install --harness opencode
./beacon endpoint hooks status --harness opencode
+./beacon endpoint hooks install --harness devin --level project
+./beacon endpoint hooks status --harness devin --level project
+
./beacon endpoint integrations claude-cowork setup --endpoint https://collector.example.com --open
./beacon endpoint integrations claude-cowork setup --ngrok --open
./beacon endpoint integrations claude-cowork validate --since 10m
@@ -81,6 +84,12 @@ normalization, retention, redaction, and JSONL output locally. For local
troubleshooting, set `BEACON_OPENCODE_DEBUG=1` in the environment that launches
opencode to emit best-effort plugin debug logs.
+The Devin integration writes Claude-compatible command hooks for Devin for
+Terminal. Project-level installs use `.devin/hooks.v1.json`; user-level installs
+use `~/.config/devin/config.json` under the `hooks` key. The hooks invoke
+Beacon's local Go hook binary and write normalized prompt, tool, command, file,
+approval, and session events to the configured runtime JSONL log.
+
Claude Cowork monitoring is configured in the Claude admin console at
`https://claude.ai/admin-settings/cowork`. The OTLP endpoint must be reachable
by Claude Cowork, so use a durable public HTTPS Collector endpoint for ongoing
diff --git a/packaging/macos/README.md b/packaging/macos/README.md
index 163b31fe..cd025840 100644
--- a/packaging/macos/README.md
+++ b/packaging/macos/README.md
@@ -116,14 +116,16 @@ Recommended rollout:
4. Scope repair/remediation to unhealthy devices.
5. Broaden deployment in stages after inventory and validation stay healthy.
-Cursor, Factory, and opencode hook installation is separate from the base system
-package because these integrations write per-user or per-project runtime
+Cursor, Devin, Factory, and opencode hook installation is separate from the base
+system package because these integrations write per-user or per-project runtime
settings. Run hook helpers only when an interactive console user is present.
-Cursor hooks use `.cursor/hooks.json`; Factory hooks use `.factory/settings.json`;
-opencode uses Beacon's owned plugin at `~/.config/opencode/plugins/beacon.ts`.
-Restart the runtime after installation so new sessions pick up the settings.
-Install hooks with the same endpoint log path as the collector when you want hook
-telemetry and OTLP telemetry to appear in one dashboard.
+Cursor hooks use `.cursor/hooks.json`; Devin hooks use `.devin/hooks.v1.json`
+for project installs or `~/.config/devin/config.json` for user installs; Factory
+hooks use `.factory/settings.json`; opencode uses Beacon's owned plugin at
+`~/.config/opencode/plugins/beacon.ts`. Restart the runtime after installation
+so new sessions pick up the settings. Install hooks with the same endpoint log
+path as the collector when you want hook telemetry and OTLP telemetry to appear
+in one dashboard.
Factory Droid OTLP metrics are also managed outside the base system package.
Droid reads OTLP settings from its launch environment, so deploy the environment
@@ -152,6 +154,14 @@ the logged-in user's context:
beacon endpoint hooks install --harness opencode --level user --log-path /var/log/beacon-agent/runtime.jsonl
```
+For Devin prompt/session/tool/approval/file telemetry, install Beacon's Devin
+hooks in the logged-in user's context or project context:
+
+```bash
+beacon endpoint hooks install --harness devin --level user --log-path /var/log/beacon-agent/runtime.jsonl
+beacon endpoint hooks install --harness devin --level project --log-path /var/log/beacon-agent/runtime.jsonl
+```
+
The opencode plugin is a small Beacon-owned TypeScript adapter that calls the
Beacon Go hook binary with raw opencode payloads. It does not depend on the
third-party `@devtheops/opencode-plugin-otel` package or configure a separate
@@ -198,8 +208,9 @@ tokens do not need to be entered as visible script parameters.
Use `/opt/beacon/jamf/scripts/repair.sh` as a remediation policy for Macs where
Extension Attributes report a stale or unhealthy install. Use
`/opt/beacon/jamf/scripts/install-cursor-hooks.sh` as a separate user-context
-policy for hook telemetry. Set `BEACON_HOOK_HARNESSES=cursor,factory,opencode`
-to install supported hook integrations; the helper writes hook events to
+policy for hook telemetry. Set
+`BEACON_HOOK_HARNESSES=cursor,devin,factory,opencode` to install supported hook
+integrations; the helper writes hook events to
`/var/log/beacon-agent/runtime.jsonl` by default.
### Jamf Extension Attributes
@@ -327,7 +338,7 @@ removal remains under the MDM/package receipt lifecycle.
writable by the collector.
- No recent runtime events: confirm supported harnesses are configured and the
local OTLP ports are not in use by another process.
-- Cursor, Factory, or opencode hooks are missing: run the hook helper while a
- non-root console user is logged in, and confirm the helper uses the same
- runtime log path as the endpoint collector.
+- Cursor, Devin, Factory, or opencode hooks are missing: run the hook helper
+ while a non-root console user is logged in, and confirm the helper uses the
+ same runtime log path as the endpoint collector.