| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| imsg-macos.zip | 2026-10-23 | 4.2 MB | |
| imsg-linux-x86_64.tar.gz | 2026-10-23 | 29.9 MB | |
| SIGNING-MANIFEST.json | 2026-10-23 | 373 Bytes | |
| RELEASE-NOTES.md | 2026-10-23 | 847 Bytes | |
| SHA256SUMS | 2026-10-23 | 430 Bytes | |
| ASSET-INVENTORY.json | 2026-10-23 | 553 Bytes | |
| README.md | 2026-10-23 | 847 Bytes | |
| v0.19.1 source code.tar.gz | 2026-10-23 | 619.9 kB | |
| v0.19.1 source code.zip | 2026-10-23 | 848.8 kB | |
| Totals: 9 Items | 35.5 MB | 1 | |
0.19.1 - 2026-10-22
Highlights: Keep the IMCore bridge injected across reboots with an opt-in login agent, report your own account as the sender of outgoing 1:1 messages, and stop the bridge debug log from growing without bound.
- Rotate the injected helper's
.imsg-bridge.logat 8 MiB to.imsg-bridge.log.1, matching the event log, so long-running Messages hosts no longer accumulate gigabytes of handler tracing (#362). - Report your own account instead of the recipient as
senderon outgoing 1:1 messages, reactions, and reaction events, and match--participantsagainst that same sender (#358, thanks @regaw-leinad). - Add an opt-in bridge login agent with
imsg launch --install-agentto restore injection after reboots and periodically repair missing or stale helpers, with configurable intervals and bounded logs (#363).
