Pre-alpha — the extension is published, the desktop app builds from source. Don't make it your only safeguard yet.
Install

Extension from the store. App from source.

The browser extension is published — one click and it's on. The desktop app is still built from the source on GitHub, which takes about ten minutes if you already have the tools. It's optional, and strongly recommended: the extension alone can't enforce cool-off delays, run the AI monitor, filter outside the browser, or keep itself installed.

!

Read this first — it's pre-alpha software

Oath Light is early and unfinished. Expect bugs, gaps in coverage, and breaking changes. It is provided as-is, with no warranty. The desktop app deliberately resists being switched off or removed, so only install it if you understand what that means — read the friction system first. It should complement other safeguards and real support, not replace them.

Before you start

What you'll need for the desktop app

Git & Node.js 18+

To clone the repository and drive the Tauri CLI.

Rust toolchain

Installed via rustup. CI pins 1.96.0, so that's the safest version to match.

Windows, ideally

Windows is the first-class target. macOS and Linux builds are experimental.

The walkthrough

Four steps to protected

1

Install the extension

This is the only step that isn't optional, and it's a click. The Chrome listing also covers Edge, Brave and other Chromium browsers.

2

Clone the repository

Grab the source and step into the folder.

terminal
git clone https://github.com/Xeno-legit/Oath-Light.git
cd Oath-Light
3

Build the desktop app

The Tauri app carries the DNS filter, the AI monitor, the friction layer and the recovery tools. The first Rust build is the slow one.

terminal
cd desktop-app
npm install
npm run build

The extension itself has no build step — it's plain files. Scripts and folder names may shift as the project evolves; the repo's CONTRIBUTING.md is the source of truth.

4

Run it, and let the wizard set the floor

The first-run wizard covers voice, strictness preset, vulnerable hours, and the optional master password and trusted contact — then shows you a live block so you can see it working.

  1. Accept the one-time administrator prompt if you can. It writes browser policy machine-wide, points DNS at the local resolver, and registers autostart — that's the strong configuration.
  2. Decline it and the app still runs: the browser stays protected, and the DNS layer keeps asking until you allow it.
  3. Check the extension shows as connected in the app. If it doesn't, the native-messaging host is the thing to look at first.

Platform support today

Extension — Chrome, Edge, BravePublished
Extension — FirefoxPublished
Desktop app — WindowsPre-alpha
Desktop app — macOS / LinuxExperimental
AndroidPlanned

How to remove it

Removal is deliberately slow. This is the friction working as designed, not a malfunction — and it's why you should read about it before installing rather than after.

  1. Settings → Apps → Uninstall is refused outright. The route out is inside the app.
  2. File an uninstall request there. The app mints a random 12-word phrase and starts a 24-hour cool-off, with protection fully active throughout.
  3. After the wait, type that exact phrase back to confirm. Rolling the system clock forward freezes the timer rather than skipping it.