[ald3b]

Why

"Mark as Unread" on a chat brings its dot back, but not the place to pick up from. When you read a long answer and want to come back to it later, the next open lands at the latest message with no "New" line, so you have to find that reply again yourself.

What changed

Every sent message's menu now has Mark as unread, right after Reply:

• The chat's unread dot comes back straight away.
• The chat stays unread for the rest of the visit, even though it's still on screen.
• The next time you open it, the "New" divider sits above the first reply from that message on. On a reply, that's the reply itself. On your own message, it's the reply that followed it.
• Live progress and subagent rows can't be marked, because they aren't stored messages.

Server.

• threads/markUnread takes an optional messageId. With it, the thread is marked unread and the read cursor moves to just before that message.
• A message that isn't in the thread is rejected as not found, so a stale or foreign id can't move the cursor.
• Without messageId, the call behaves exactly as before.

Shared. One helper in @rakazo/core decides which messages offer the action, so mobile and web agree.

Mobile.

• The native context menu shows the item second, after Reply, with the message.badge symbol (an outline speech bubble with a dot, matching the menu's other outline icons).
• The Android action sheet and the VoiceOver actions get the same item in the same place.
• While the chat is held unread, the screen skips its usual mark-read on focus, so the dot doesn't clear under you. Leaving or switching chats ends the hold.

Web and desktop.

• The message's More menu shows the item after Reply, with a speech-bubble-with-dot icon.
• The More menu now sizes to its content instead of its icon button, so labels stay on one line.

New copy. "Mark as unread", the menu item's label and accessible name.

• It's needed because the item is the only way to set the resume point at a message. An icon alone in a text menu would be ambiguous.
• The chat list's existing "Mark as Unread" is title case. The message menu's other items use sentence case ("Speak message", "Select text"), so this label follows the menu it sits in.
• It appears only inside the message menu, which is already a reveal-on-demand surface.
• It's translated in the mobile catalogs (de, ru, zh, nl) and in every web catalog, reusing each locale's existing "Mark as Unread" wording.

How it was tested

On an iOS 27 Simulator with a Debug build against a local server, and in Chromium against the same kind of server. The test account had a bot chat with two answered questions, all read. Light and dark mode were both checked.

• Before the change: long-pressing a reply showed Reply, Copy, React, Quote, Speak message and Select text. There was no way to mark a single message unread.
• After:
  • Long-pressing a reply shows Reply, Mark as unread, Copy and React, then Quote, Speak message and Select text. Light and dark mode were both checked.
  • Long-pressing the user's own second question shows the same item in the same place.
  • Choosing it there and going back shows the chat with its unread dot in the chat list.
  • Opening the chat again shows the "NEW" line between that question and the bot's reply to it. The first exchange is above it.
  • On web, the More menu lists Reply, Mark as unread and Copy on one line each. Marking the first reply and reopening shows the divider above that reply. Marking the user's second question and reopening shows the divider above the reply to it.

Unit tests. Each new test fails without this change.

• Server: marking from a message sets the thread unread and moves the cursor to just before it, so the next markRead reports that message as the start. A message that isn't in the thread is refused and changes nothing.
• Shared helper: any stored message, the user's own included, can be marked, but live progress and subagent rows can't. Marking the user's message starts the divider at the reply after it.
• Mobile menu: "Mark as unread" comes right after Reply, only when asked for, and not in the inline group.

Full suites.

• The mobile, API, core and contracts suites pass.
• On a local Node version with built-in web storage, three web files that read localStorage fail. They fail the same way without this change, and they pass with that storage turned off.
• Typecheck and lint pass.

Web e2e: "marking a message unread brings the chat back with New above the reply from there" (new).

• Setup: a bot answers two questions and the chat is read.
• The first reply's More menu lists Reply, Mark as unread and Copy. Choosing Mark as unread brings the chat's unread state back.
• Reopening the chat shows the divider directly above that reply.
• The same item on the user's second question puts the divider above the reply to it.
• It captures message-mark-unread-menu and message-mark-unread-divider for CI.

Mobile. CI can't capture the native context menu; the iOS results above come from a simulator.

Not in this PR

• The off-screen unread count in the chat list.

That is a separate change.

🤖 Generated with Claude Code

[vercel]

@ald3b is attempting to deploy a commit to the Inbox Zero Team on Vercel.

A member of the Team first needs to authorize it.

[greptile-apps]

Confidence Score: 4/5

[Medium impact] The change reaches unread behavior across web, mobile, and the thread API.

The delayed-read finding remains partly unresolved, so the PR should not merge yet.

Findings

1.  Delayed reads erase reminders ▶

Summary

Adds “Mark as unread” to stored messages on mobile, web, and desktop.

• Chats can resume unread from a chosen message.
• Mobile message menus can mark a chat unread.
• Web message menus can set where a chat resumes unread.

Diagram

sequenceDiagram
  participant User
  participant Client
  participant API
  participant Thread
  User->>Client: Mark message unread
  Client->>Client: Hold unread for this visit
  Client->>API: Queue markUnread with messageId
  API->>API: Check message belongs to thread
  API->>Thread: Set unread and cursor to message seq minus one
  User->>Client: Reopen chat
  Client->>API: Mark read
  API-->>Client: Return saved cursor
  Client->>Client: Show New above first reply after cursor

Loading

_{Reviews (4) · Last reviewed commit: "feat: mark a message as unread from its ..." · Reviewed by Greptile}

[github-actions]

Playwright screenshots

Feature frames for this PR:

• message mark unread divider (new)
• message mark unread menu (new)
• chat unread divider dark (changed)
• chat unread divider read (changed)
• chat unread divider (changed)

Open screenshot gallery · Dashboard · CI run

Updated for commit ddba5cb.