The Explorer integration deletes whatever folder you point it at
Phone Link / KDE Connect alternative
At a glance
- What is it?
- Sefirah pairs a Windows PC with an Android phone over the local network, sharing clipboard, notifications, files, calls and screen. Its storage integration carries an explicit data loss warning, its clipboard reader escalates through three separate privilege mechanisms, and the desktop app can grant itself a notification permission on the phone over ADB without asking.
- Who is it for?
- Sefirah is a reasonable pick if you want a Windows and Android pairing utility you can read end to end in one sitting, because the feature list is short and the documentation is unusually candid about what breaks. Three things to decide before you install it.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 28 days ago.
- What is it written in?
- Mainly C#, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 14, 2026, and from our analysis. They are not legal advice.
Star history
- shrimqy/Sefirah3,094 ★ · +137
| Repository | 2026-09-24 | 2026-11-14 |
|---|---|---|
| shrimqy/Sefirah | 3k | 3.1k |
137 Stars in the last 51 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The storage integration is documented as a data loss hazard
One feature on this page is described with a warning in capitals, and it is the one most likely to cost you something. Integrating the Android storage into Windows Explorer requires Android 11 or newer and a storage access permission, after which the desktop app creates a link to the phone's storage in File Explorer. The documentation then says, in a warning, that you must not set the remote storage location to a pre-existing folder, because it will delete the contents of that folder.
That is not a subtle interaction. A remote storage location that points somewhere real will clear it, and the user-facing surface for choosing it is a folder picker inside a settings screen.
The same feature carries a second caveat: it is still a bit experimental and may not work on all Windows versions, especially older Windows 10 releases and unofficial debloated Windows 11 builds. So the honest reading is that this is a preview feature with a destructive failure mode, and the two caveats sit next to each other for a reason. Every other feature on the page is a copy or a control; this one writes to your disk from the other side of a network link.
The desktop app grants itself a notification permission over ADB
Android 15 stopped showing sensitive notifications to anything but the system, and that is the kind of notification that matters: the ones carrying codes and account activity. The documented workaround is an app operation command rather than a settings toggle.
adb shell appops set com.castle.sefirah RECEIVE_SENSITIVE_NOTIFICATIONS allowTwo further details make this sharper than a one-off command. On some devices, and OnePlus is named, the command fails until system optimization or a permission monitoring switch is turned off in developer options, after which you run it again. And if ADB is connected, the desktop app attempts this grant by itself when the device comes online.
That last sentence is the one to sit with. The operation is the same grant, and the app performs it without a prompt, so the boundary between what you configure and what the tool quietly enables is narrower here than anywhere else in this documentation. Obtaining ADB in the first place requires USB debugging authorisation on the phone, so it is not unauthenticated, but it is a state change made on your behalf.
Clipboard reading needs Shizuku, then ADB, then accessibility
Automatic clipboard sync from Android to a desktop is the feature people want, and on modern Android it cannot be done by an ordinary app. The documentation lays out the escalation explicitly.
Automatic detection on Android 10 and newer requires either the Shizuku service or a connected ADB session. In practice you enable clipboard sync in the device settings, enable auto-detect on the app's settings page, and then grant Shizuku if you have it or keep ADB connected from the desktop side. The app prefers Shizuku when it is available and falls back to ADB. Accessibility remains a last resort when neither is available and you have granted the accessibility permission, and the documentation says plainly that it may not work in every scenario.
Images need a second switch, since received images are only placed on the Android clipboard once an option to add them is enabled. And manual sharing bypasses the problem entirely through three routes: a persistent status notification, a Quick Settings tile, or the share sheet.
Twenty-one ports on the local network, and a key you must match by hand
Pairing is a local network arrangement, not a cloud account, and the network requirements are spelled out. Both devices have to be on the same network, and if the devices discover each other but will not connect, the documentation points at the firewall and a port range: 5149 through 5169.
Twenty-one ports for a desktop and a phone to find each other is a wide surface for a local service, and it is the kind of detail that matters on a shared or office network where outbound connections are logged.
The connection itself has a handshake you participate in. The Android side initiates, either manually or automatically, with manual described as faster and automatic as taking longer because it has to work out which address works. Windows then shows a pop-up to accept or decline, and the instruction is to make sure the keys match on both devices. After that, both sides land on their home screens and the first notification sync takes a while to arrive. Connection refusal is a documented option, which is worth noting on a shared network.
Two steps in the walkthrough are numbered six
The how-to list has eight steps and two of them share a number. Setting up is one, clipboard sharing two, file transfer three, Android storage four, SMS texting five, and then Bluetooth calling and screen mirroring are both numbered six.
In a strict renderer the second six becomes seven, and in GitHub's own rendering the marker is corrected silently. Either way the source is wrong, and the effect for a reader following along by number is that the last two steps look like one, or the count no longer matches the eight headings.
The content of those two steps is where the two most hardware-dependent parts of the app live. Bluetooth calling asks you to remove the device first if it has already been registered with another app, because Windows binds a device to one app, and then to pair it either through the app or through Windows settings. Screen mirroring needs scrcpy downloaded, extracted and pointed at from the settings, with launch preferences configurable, and it is started by plugging the phone in over USB and clicking the phone frame.
Two repositories, two stores, and a different permission path for sideloading
The Windows side is what this repository holds: source, a distribution directory, a licence, and a translation configuration that points at a Crowdin project. The Android side lives in a separate repository, linked from the badge row.
Each side has its own store. The desktop app installs from the Microsoft Store. The Android app is on Google Play and also on a third-party F-Droid style repository, which means a sideloaded copy is a supported path rather than a hack.
That has a consequence the documentation handles explicitly. During setup it tells you to grant the restricted settings entry from the app's info page after attempting to grant notification access or accessibility, because Android blocks side-loaded apps from requesting sensitive permissions. In other words the permission dance differs by distribution channel: a Play install can ask, and a repository install has to be unlocked in system settings first. SMS is the other permission-heavy feature, needing everything on the permissions page followed by a reconnect, and it supports switching between dual SIMs while attachments remain unimplemented.
The package identifier and the release codename both point elsewhere
The name of this project collides with several other things, and the repository is where that shows. The Android package identifier is not the product name: it carries a castle word in front of it, visible in the app operation command the documentation asks you to run. And the 3.0.0 release is not titled 3.0.0 alone, it carries a single codename after the version.
Neither choice is explained anywhere in the documentation. There is no line saying where the name comes from or what the codename refers to, and for a project whose name is also a word in other languages and a proper noun in a couple of fandoms, that silence is a practical problem: someone searching for the name will land on unrelated material and never reach this page.
The release cadence itself is healthy. Three tags in three months, ending with 3.1.0 in late August 2026, and the branch was pushed to on the same day this description was written. The licence is GPL, which matters for anyone who wants to change it.
Linux gets one sentence, and the feature list never says which features
There is a section headed Linux status and it contains one claim: support is limited, and some features available on Windows may not be available on Linux. No list, no matrix, no partial credit.
That is the entire Linux story, and it sits next to eight features listed without any indication of which platforms they cover. Storage integration is the obvious candidate for exclusion, since it mounts into Windows Explorer, and the desktop app itself is distributed through the Microsoft Store, so a Linux user is already outside the documented install path.
The honest way to read the feature list is as a Windows feature list. Everything in it is presented unconditionally, the one platform caveat is a single sentence, and the storage caveat is the only one that names a specific Windows version range. Anyone on Linux is left to discover the boundaries by running into them.
Editorial conclusion
Sefirah is a reasonable pick if you want a Windows and Android pairing utility you can read end to end in one sitting, because the feature list is short and the documentation is unusually candid about what breaks. Three things to decide before you install it. Do not enable the storage integration until you have read the warning, because pointing it at an existing folder deletes that folder, and it is marked experimental besides. Decide how much privilege you want to hand the clipboard reader: Shizuku, ADB, or an accessibility fallback the documentation admits may not work everywhere. And decide about the notification permission, since the desktop app will try to grant it for itself over ADB when the phone comes online. For anyone on Linux, expect a partial experience that this repository describes in a single sentence.
Frequently asked questions
how to use sefirah
Put both devices on the same network with ports 5149 to 5169 open, launch the Windows app and wait for the devices to appear, then initiate the connection from Android by manual or auto connect. Accept the pop-up on Windows after confirming the keys match on both devices. Clipboard sync then needs its own switches enabled on each side.
how to install sefirah
The Windows app comes from the Microsoft Store. The Android app comes from Google Play or from a third-party F-Droid style repository. They are two separate repositories: this one holds the desktop side and another holds the Android app.
Why can Sefirah not see all my Android notifications?
Android 15 and later hide sensitive notifications. The documented workaround is an app operation command over ADB, and on some devices you first have to disable system optimization or permission monitoring in developer options and run it again. If ADB is connected, the desktop app attempts the grant itself when the phone comes online.
Is it safe to point the Sefirah storage integration at an existing Windows folder?
No. The documentation carries an explicit warning not to set the remote storage location to a pre-existing folder, because it will delete that folder's contents. The same feature is called experimental and is reported as unreliable on older Windows 10 releases and unofficial debloated Windows 11 builds.
Does Sefirah work on Linux?
Partially. The documentation states that support is limited and that some features available on Windows may not be available on Linux, without listing which ones. The Windows application is distributed through the Microsoft Store, so a Linux install is not one of the documented paths.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/shrimqy-sefirah)Star history chart for your README
[](https://hysenlabs.com/projects/shrimqy-sefirah)Was this useful?