amadan
ios+mac: mint native 0.9.3 (17) — the changelog entry for the build (#1496)
One entry per build, added by the mint rather than the feature PRs: a native change only reaches members when a build is downloadable. Since 0.9.2 (16), all of it thread work: Reply and threads separated so nothing joins a thread by accident (#1490); the thread panel as one scrolling list with its root at the top (#1492); a tapped notification landing on THAT message and the channel composer keeping the caret on activation (#1489); Convert to thread for a chain that sprawled down the chat (#1493); and a Threads list in the chat kebab (#1494). Excluded as invisible to members: the Mac feed's composer-band re-pin (#1488) is a fix to a fix from the same unreleased window. Claude-Session: https://claude.ai/code/session_01EXy6kzmYE9rChy3KgciJvZ
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
1 file changed,
+17
−0
changelog/2026-08-30-native-0-9-3.md+17 −0
diff --git a/changelog/2026-08-30-native-0-9-3.md b/changelog/2026-08-30-native-0-9-3.md| new file mode 100644 |
| index 0000000..49ca763 |
| --- /dev/null |
| +++ b/changelog/2026-08-30-native-0-9-3.md |
| @@ -0,0 +1,17 @@ |
| +🤖 New iPhone and Mac apps (0.9.3), mostly about threads. Reply and threads are |
| +now two separate things: a plain reply quotes a message and stays in the chat |
| +where you can see it, and a thread only ever starts because you chose "Reply in |
| +thread" — nothing gets pulled into one by accident. A thread reads as its own |
| +small conversation, the message it's about sitting at the top of it. |
| + |
| +When a conversation has already sprawled down the chat, **Convert to thread** |
| +on the message it started from tucks the whole run of replies into a thread, |
| +leaving the original in place with a count under it. And the chat's ⋯ menu |
| +gains **Threads** — every thread in that chat, most recent first — so a thread |
| +you meant to come back to is somewhere you can find it rather than somewhere |
| +you have to remember. |
| + |
| +Tapping a notification for a reply now takes you to that reply, opening its |
| +thread if that's where it lives, instead of dropping you at the bottom of the |
| +chat. And coming back to the app with a thread open puts the cursor back in the |
| +main conversation, not the thread. |