Tray status.
The helper sits in the tray and opens the local dashboard when you need logs, settings, or recent jobs.
Get the helper running, add the browser button, then click Uoink on any video. No Python install, no command line, no PATH wrangling.
Windows 10/11 / local helper / extension sideload until Web Store approval
Windows 10/11 / release page
The helper bundles Python, yt-dlp, ffmpeg, keyring, SQLite, and MCP pieces. It runs locally and exposes the loopback server at 127.0.0.1:5179.
Windows may flag early builds as an unrecognized publisher. Click More info, then Run anyway if you trust the GitHub release.
Chrome / Edge / Brave / Vivaldi / Opera GX
The extension needs host permissions for supported video pages so it can render the in-page Uoink button and context menu. It does not ask for browsing history.
Until Web Store approval lands, download the extension zip from the same GitHub release and load it through your browser extension page.
DMG, Keychain, LaunchAgent
The macOS path uses the same corpus format and MCP surface. The signed DMG and notarization work are tracked in the release queue.
The helper starts in the background. The extension checks localhost. When both are green, the Uoink button appears on supported video pages.
The helper sits in the tray and opens the local dashboard when you need logs, settings, or recent jobs.
Captures write to your Uoink folder and into a local SQLite index. Nothing uploads to Uoink because there is no Uoink cloud.
Paste into Claude or ChatGPT, or skip the clipboard and let your MCP client call Uoink directly.
Uoink supports Windows 10 and 11 today. macOS support is on the v3.1 track with a signed DMG target. A manual source path is available for developers who want to run the local helper directly.
No. The helper runs in user space. On Windows it installs under %LOCALAPPDATA% and starts from the current-user startup entry.
The extension is Manifest V3 and targets Chromium browsers: Chrome, Edge, Brave, Vivaldi, Arc, and Opera GX. Web Store approval is pending, so the launch path uses the GitHub release zip.
The browser extension cannot run yt-dlp, ffmpeg, Whisper, SQLite indexing, or the local MCP server by itself. The helper does that work locally so your corpus never has to pass through a Uoink cloud.