nanoMuse 1.0.9 · Tiller

🐉 nanoMuse 1.0.9 “Tiller”: a fix release the same day as Crew. The desktop starts again when you are signed in, the relay's console loads on a large record, and the runtime takes a budget for a task and recalls from the whole memory store.

1.0.8 went out this morning, and its desktop did not start for anyone who was signed in. The plugin pointed the nanoMuse Cloud provider row at the loopback door it opens for the relay and waited for that settings write while the plugins were still starting; the write waits for the plugins, so the Host never announced its address and the window sat on Starting… for good, with nanoMuse is still starting every ten minutes (#701, fixed in #703). A fresh install was never affected, which is why the release check passed; everyone who had used 1.0.7 or signed in was. The same day the hosted relay's console stopped loading: the Usage page's table of the turns people ran on keys of their own read a week of them from the record itself, where a turn's provider and cached count sit behind its request and answer, and on 40 GB one call took minutes while holding the read connection's lock, so every page waited behind it (#708). Both are fixed here, together with three runtime changes that landed in between: a task can be given a budget and recall reads the whole memory store, both by @hobostay (#697, #696, for #685), and a contact's card folds its long lines, by @Yicheng-Mark (#702). Nothing changed on the phones; they move to 1.0.9 so every device reads the same version.

Highlights

• The desktop starts again when you are signed in. The loopback door now asks for the port it had last, so the provider row is usually right as it is; when it is not, the row is rewritten once the Host is up, without being waited for. If your 1.0.8 sits on Starting…, quit it and install 1.0.9 over it: your settings, your chats and your sign-in stay where they were, and nothing else is needed (#703, #701).
• The relay's console loads on a large record. The relay keeps the figures of a turn run on a key of the person's own in one small row (own_figures: account, time, provider, model, the three token counts), written with the turn and removed with it; the Usage page's table reads those rows in milliseconds instead of walking the record. The own turns kept before this version are filled in by a paced backfill after the restart, 200 a page, and the usage answer says own_keys_pending while it runs (#708).
• A task can be given a budget: tokens, money, time, and the size of one request. Off unless set. [agent.budget] in config.toml takes max_total_tokens, max_cost_usd (with your own per-million rates) and max_seconds; a task that reaches one stops with a sentence that says which, and the turn's usage goes to the audit log as a task_budget entry, only when a limit is set or reached. agent.max_context_tokens caps the approximate size of one request: tool results are shortened to a labelled head and tail and old exchanges dropped as whole groups; the saved conversation keeps the original text. By @hobostay (#697, #685); docs/runtime-budgets.md (github.com) has the details.
• Recall searches the whole memory store. Keyword search and recall by meaning read every memory, not only the newest 1,000 the listing shows, and a near-duplicate is found anywhere in the store, through the same search index, so a store with years of memories answers as fast as a new one. By @hobostay (#696).
• A contact's card folds its long lines at 75 octets. render_vcard wrote a long Chinese note as one oversized line, past what RFC 6350 allows, so a strict importer could reject or truncate it; the card now folds with the UTF-8-safe cut the calendar's lines already use, and parses back without loss. By @Yicheng-Mark (#702).
• TestFlight. Build 31 (1.0.8) was uploaded this morning and handed to the external group nanoMuse Beta for Apple's beta review; 1.0.9 goes up as build 32 to the same group and review. On the phone the two are the same app.

Upgrade Notes

• Android installs over 1.0.8 and keeps your data. nanoMuse-1.0.9-arm64.apk (Android 8.0+, arm64; versionCode 52) is signed with the same key as every version before it. Verify with sha256sum -c nanoMuse-1.0.9-arm64.apk.sha256. Nothing changed on the phone in this version; installing it there can wait.
• iPhone and iPad come through TestFlight. Build 32 (1.0.9) is handed to the external group when it is uploaded and reaches the public link once its review has passed, the internal testers before that; until then the link installs the newest build that passed.
• The desktop installers are built by CI from the tag v1.0.9. Install over 1.0.8; your settings stay. The Mac packages are not notarized: the first time, open the app from System Settings → Privacy & Security → Open Anyway (or right-click → Open). The Windows package is not signed: click More info and Run anyway once. On Linux prefer the .deb; the AppImage needs FUSE (--appimage-extract-and-run without). They arrive a little after the APK, and SHA256SUMS-desktop.txt lists every checksum. A 1.0.8 on Windows that never finished starting cannot offer the update from its corner menu, so download the installer.
• The relay is 0.31.1; a 1.0.8 client works against it unchanged. For operators: the first start after the upgrade creates own_figures and a backfill fills it for the own turns already kept, in the background, 200 turns a page with a pause after each page; about fifteen minutes for a hundred thousand own turns on the hosted relay. Until it is through, the Usage page's own-key table is short of the older turns and the answer carries own_keys_pending: true. No new setting. cloud/README.md (github.com) has the details.
• The runtime's settings are the same unless you add a budget. [agent.budget], [gui.budget] and agent.max_context_tokens are new and off until set; nothing else in config.toml changes.
• Where to get it.

In our measurements GitHub's own downloads are quick from China as well; if they fail where you are, the same files are on nanomuse.cn/dl/v1.0.9/ within fifteen minutes.

Community

nanoMuse is open source, free and non-profit. Sign in with a phone number or an e-mail and you get a starting allowance; the developer pays for it. The account page shows what is left and how to add more. When it is gone, use your own key or a plan you already pay for (how). With an account, nanoMuse Cloud keeps the record of your conversations with its models and the turns your own key answered, and what was decided around each turn as codes and never as words; your devices and the person running the relay can read it, nobody else; one tap under Data controls deletes it, and nothing is sold (privacy policy); delete the account whenever you want. The same relay runs on a server of yours: docs/self-hosting.md (github.com).

Thanks to @yklykl530 for reporting the desktop that would not start, with the log that named the cause (#701), to @hobostay for the task budgets and the whole-store recall (#697, #696), to @Yicheng-Mark for the card's folding (#702) and to @poppis-xin for watching the TestFlight build (#700). The roadmap says where help is wanted, and docs/parity.md (github.com) says what each client has. Open an issue · send a pull request · Discussions · Discord · star the repo; if it is useful to you, a star helps others find it.

Based on OpenMinis 1.13 (GPL-3.0), modified since 2026-09-24. The complete corresponding source of this build is tag v1.0.9 plus the android/deps/proot submodule (nano-muse/proot); the desktop installers and the Docker image are built by CI from the same tag. The whole repository is GPL-3.0-or-later. nanoMuse Desktop carries DeepSeek Harness unmodified, with its licence files inside; harness in the name is the word, not DeepSeek's. The chat apps follow nanobot's design (MIT); the desktop's operator is ported from UI-TARS-desktop (Apache-2.0; THIRD_PARTY_NOTICES.md). nanoMuse is not affiliated with Meta; Muse is a trademark of Meta Platforms, Inc. The desktop follows what Muse's app looks like and does, written down from using it; none of Meta's assets, code or content is in it.

What's Changed

• fix(contacts): a long note folds at 75 octets instead of one oversized line by @Yicheng-Mark in https://github.com/nano-muse/nanoMuse/pull/702
• fix(desktop): the 1.0.8 desktop starts again when signed in (#701) by @lgy0404 in https://github.com/nano-muse/nanoMuse/pull/703
• fix(relay): read the own-key usage table from a small figures table by @lgy0404 in https://github.com/nano-muse/nanoMuse/pull/708
• feat(runtime): share task budgets and log context truncation by @hobostay in https://github.com/nano-muse/nanoMuse/pull/697
• fix(memory): retrieve facts beyond the listing limit by @hobostay in https://github.com/nano-muse/nanoMuse/pull/696
• build(release): 1.0.9 Tiller by @lgy0404 in https://github.com/nano-muse/nanoMuse/pull/711

New Contributors

• No first-time contributors in this release; yours could be the next one: good first issues.

Contributors

@hobostay · @lgy0404 · @Yicheng-Mark

Full Changelog: https://github.com/nano-muse/nanoMuse/compare/v1.0.8...v1.0.9

Android APK refresh: 2026-10-31

The Android APK was replaced to correct context budgeting and compaction recovery in long conversations. It remains version 1.0.9 (52), signed with the same release key. Download and install it over the existing app to receive this fix; the unchanged version does not trigger an automatic update. Built from 994f0afd, merged in #723. For [#719].

Android 安装包已替换，修正了长对话的上下文预算和压缩恢复处理。版本仍为 1.0.9（52），使用同一发布签名。请重新下载并覆盖安装；版本号未变，不会触发自动更新。源码为上方提交，修复已通过 [#723] 合入主分支。