On this page
Google Messages has swapped the direction of its swipe gestures, and your muscle memory is about to be wrong. Swiping left inside a conversation no longer starts a reply. It now pulls the whole thread across to reveal every message timestamp, along with the RCS encryption status for that conversation.

What the new Google Messages swipe gestures do
Replying to a specific message is now a right swipe on that bubble. The old behaviour was a left swipe, so the two actions have effectively traded places.
The timestamp view is the more useful half of the change. Previously you had to tap individual bubbles to check when each one landed. A single left swipe now exposes the times for the entire thread at once. That beats checking one bubble at a time when you are scrolling back through a long conversation.
Tapping a message still works the way it always did and shows read-receipt information. The app also flashes a brief timestamp hint on tap, which looks like a nudge to help people find the new gesture.
Rollout so far
The change is showing up in Google Messages version 20260910_03_RC02. It is described as rolling out widely, but it is not consistent across the app yet.
So far it turns up mainly on individual message Details pages and on the homepage, rather than everywhere at once. Google has not given a timeline for finishing the rollout, so a device on the same app version may still behave the old way.
A reversal with no heads-up
Flipping the direction of an established gesture is a small change with an outsized effect on habit. Reply is one of the most-used actions in a messaging app, and nothing in the app announces that it moved. The change was spotted in the wild rather than documented. That leaves people to work out on their own why a reply swipe suddenly shows a wall of timestamps.
It follows another recent interface pass on the app. Earlier this week, Google Messages began rolling out a redesigned floating long-press menu with selective copying. That is a separate mechanic from this gesture swap.
Sources: 9to5Google, Android Authority
