# Pinned chats, queue and alerts on every device

> In Shuriken 5.1, pinned chats, the queue and notifications stay in step on every device. How the sync works, and where we're still improving it.

Source: https://shuriken.sh/blog/sync-in-step

In Shuriken 5.1, pinned chats, the queue and notifications stay in step on every device. How the sync works, and where we're still improving it.

[Update](https://shuriken.sh/blog) By Shuriken Updated 14 November 2026 4 min read

**Contents**

In Shuriken 5.1, pinned chats, the queue and notifications stay in step on every device. Pin a chat on your laptop and it's pinned on your phone. Queue three messages from the desktop and your phone shows three, not one. Answer an approval on one device and the others stop asking.

That should always have been true. For a while, it wasn't, and this post is about why and what we changed.

## Why we went back to sync #

The report that started it was blunt. One device showed a chat with six things running and one message queued. Another device, same account, same chat, showed one running and nothing queued. Both were sure of themselves.

When devices disagree, you stop trusting all of them. You start opening the laptop to check what the phone said, which defeats the point of a phone.

## How sync works in Shuriken #

Shuriken has an unusual shape, so here it is in one picture.

- Your agents run on your machines. A chat lives on the computer or server that runs it. Its history, its queue, whether it's pinned and whether it needs you are all kept there. We wrote about why in [Your agents run on your machines, not ours](https://shuriken.sh/blog/agents-on-your-machines).
- Every other device is a window onto that computer. Your phone, a second laptop or a browser tab doesn't keep its own version of the queue. It shows what the computer says.
- The messages between them are sealed. What your devices send each other is end-to-end encrypted. Our cloud signs you in, links your devices, relays the sealed messages and stores your sign-ins and API keys sealed. It can't read your chats, the queue, changes or voice. It does keep a key that opens your vault, so any sign-in opens it with nothing asked, and it could read your sign-ins, API keys and project and device names. The [security page](https://shuriken.sh/security) lists exactly what it does and doesn't keep.

So "sync" in Shuriken doesn't mean copying data to a server and back. It means every device asking the same computer and getting the same answer.

## What was going wrong #

Three things, mostly.

The computer stalled, and every stall looked like a disconnect. In 5.0, the background service could freeze on a very long chat history. While it was frozen it couldn't answer anyone, so every connected device decided the computer was gone, reconnected, and asked for everything again. Each device came back at a different moment and saw a slightly different picture. That's also where the "Connection lost" messages came from: [here's that story](https://shuriken.sh/blog/why-chats-said-connection-lost).

Devices worked some numbers out for themselves. A count like "6 running" was partly calculated on each device from what it had seen. Two devices that had seen different things came up with different counts.

A message sent twice could count twice. If your phone lost signal mid-send and tried again, the queue could end up with a ghost copy on one screen.

In Shuriken whatever you type while the agent works waits in a queue you can edit and reorder.

[Try Shuriken](https://shuriken.sh/)

## What 5.1 changes #

- The computer keeps answering. Long chat histories load in pieces, so the background service stays responsive while it reads them. No more freeze, and no more stampede of devices reconnecting at once.
- The computer decides, devices show. What a count or a badge depends on is decided on the computer that runs the chat and sent to every device as is. Two devices looking at the same chat read the same answer.
- Pins live with the chat. A pin is stored on the computer that runs the chat, so every device sees it, including the one you just picked up.
- Each queued message has its own id. If your phone sends a message, loses the connection and sends it again, the computer adds it once.
- Alerts follow the chat. Whether a chat needs you comes from the computer running it, so once you've answered on one device, the others stop showing it.
- Busy isn't gone. A computer that is slow for a moment is no longer shown as unreachable.

## Honest note: we're still working on it #

Sync across devices is one of the hardest parts of Shuriken, and 5.1 is a big step, not the last one. You may still catch two screens out of step, most likely right after a computer wakes up or a connection comes back. Reload and they should agree.

If they don't, please tell us. Use Report a bug in the top bar, say which devices showed what, and attach a screenshot from each if you can. "What's new" will tell you when your bug is fixed. Reports like that one, six running on one screen and one on another, are how we found these causes in the first place.

## Try it #

Update the computers and servers that run your agents to Shuriken 5.1, then open the same chat on your laptop and on your phone at app.shuriken.sh. Pin it on one and watch it show up on the other. The [phone feature page](https://shuriken.sh/features/phone) has more on following your agents from anywhere, and if you're new, [try Shuriken](https://shuriken.sh/) to get started.

Share

[X](https://x.com/intent/post?url=https%3A%2F%2Fshuriken.sh%2Fblog%2Fsync-in-step&text=Pinned%20chats%2C%20queue%20and%20alerts%20on%20every%20device)[LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fshuriken.sh%2Fblog%2Fsync-in-step)[Hacker News](https://news.ycombinator.com/submitlink?u=https%3A%2F%2Fshuriken.sh%2Fblog%2Fsync-in-step&t=Pinned%20chats%2C%20queue%20and%20alerts%20on%20every%20device)[Reddit](https://www.reddit.com/submit?url=https%3A%2F%2Fshuriken.sh%2Fblog%2Fsync-in-step&title=Pinned%20chats%2C%20queue%20and%20alerts%20on%20every%20device)[E-mail](mailto:?subject=Pinned%20chats%2C%20queue%20and%20alerts%20on%20every%20device&body=https%3A%2F%2Fshuriken.sh%2Fblog%2Fsync-in-step)

## Frequently asked questions

**How does Shuriken keep chats in sync across devices?**

The computer that runs a chat holds its truth: the history, the queue, the pins and whether it needs you. Your other devices show what that computer says, through end-to-end encrypted messages our cloud relays.

**Can Shuriken's cloud read my chats or my queue?**

Not your chats. Chats, the queue, changes and voice travel end-to-end encrypted between your devices, and the cloud stores no code or chats. Sign-ins, API keys and project names are stored sealed in your account, and our cloud keeps a key that opens your vault.

**Do I need to update every device?**

Update the computers and servers that run your agents to 5.1. The web app picks up the new version when you reload it.

**What should I do if two devices disagree?**

Report a bug from the top bar and say which devices showed what. Include a screenshot of each if you can. What's new tells you when it's fixed.

Queue

Type while your agent works.

Messages wait their turn. Repeat one, attach files, reorder them, or Steer one into the running turn.

[Try Shuriken](https://shuriken.sh/)

[How it works](https://shuriken.sh/features/queue)

## Keep reading

- [How we keep your data safe: Story 28 Oct 2026 9 min read A security engineer told us he wouldn't use a closed-source app he couldn't check. What we changed, what our cloud can't read, and what it still can.](https://shuriken.sh/blog/security-what-the-cloud-sees)
- [How our encryption works, with the code: Update 1 Nov 2026 4 min read Every key Shuriken makes, the relay handshake, what is sealed to whom and the known limits, on one page with the encryption code read at each build.](https://shuriken.sh/blog/how-our-encryption-works)
- [What's new in Shuriken 5.1: Update 27 Oct 2026 16 min read Shuriken 5.1 adds sign-in with Google, Apple or an email code, Allow and Always allow at a MacBook's notch, and billing and fuel in Sources.](https://shuriken.sh/blog/shuriken-5-1)
- [Shared projects beta: share a project with a friend: Update 27 Oct 2026 3 min read Shared projects (beta) let a friend work in one of your projects on your computer, with your files and your Claude. Both sides opt in; sharing needs Pro.](https://shuriken.sh/blog/shared-projects-beta)
- [Your agents on your phone, from the browser: Update 27 Oct 2026 4 min read Open app.shuriken.sh in any phone browser and add it to your home screen: every chat, the queue, Changes and voice. Browsers never count as devices.](https://shuriken.sh/blog/phone-web-app)
- [A notification when a chat needs you: Update 27 Oct 2026 3 min read Get a desktop notification when Claude Code or Codex finishes, asks a question or wants approval. The DIY hooks route, and what Shuriken does for you.](https://shuriken.sh/blog/desktop-notifications)
- [Shared projects: who gets what access: Update 27 Oct 2026 4 min read Shared projects are an opt-in beta in Shuriken 5.1. The trust model: what a member can reach, the controls you keep, and who to invite.](https://shuriken.sh/blog/shared-projects-trust)
- [Why our phone apps are native, not a web view: Planned 16 Nov 2026 4 min read Our phone apps go native in November 2026, because a web view is weak at the keyboard, gestures, sheets, haptics and push. The web app stays.](https://shuriken.sh/blog/why-native-not-web)

## Free tools

- [Claude limit reset tracker](https://shuriken.sh/tools/limit-resets/claude)
- [Codex limit reset tracker](https://shuriken.sh/tools/limit-resets/codex)
