The 0.7.0-beta.1 release notes describe the Windows and Linux release as a beta that works, but has had far less use than the Mac app, so you should expect some rough edges. Some file types and features are missing by design in this version, and several user-reported problems remain open without a confirmed fix as of 2026-10-16. You can read more about the packages on the Windows download page, the Linux download page and the changelog.
Not in this version yet
According to the 0.7.0-beta.1 release notes and README, the search model and results are the same as on the Mac, except for these missing items:
- The text inside screenshots is not read yet, so a screenshot is found by what it shows rather than by an exact code typed into the search.
- Old Word
.docfiles, RAW photos and SVG pictures are skipped (they are only read on a Mac). See supported file types for the full list. - The Mac app is not part of this release and stays at 0.6.1.
Reported issues as of 2026-10-16
These items come from user reports on GitHub Issues and are observations rather than maintainer-confirmed diagnoses.
| Report | System | What the reporter describes | Status as of 2026-10-16 |
|---|---|---|---|
| #97 | Windows 11 (64-bit) | Indexing finishes with no error, but the folder shows “0 files indexed” and searches return nothing. See 0 files indexed troubleshooting. | Open, no maintainer-confirmed fix in the checked thread |
| #67 | Windows (0.7.0-beta.1) | Commenters on the thread report seeing “0 files indexed” (one sees “0 files out of 0”) even though folders are selected. | Open, no maintainer-confirmed fix in the checked thread |
| #87 | Windows 11 (0.7.0-beta.1) | A file larger than 2 GB in a chosen folder stops indexing, and folders after it are not indexed either (a second user reports the affected sizes are 2 GiB to 4 GiB). | Open, no maintainer-confirmed fix in the checked thread |
| #92 | Linux beta | On first run, setup ends with “The model download stopped” and “0 of 0 files searchable” although the model files were downloaded. See model download troubleshooting. | Open, no maintainer-confirmed fix in the checked thread |
| #95, #96 | Linux and Windows | A malformed RTF file (#95) or a HEIF picture with truncated metadata (#96) can stop the indexing helper; reported from reading the code, with no crash reproduced on Linux or Windows. | Open, no maintainer-confirmed fix in the checked thread |
| #75 | 0.7.0-beta.1 | Feature request noting that .xlsx, .xls, .pptx, .ods and .odp files are skipped. |
Open, no maintainer-confirmed fix in the checked thread |
Documented setup notes
- Unsigned Windows installer: Because
DigUp_0.7.0-beta.1_x64-setup.exeis not signed yet, Windows may say it does not recognize the app. Choose More info, then Run anyway. See the unsigned installer guide. - Wayland shortcuts: On GNOME and KDE under Wayland, DigUp adds Ctrl+Shift+Space to the desktop’s own keyboard settings during setup. On other Wayland desktops, Settings shows the command to bind to a shortcut. See global hotkey troubleshooting.
- GNOME tray icon: The tray icon needs the AppIndicator extension, which Ubuntu includes. Without it, the window’s ⋯ menu has the same items.
- Graphics card use: DigUp runs the model on your graphics card with Vulkan when a quick check at setup finds it faster than the processor and giving the same results, and on the processor otherwise.
How to help the developer
In the 0.7.0-beta.1 release notes, the developer asks beta testers for two things: open an issue at DigUp’s GitHub Issues page for anything that does not work, and if you have a graphics card, mention whether DigUp used it. The last line of speed.log says "device": "gpu" or "cpu". You can find speed.log in %LOCALAPPDATA%\com.abdurrahim.DigUp\logs on Windows and in ~/.local/share/com.abdurrahim.DigUp/logs on Linux.