tcballard / omarchy-plugin-familiar-desktop

# Familiar Desktop — end-of-life transition
**I’ve ended feature development and don’t recommend new installations.**
On 13 October 2026, I decided to retire Familiar Desktop after Omarchy
incorporated much of its mouse-friendly desktop functionality into Core.
v0.1.7
was the patch I shipped afterwards to fix foreign app-ID icon loading. That release does not
restart the feature roadmap.
As of 14 October, the replacement functionality has merged into **Quattro
development**. This is not a claim that it is available in stable Omarchy or on
your installed desktop. Check your version, channel and official release notes
before migrating. There is no requirement to switch to a development channel.
The source, MIT licence, history and existing releases remain accessible. This
repository is not archived. Existing installations are not remotely disabled or
removed by this announcement.
## Existing users: choose your next step
| Your situation | Next step |
| --- | --- |
| Your installed Omarchy does not yet provide the Core desktop you need | You can keep your existing Familiar installation for now, subject to the support limits below. Plan migration when your channel supplies it; do not force an ABI mismatch or load competing titlebar renderers. |
| Core's replacement is available on your desktop | Back up your settings, restore hidden/minimised windows, disable Familiar, then configure and verify Core before uninstalling. |
| You want to remove Familiar now | Use the installed cleanup script after reading the EOL and migration guide. You do not need Core's replacement to uninstall, but need another way to launch and restore windows. |
| Setup, disabling or removal fails | Stop at the reported error. Preserve the installed source, matching helper and recovery files; see troubleshooting. Do not delete the plugin directory to bypass cleanup. |
**Start with the EOL and migration guide** for backup,
safe disabling, rollback, retained preferences and failure recovery.
For an intact supported installation, the removal entry point is:
 [code] 
Run it from your normal desktop session as your own user, not with `sudo`.
It restores journalled windows, refuses to proceed with remaining minimised
windows, resets Familiar-owned configuration and removes the plugin only after
cleanup succeeds. The generic `omarchy plugin remove` command alone does not
perform this cleanup. Disabling alone also does not reset all native preferences.
## Maintenance expectations
- I’m no longer planning v0.2.0, a Mac/Windows split, a curated app collection or
 a new feature roadmap. The earlier plan in #87 is superseded.
- Security, safe removal, migration and narrowly scoped compatibility fixes are work
 I may consider for existing users. I can’t guarantee **a response time, support
 period, future release or compatibility with future Omarchy updates**.
- Bug reports remain open where unresolved. An open issue or PR is not a promise
 to fix or ship it. Report sensitive vulnerabilities