Remotes get a pin of their own
Your favourite direct remotes and orgs can now hold a spot above the chatter. The choice follows your account from desktop to phone, with no setting to hunt for.
You open the … menu on a direct remote and choose Pin, and the row hops above the newer conversations on the Remotes page. Reload and it is still there. Sign in on your phone and the same remote is already sitting at the top. Same story for an org.
Credit goes to xHeaven, who gave every membership its own pin timestamp. It is one nullable column, nothing more. The inbox loads 30 conversations at a time, pinned ones first, and inside each group the newest message leads. Because pins and the page cursor are read together, another device flipping a pin mid-scroll cannot scramble your list, and a failed save leaves the old order alone and offers a retry. Stash a pinned remote and the pin waits for it to come back.
One catch. Pins do not hold their order among themselves. They sort by latest message, so a pinned org that gets busy overnight climbs above the pin you set first, and there is no drag handle to argue with it.
Key files · #1088
- app/
Actions/ UpdateConversationPin.php - app/
Queries/ ConversationsQuery.php - database/
migrations/ 2026_10_23_203507_add_pinned_at_to_conversation_participants_table.php - resources/
js/ chat.tslib/ - resources/
js/ conversation-actions.tsxcomponents/ chat/ - app/
Http/ ConversationPinController.phpControllers/ - routes/
web.php - app/
Actions/ CreateExport.php