mond: a MobileGestalt editor scoped to five iOS 27 betas
Edit MobileGestalt on iOS 27.0 beta 1 - 4!
At a glance
- What is it?
- mond is a Swift tweak project that edits MobileGestalt on iOS 27, and its support window is the whole story: developer betas 1 through 4 and public betas 1 and 2, with everything at or below iOS 26.x and every later beta marked unsupported. Three tools are implemented and a fourth is planned. The README warns twice that the outcome can be a device that does not boot, and names neither tweak.
- Who is it for?
- Use this if you are on one of the five listed iOS 27 betas and you specifically need to change MobileGestalt values, since the HouseArrest file browser and Pocket Poster are listed without any description. Skip it if you are on iOS 26.x or on any beta past the supported window, because nothing here says what happens then.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 4 days ago.
- What is it written in?
- Mainly Swift, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- rooootdev/mond712 ★ · +82
| Repository | 2026-09-17 | 2026-11-15 |
|---|---|---|
| rooootdev/mond | 630 | 712 |
82 Stars in the last 59 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Supported on developer betas 1 to 4 and public betas 1 to 2, and nothing else
mond is a MobileGestalt editor for a narrow slice of iOS 27, and the version table is the first thing to read. Everything at or below iOS 26.x is marked unsupported. So is iOS 27.0 developer beta 5 or later, and so is iOS 27.0 public beta 3 or later.
What is supported sits between those lines: iOS 27.0 developer beta 1 through 4, and iOS 27.0 public beta 1 through 2.
The two tracks close at different points, and that is the detail worth noticing. A developer on beta 4 is supported, a developer on beta 5 is not, and a public tester on public beta 2 is still supported while one on public beta 3 already is not. So the public beta window is half the length of the developer window and shuts earlier.
That means the tool has a shelf life measured in beta releases rather than in time. When the stable release lands, nothing in this table says what happens, because the table stops at the betas.
The bricking warning does not say which tweaks do it
There is a warning box near the top of the page and it is blunt. Some of the tweaks have the potential to brick your device, and the instruction is to use it at your own risk.
The warning does not name a single tweak. The implemented list runs to three items, Pocket Poster, the MobileGestalt Editor and the HouseArrest File Browser, and there is no mapping between the warning and any of them. So you cannot use the page to decide which of the three to be careful with.
A brick in this context is also a different order of problem from a tweak not appearing. A tweak that fails to apply leaves you with an unchanged device, and one that leaves the device unable to boot needs a restore. The warning is about the second kind and the rest of the page describes behaviour of the first kind.
The practical reading is that the three implemented features are not equally risky in the author's judgement but the page does not give you the information to act on that.
Three tools are implemented and the fourth is only listed as planned
The scope is stated as two short lists. Implemented: Pocket Poster, MobileGestalt Editor, HouseArrest File Browser. Planned: Gestalt Keys browser.
The implemented three do three different kinds of work. The MobileGestalt Editor is the one the project description leads with, and MobileGestalt is the preferences dictionary on iOS that carries the device identity values an editor would change. HouseArrest File Browser is a file browser over the HouseArrest mechanism, which is the sandbox escape hatch normally used to get documents out of an app container. Pocket Poster is the one the page gives no detail on at all.
The planned item is the Gestalt Keys browser, and the naming is suggestive: the MobileGestalt Editor and the planned Keys browser are two views onto the same preference dictionary, one for editing values and one for browsing keys.
No feature descriptions, no screenshots of the tools in use and no configuration options appear anywhere in the page. All four names are given as bare list entries.
Tweaks may disappear on reboot, which makes the release cadence matter
The first known issue is short and has no qualifier: tweaks may disappear on reboot.
That is a persistence problem rather than a correctness one. Nothing is said about whether the change is applied incorrectly, only that it may not survive a restart. On a device that reboots on its own schedule, that turns a MobileGestalt edit into something you may have to reapply rather than something you set once.
It also interacts with how fast this is being cut. Three releases landed inside four days: version 2.0 on 2026-08-16, version 2.2 on 2026-08-17, and a tag named development on 2026-08-19. The last recorded push is 2026-08-19, the same date as that last tag.
A tag literally called development sitting in the release list is worth noting for anyone pinning a version, because it is not a version number and will sort unexpectedly against the numbered ones.
iPadOS gets its own warning, and it is the only one about bootlooping
The last known issue is about a device class rather than a version: iPadOS UI and related tweaks may not work and may bootloop you.
It is the only item on the page describing a failure that leaves the device unusable rather than a tweak that misbehaves, and it is separated from the other three because it applies to a different form factor.
The wording pairs two outcomes. Not working is the mild case, where the iPadOS UI element simply does not appear or does not respond. The bootloop case is the severe one. Both are grouped in a single line, so the page gives you no way to tell which iPadOS tweaks are in the mild group and which are in the severe one.
Combined with the brick warning near the top, there are two separate places in this README where it tells you the outcome can be a device that does not come back up, and neither one attaches the risk to a named feature.
Two known issues you cannot check for before you install
Apple Intelligence spoofing does not work on iPhone 15, which is specific enough to act on. If you are on that model the feature does nothing, and no amount of configuration elsewhere changes that.
The other one cannot be checked in advance: Disable Region restrictions may be broken on some versions and devices. No version is named and no device is named, so the only way to find out is to install and find out.
That is a different failure mode from the iPhone 15 line. The iPhone 15 entry is a closed fact about a specific model. The Region restrictions entry is an open one, and it sits on the same page as a supported-version table that is precise to the beta number, which makes the vagueness stand out.
None of the four known issues is described with a workaround. Each is stated, and the mitigation, where one is implied, is the version table at the top.
Apple Intelligence questions have left the issue tracker for Discord
There is a note about support that narrows rather than widens. No questions regarding Apple Intelligence will be answered in GitHub issues anymore, and the instruction is to ask in the Discord server, which is linked at the top of the page next to the stars and issues badges.
The scope is deliberately narrow in one direction and open in another. It says nothing about non-Apple-Intelligence issues, so the issue tracker is still the place for everything else, but the single largest feature area has moved off it.
That matters for anyone triaging this project from the outside. A closed or redirected issue about Apple Intelligence is not necessarily a fix that was rejected, and the version support table is the only machine-readable statement about what the software does.
The page carries three badges, for the Discord server, for stargazers and for issues, and no release or download link at all.
One Xcode project, and three credits for techniques borrowed from elsewhere
The repository is small in the way a jailbreak tweak repository is small. The top level is a .github directory, a LICENSE, the README, one image called mond.png, an Xcode project directory and the source directory itself. There is no package manifest, no build script and no release binary in the tree.
The credits section is more informative than the feature list. forcequit is credited for work on bad_query. johnny is credited for work on what is called the MCM bug class, which is the mechanism behind the MobileGestalt edits. jailbreak.party is credited for PartyUI and GestaltView, and for implementing the respring method from a third party named neon.
So of the three implemented features, the UI layer, the Gestalt viewer and the respring behaviour are named after other people's projects, and the query mechanism underneath comes from bad_query. The repository is a container for those pieces rather than the origin of them.
The licence is AGPL-3.0, the primary language is Swift, the default branch is main, and there is no homepage recorded. The repository is not archived, with 2026-08-19 as the last recorded push.
Editorial conclusion
Use this if you are on one of the five listed iOS 27 betas and you specifically need to change MobileGestalt values, since the HouseArrest file browser and Pocket Poster are listed without any description. Skip it if you are on iOS 26.x or on any beta past the supported window, because nothing here says what happens then. Before you install, read the known issues twice: reboots can drop your tweaks, the iPadOS path is called out as a bootloop risk, and the region restriction feature is described only as broken on some versions and devices, which you cannot check beforehand.
Frequently asked questions
Which iOS versions does mond support?
A narrow window on iOS 27 only. Developer betas 1 through 4 are supported, as are public betas 1 and 2. Everything at or below iOS 26.x is unsupported, and so are developer beta 5 or later and public beta 3 or later, so the public beta window closes earlier than the developer one.
Can mond brick my device?
The README warns that some of the tweaks have the potential to brick your device and to use it at your own risk, without naming which of the three implemented tweaks those are. A separate known issue says iPadOS UI and related tweaks may not work and may bootloop you.
Will my mond tweaks survive a reboot?
Not always. Tweaks may disappear on reboot is the first item in the known issues list, so whatever you apply is not guaranteed to persist across a restart and may need reapplying.
Where should I ask questions about mond?
Not GitHub issues, at least for Apple Intelligence. The README states that no questions regarding Apple Intelligence will be answered in GitHub issues anymore and directs people to the Discord server linked at the top of the page. It says nothing about moving the other kinds of issue.
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/rooootdev-mond)Star history chart for your README
[](https://hysenlabs.com/projects/rooootdev-mond)Was this useful?