The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu
Go agent-ai-cliagent-harnessesagent-securitybrowser-extensionciclaude-codecloudcodexcursordetection-engineeringjevknowledge-basememorymobile-device-managementobservabilitysecuritysecurity-information-and-event-managementsecurity-toolstelemetrytraces
---
title: "Common Issues"
description: "Solutions for common issues when setting up and using Beacon."
---
<AccordionGroup>
<Accordion title="My coding agent isn't being intercepted">
Ensure Beacon is configured for your agent. See the [Coding Agent Integrations](/runtimes/cursor) docs for setup instructions for your specific tool.
</Accordion>
<Accordion title="How do I disconnect all repositories?">
In GitHub: **Organization → Settings → GitHub Apps → Beacon Security**, then suspend or uninstall the app.
</Accordion>
<Accordion title="How do I remove agent hooks from my local machine?">
Use `beacon endpoint hooks uninstall` for whichever hook harness you set up:
**Cursor**
```bash
beacon endpoint hooks uninstall --harness cursor
beacon endpoint hooks uninstall --harness cursor --level project
```
**Claude Code**
```bash
beacon endpoint hooks uninstall --harness claude
beacon endpoint hooks uninstall --harness claude --level project
```
**Factory Droid**
```bash
beacon endpoint hooks uninstall --harness factory
beacon endpoint hooks uninstall --harness factory --level project
```
**All supported hook integrations**
```bash
beacon endpoint hooks uninstall --all
```
After uninstalling hooks, restart the affected agent or IDE so new sessions pick up the updated hook configuration. See the [hook command docs](/cli/hooks#beacon-endpoint-hooks-uninstall) for supported harness names and flags.
</Accordion>
<Accordion title="beacon endpoint install fails with Collector ports are not listening">
The collector did not start listening, and the install rolled back. The error goes on to quote the collector's own last error line and the path of its log. On systemd and Windows it names where to look instead. A bind error there (`address already in use`) means another process, often a second Beacon collector, holds one of the ports. To run a user-mode endpoint beside a system-mode one, give it alternate OTLP ports, for example `beacon endpoint install --user --otlp-grpc-port 4327 --otlp-http-port 4328`. Its health-check port moves with them, or you can set one with `--health-port`. See [running user and system mode together](/cli/endpoint-install#running-user-and-system-mode-together).
</Accordion>
<Accordion title="Endpoint package self-update is not running">
For signed macOS package installs, self-update is off by default. Check the
configured mode, updater LaunchDaemon state, and local update events:
```bash
sudo /opt/beacon/bin/beacon endpoint update status
sudo launchctl print system/com.beacon.endpoint.updater
sudo tail -n 30 /var/log/beacon-agent/system.jsonl
```
See [Troubleshooting self-update](/cli/upgrade#troubleshooting-self-update)
for mode explanations, manual apply, and scheduled updater checks.
</Accordion>
</AccordionGroup>
<Info icon="circle-question" title="Still stuck?">
Contact us at [[email protected]](mailto:[email protected]) and we'll help you get sorted.
</Info>