یہاں OmO (Baseline) کے 9 ورژن درج ہیں، 10 نومبر، 2026 سے لے کر موجودہ 5.1.79 تک۔ ہر ورژن پبلشر کی اپنی انسٹالر فائلوں سے منسلک ہے۔
| ورژن | تاریخ | سائز | فائلیں |
|---|---|---|---|
| 5.1.79تازہ ترین | 19 نومبر، 2026 | — | 64 بٹ پورٹیبل ریلیز نوٹسFixed
- The /remote close in the TUI follows thread_close's close contract (#14234). A close refused because the thread has messages it has not read names /remote close <session> --force and lists those messages, or says the ids are unavailable on that device's engine. The picker then offers "Close anyway". A forced close lists the messages it dropped. The refusal's details.reason is the engine's own reason (turn_active or work_pending). (#14246, fixes #14245) (#14248)
- Thread tools: a command for a thread whose session parked on another device after it was listed no longer fails unsupported with advice to update omo on that device. The device service answers such a command route_unlisted (its host no longer lists that session, so nothing was sent to it). thread_close now answers closed: false, reason: "not_live", and the other thread tools answer not_resumable, as for a session that ended there. A create, or a reopen's session-file lookup, refused that way is host_unavailable, with a retry. (#14237, fixes #14233) (#14248)
- The cold-wake session host unit (and every other unit or plist the cold-wake install writes) is now written 0644 under any umask. Under umask 077 it was written 0600, because a file's creation mode is masked by the umask; the mode is now set explicitly before the file is moved into place. (#14249, fixes #14247) (#14248)
- A cold-wake unit or plist an earlier build already left 0600 is set back to 0644 the next time the install (or a refresh to a newer runtime) finds its content unchanged, with no reload or restart. A file this user cannot change the mode of (another owner's, or on a read-only filesystem) is left as it is and the install still succeeds. (#14249) (#14248)
Changed
- thread_close no longer drops messages a thread has not read unless you ask it to. Before, it always interrupted the session and silently dropped any messages queued behind its run. Now:
- A busy thread with unread messages is refused turn_active. The refusal names those messages (pending_deliveries) and gives the force option.
- thread_close({ thread, force: true }) closes it anyway.
- Every close result carries dropped_deliveries, the messages it handed back unread (an empty list when there were none).
- An idle thread still closes without force, even when an interrupted run left messages stranded (#14169); those are listed too.
- On a device whose engine cannot name its queued messages (older than code-yeongyu/senpi#7006), a default close never interrupts. It says the message ids are unavailable there, and force: true still closes it.
- omo remote close takes --force and reports the dropped messages as well. (#14242, fixes #14234) (#14248)
Added
- The desktop can ask OmO which model each category and agent runs. A new read-only extension request, omo.modelRouting.resolve, answers the model every category (under its canonical name) and every task agent would spawn on, using the same resolvers a task call uses against the session's project config, model registry and sign-ins, and says whether that model came from your omo.json or from OmO's defaults. (#14025)
- 822bd92303 Merge pull request #14290 from code-yeongyu/release/v5.1.79-source-state
- fd7c18a9de Merge pull request #14286 from code-yeongyu/ratchet-no-ignore
- 2d1b133359 fix(lint-ratchet): the lint ratchet refuses a file oxlint skipped, so a config's ignorePatterns cannot hide one either
- 0bed7304a4 fix(lint-ratchet): lint ratchet runs oxlint with --no-ignore, so an ignore file cannot hide a file from it
- abfb5be796 Merge pull request #14248 from code-yeongyu/release-train/omo-20261119-thread-train-3
- 7559752bf0 Merge pull request #14267 from code-yeongyu/fix/11845-progress-aware-spawn-budget
- 5e628bcd6f Merge pull request #14268 from code-yeongyu/feat/no-bun-mock-module
- c7367ed9aa test(omo-native): review fixes for the progress-aware budget
- 07b5060b91 test(script): cover createRequire and members read off a loaded bun:test
- 42ef9ed14e fix(script): no-module-moc |
| 5.1.78 | 18 نومبر، 2026 | — | 64 بٹ پورٹیبل |
| 5.1.77 | 18 نومبر، 2026 | — | 64 بٹ پورٹیبل |
| 5.1.75 | 16 نومبر، 2026 | — | 64 بٹ پورٹیبل ریلیز نوٹسFixed
- omo remote devices shows this device offline while its device service is not connected, and omo remote sessions --device naming a device the account does not have reports it instead of listing nothing. (#13916)
- Memory sync's own test suite no longer fails a later, unrelated test when one test times out while a sync cycle is still running: device teardown in the tests now stops the engine and waits for that cycle before removing its files, and the push-bounded test waits on the cycle instead of a fixed 30 s budget. (#13887, fixes #13680)
- The first memory sync cycle after signing in no longer fails with "the device's sign-in token could not be read or refreshed" when the system keychain briefly reads nothing. That one empty read is now checked again before sync treats the sign-in as gone; signing out still stops sync at once. (#13879, fixes #13739)
- Regenerating the computer-use prelude (bun run generate in senpi-desktop-prelude) now runs its generated method tables through bun fmt, so prelude.js, its index.ts allowlist and the desktop protocol tier tables stay formatter-clean instead of reverting to unformatted output at every release regeneration. The published prelude JavaScript is the formatted copy again. (#13855)
Changed
- A memory sync capture that receives files from other devices no longer scans every known file once per received file, so a large memory catching up on many incoming files stays fast. (#13862)
- 2ec6b5d944 ci(publish): operator-built darwin artifacts for the v5.1.75 release (workflows from #13928, merge 8f8f4d1076)
- 89bbf71eda Merge pull request #13887 from code-yeongyu/fix/memory-sync-push-bounded-test-13680
- 598ec2344c Merge pull request #13862 from code-yeongyu/fix/memory-sync-capture-known-set
- c3304b602a Merge pull request #13879 from code-yeongyu/fix/memory-sync-first-receive-token-13739
- 83422463da Merge pull request #13870 from code-yeongyu/docs/13855-pin-comment-wording
- 9ed8307f17 Merge origin/dev into fix/memory-sync-first-receive-token-13739
- f47c976114 chore(changes): the fragment links this PR (#13887)
- bc1abdab02 Merge origin/dev into fix/memory-sync-push-bounded-test-13680
- 8c3f1a1502 Merge origin/dev into fix/memory-sync-capture-known-set
- 821eafd5a2 Merge remote-tracking branch 'origin/dev' into docs/13855-pin-comment-wording
- 31e08cb319 Merge pull request #13916 from code-yeongyu/rt/13414-client-parity
- 984088bb87 Merge origin/dev into fix/memory-sync-first-receive-token-13739
- 9bd2382748 Merge pull request #13855 from code-yeongyu/fix/prelude-fmt-clean-regen
- f865a7afc5 Merge pull request #13918 from code-yeongyu/ci/platform-decision-body-comment
- ebeaac0e72 Merge remote-tracking branch 'origin/dev' into fix/prelude-fmt-clean-regen
- 03e4b7e8c5 ci(pr-platform-decision): restore why the PR body is read from the event file (#13859)
- f9f610d53a Merge pull request #13912 from code-yeongyu/ci/platform-decision-one-cap
- add0ca2bc2 docs(changes): fragment for remote client read-path parity (#13916)
- bca0d62dde Merge branch 'dev' into rt/13414-client-parity
- 72cecaeec7 fix(remote): the client's devices.list and sessions.list carry #13402's CLI behaviour (#13414)
- 02915ac7ad Merge remote-tracking branch 'origin/dev' into fix/prelude-fmt-clean-regen
- eac1e0af78 ci(pr-platform-decision): one file-cap number, owned by the classifier (#13859)
- 86949060a2 Merge origin/dev into fix/memory-sync-capture-known-set
- d81b80ade6 Merge remote-tracking branch 'origin/dev' into fix/prelude-fmt-clean-regen
- 2fc39fc83f Merge origin/dev into fix/memory-sync-first-receive-token-13739
- 00026f3825 chore(changes): the fragment carries this PR's number (#13887)
- 223aefb941 test(memory-sync): teardown waits for a running cycle; push-bounded waits on the cycle
- ea7660546f fix(memory-sync): re-read a transiently empty credential once before retiring the capture
- 4e51d430c6 Merge remote-tracking branch 'origin/dev' into fix/prelude-fmt-clean-regen
- 7560233dd2 docs(desktop-prelude) |
| 5.1.73 | 16 نومبر، 2026 | — | 64 بٹ پورٹیبل |
| 5.1.72 | 15 نومبر، 2026 | — | 64 بٹ پورٹیبل |
| 5.1.71 | 15 نومبر، 2026 | — | 64 بٹ پورٹیبل |
| 5.1.70 | 14 نومبر، 2026 | — | 64 بٹ پورٹیبل |
| 5.1.68 | 10 نومبر، 2026 | — | 64 بٹ پورٹیبل ریلیز نوٹسRelease binaries may be up to 210 MiB. The 5.1.67 publish stopped on Linux x64 because its binary measured 209,889,456 bytes, 174,256 bytes over the 200 MiB per-binary budget (5.1.66's was 209,664,176). The budget moves to 210 MiB, about 5% above that size, and still fails any release that goes past it; the 5 MiB headroom warning is unchanged. (#13052) (#13052)
- 8ed3326361 Merge pull request #13052 from code-yeongyu/fix/binary-size-budget-210mib
- 5e5c60b976 docs(changes): add the 13052 release-note fragment
- 957de2b66d fix(release): raise the per-binary size budget to 210 MiB
- 42d5746e72 Merge pull request #13047 from code-yeongyu/release/v5.1.67-source-state
- 3b88a0027f Merge pull request #13005 from code-yeongyu/fix/12989-endpoint-cache-at-resolve
- d26f4d7db4 Merge remote-tracking branch 'origin/dev' into fix/12989-endpoint-cache-at-resolve
- 245869b604 Merge pull request #12993 from code-yeongyu/fix/12989-credential-lock-torn-record
- 8ce72e7a64 Merge remote-tracking branch 'origin/dev' into fix/12989-credential-lock-torn-record
- bb340a0fa2 Merge pull request #12815 from code-yeongyu/fix/12801-file-backed-ps-snapshot
- 7a0e5b3d0c chore(train/omo-2): regenerate bundles at the train top on dev f922d6ac3a (#12944 #12949 #12815)
- 302b797899 Merge #12815 (4f50baaf95) into train/omo-2 (re-cut without #12351)
- 4c32820728 Merge #12949 (e6de1f0ebc) into train/omo-2 (re-cut without #12351)
- a463e158b6 Merge #12944 (e91165d545) into train/omo-2 (re-cut without #12351)
- 2215cc2d2b Merge origin/dev into fix/12989-credential-lock-torn-record
- d985fa7989 Merge pull request #12979 from code-yeongyu/fix/12978-credential-lock-account-home
- a4bdc347ce changes: fragment for #13005
- 60e17c02cd fix(thread): a published-id send reuses only an answered enumeration (#12989)
- 24f897c40c fix(thread): share one endpoint enumeration and start its cache window when it answers (#12989)
- f04cdf1f33 Merge origin/dev into fix/12978-credential-lock-account-home
- fa05c2702c Merge pull request #12975 from code-yeongyu/feat/12886-approval-wait-outcome
- 1acab30a24 changes: fragment for #12993
- 5515951be2 fix(service-auth): reclaim a torn credential lock record instead of holding it forever (#12989)
- 6874054d8f fix(service-auth): keep test CLI children on their own lock and run only System32 tools on Windows (#12978)
- e91165d545 Merge origin/dev into fix/914-tolerant-reply-decoders
- a777a723a8 Merge remote-tracking branch 'origin/dev' (#12953 merged standalone, 04ba4a7081) into train/omo-1
- 04ba4a7081 Merge pull request #12953 from code-yeongyu/feat/claude-fable-5-2
- a66d3d1ce1 fix(knip): export-check device-service-core test/local-api/event-examples.ts
- 0d993cd084 Merge #12953 (dc68e0fca5) into train/omo-1
- 0bb53e3451 Merge #12975 (3f95b9557c) into train/omo-1
- b221a27dde Merge #12954 (ffa66d41c1) into train/omo-1
- 4b35d367d7 Merge #12966 (06241b89e1) into train/omo-1
- 05dc774a1a Merge #12909 (cd21814199) into train/omo-1
- d14bda0040 Merge #12938 (06ebd08171) into train/omo-1
- cac87c0474 fix(service-auth): one credential lock per OS user on Linux, macOS and Windows, with a homedir fallback (#12978)
- 06ebd08171 Merge remote-tracking branch 'origin/dev' into fix/12853-follow-effective-mode
- 01cfed3293 fix(thread): a permission prompt (pendingDialogs) parks the receiver too, and a failed post-admission read keeps the probe's parked state (review MEDIUM + LOW, #12975)
- 5755bb8a52 Merge remote-tracking branch 'origin/dev' (#12922) into feat/12886-approval-wait-outcome
- 86441b3e66 Merge remote-tracking branch 'origin/dev' into feat/claude-fable-5-2
- 40856501af chore(changes): fragment for #12979
- cd21814199 Merge remote-tracking branch 'origin/dev' into fix/12908-canary-user-intervened
- 0763a352ca fix(service-auth): take the credential lock in the OS account's home, not $HOME (#12978)
- 363d0e34cf Merge commit '4543c85d49fab896634507a28fb3a47401521554' into fix/914-tolerant-reply-decoders
- d79bc6cc9a Merge pull request #12922 fro |