The 158-tool desktop app is much more than a yt-dlp window
OmniGet starts with a useful promise: paste a link, choose a quality, and put the result in a queue. The README says yt-dlp covers roughly 1,800 sites, while native paths handle courses, Instagram, X, Pinterest, Bilibili, Telegram, torrents, and direct transfers. Downloads can resume, back off after rate limits, and retain the exact command that ran. That is a friendlier daily experience than rebuilding a long terminal command every time.
The scope then expands sharply. The README lists 158 tools across 25 categories, a course player, PDF and ebook readers, flashcards, notes, local music, League of Legends helpers, and an experimental chat client. Some tools are marked beta or planned, which helps, but the menu still mixes mature download jobs with features that have very different failure and privacy costs. Pick OmniGet for the queue first. Treat everything else as optional until it proves useful on your machine.
A 16-second install still leads to a serious source build
Our sandbox installed 367 pnpm packages in 16 seconds and left 374 MB on disk. The checkout itself contained 991 files and about 251,847 lines of source. Building from source needs Rust, Node.js 18 or newer, pnpm, and Linux libraries for WebKitGTK, audio, indicators, SSL, and compilation. This is a desktop product with native edges, even though the JavaScript dependency step was painless.
The documented production command adds a Tauri flag that turns off updater artifacts. Without it, the build stops because the repository has a public updater key while the maintainer alone holds the private signing key. App users avoid that source-build detail, but they meet operating-system trust prompts instead. The README tells Windows users to bypass SmartScreen and macOS users to run two Terminal commands because the packages do not have paid code signing or notarization.
What happened when we ran it
Our fresh unprivileged Debian container installed commit 4d1b961 in 16 seconds, built it in 71 seconds, and passed the available tests in 6 seconds. The container had 3 CPUs, 8 GB of RAM, Node 22, and no secrets. Those results show that the measured source tree could clear its basic project checks. They do not test a desktop launch, a real download, browser-cookie import, plugin installation, or media playback.
The dependency audit was the uncomfortable result. npm audit found 9 known vulnerabilities: 6 high, 2 moderate, and 1 low, with none classed as critical. The repository has 2 CI workflow files and workspace packages, but no Dockerfile or tests directory. A clean build and test command therefore should not be read as a clean dependency report, and our run says nothing about the optional binaries or models fetched after first launch.
Linux playback has 2 open fixes after v0.10.0
Release v0.10.0 shipped on September 28, 2026. Two open pull requests filed on October 1 describe separate Linux playback failures. PR 6 says the AppImage's WebKit process can abort when required GStreamer elements are missing, leaving a blank window. PR 7 says local video, audio, and subtitles can spin forever because WebKitGTK's media loader does not use Tauri's registered asset scheme. Both fixes remain unmerged.
That matters because playback is central to the course and Study pitch. The README already asks AppImage users to install FUSE 2 and GStreamer plugin sets on some distributions, while the .deb and .rpm declare those media packages. Linux users can still use OmniGet as a downloader, but anyone choosing it for the integrated library should verify a release that contains both fixes before importing a large collection.
The 37-tool agent bridge can receive browser credentials
OmniGet's local MCP server exposes 37 tools behind a per-install token. Agents can queue downloads, process PDFs, transcribe files, search disks, inspect startup items, and use social-site helpers. A separate Claude Code plugin can fetch and transcribe media without the desktop app, so the project belongs in both MCP and Claude Code tool searches. That reach is useful when an agent needs to act on a local file instead of merely discussing it.
The same app also handles sensitive material. Its browser extension forwards cookies and referer data so OmniGet can access private posts, members-only video, and paid courses your session can open. API keys can sit in a local vault, and optional AI work goes to the provider you configure. The README says download telemetry is absent and the bridge listens on localhost, yet company policy may still forbid giving one desktop process browser sessions, local-file access, and agent commands together.
The current repository has 78 stars and several dead old-owner links
The repo our lab measured as tonhowtf/omniget no longer resolves on GitHub. The current canonical project is OpenSelena/omniget, and it contains the exact measured commit 4d1b961. GitHub showed 78 stars, a September 30 push, and 2 open issues and pull requests on October 3, 2026. Both open items were pull requests with detailed Linux diagnoses, so recent maintenance is visible.
The migration left documentation debt. The README still claims more than 9,500 stars and links its four plugin repositories, plugin registry, and OmniDisc server under the vanished tonhowtf account. All 6 links returned 404 during this review. OmniGet remains interesting as a friendly shell around proven download engines, but use the current release for the core queue and verify every extra surface you plan to depend on.