> ## Documentation Index
> Fetch the complete documentation index at: https://docs.asymptotelabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# beacon endpoint uninstall

> Remove Beacon endpoint service files while optionally preserving logs or runtime configuration

## Command overview

`beacon endpoint uninstall` unloads the local Beacon service and removes managed endpoint files.

```bash title="Command syntax" theme={null}
beacon endpoint uninstall
```

Use retention flags when you want to keep local evidence or preserve harness telemetry configuration.

## Flags

| Flag | Description |
| - | - |
| `--user` | Use per-user endpoint paths. Enabled by default |
| `--system` | Use system endpoint paths and launch daemon |
| `--log-path <path>` | Runtime JSONL log path |
| `--keep-logs` | Keep runtime logs during uninstall |
| `--keep-config` | Keep harness telemetry configuration during uninstall |

## Examples

Remove the default per-user install:

```bash title="Remove the default per-user install" theme={null}
beacon endpoint uninstall
```

Remove Beacon but keep runtime logs:

```bash title="Remove Beacon but keep runtime logs" theme={null}
beacon endpoint uninstall --keep-logs
```

Remove Beacon but keep harness telemetry configuration:

```bash title="Remove Beacon but keep harness telemetry configuration" theme={null}
beacon endpoint uninstall --keep-config
```

Keep both logs and harness configuration:

```bash title="Keep both logs and harness configuration" theme={null}
beacon endpoint uninstall --keep-logs --keep-config
```

Remove a system-mode deployment:

```bash title="Remove a system-mode deployment" theme={null}
sudo beacon endpoint uninstall --system --keep-logs
```

## Removed paths

Beacon removes files listed in its install manifest, including managed config, collector config, and service files. Unless `--keep-logs` is set, it also removes the configured runtime JSONL log.

On a macOS system install, uninstall also stops and removes the S3, GCS, and Falcon forwarders that the package's MDM helpers install (`com.beacon.endpoint.s3-forwarder`, `gcs-forwarder`, and `falcon-forwarder`). Unless `--keep-config` is set, it deletes `/Library/Application Support/Beacon/Forwarders`, which holds their credentials. `beacon endpoint repair` leaves these forwarders running.

If the endpoint was connected to Asymptote managed ingest, uninstall also stops and removes the `com.beacon.endpoint.asymptote-forwarder` service (or `beacon-asymptote-forwarder.service`) and the `asymptote/` directory holding the Vector config, buffer, enrollment record and device key; `--keep-config` keeps the enrollment record and key. The device stays registered server-side until it is revoked from the dashboard's Beacon Endpoints page.

## Related

<Columns cols={2}>
  <Card title="Endpoint install" icon="download" href="/cli/endpoint-install">
    Reinstall the local endpoint collector and runtime telemetry.
  </Card>

  <Card title="Endpoint status" icon="circle-info" href="/cli/endpoint-status">
    Check endpoint state before or after uninstalling.
  </Card>
</Columns>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.