TL;DR — Anthropic made Cowork threads portable between desktop and phone, Shopify turned Quick Sale on everywhere it operates, and the POS app rebuilt its discount flow to cost fewer taps per sale. Three shipments, one pattern: the control surface moved into the merchant's pocket.
The theme
A good week to notice what hardware is no longer required to do serious work. The Cowork change lifts agent state off a single laptop and puts it on a server you can nudge from an iPhone on a sidewalk. Quick Sale kills the "do I need a card reader" question for any merchant outside the old Tap to Pay map. And the POS discount rewrite shaves seconds off a flow that a tablet-toting cashier runs twenty times a shift. Different products, same direction of travel: the thing you used to need a desk for is now something you do while walking.
The interesting part is not that mobile got more capable — that has been the trajectory for a decade. It is that all three updates treat the phone as the primary surface and the desktop as the optional one. Cowork's local VM still matters, but the thread context outlives the laptop going to sleep. Quick Sale treats payment links as the default and Tap to Pay as the regional upgrade. POS assumes the register is a handheld and redesigns the number pad accordingly. When the primary surface changes, the right workflow changes with it, and this week gave us three small examples of what that looks like in practice.
1. Cowork from Your Phone: Persistent Agent Threads Anywhere (original)
Overview
On March 17, Anthropic shipped a research preview that gives Pro and Max users a persistent Cowork agent thread accessible from Claude Desktop and the iOS and Android apps. Max got it first, Pro followed over the next two days. The headline reads "Cowork on mobile," but the word doing the work is persistent. A single agent thread lives server-side, keyed to your account, and any device can attach to it, read its state, and send it a follow-up. Start a research task on your laptop, walk out for coffee, check progress from your phone, approve a gate, come back and the work is done.
That is the first time agent work and mobile life have actually overlapped in a useful way for me. Previously a Cowork session was tied to the local VM on whatever machine started it — close the app and you lost the thread. Now the thread is the durable object and the desktop is just one client attached to it.
Technical
The architecture matters. The isolated VM still runs on your desktop when you are there, because tools that touch the file system or drive computer-use still need a local surface. What moved server-side is the agent state: the plan, the tool call history, the conversation context. That is the object your phone attaches to. From the mobile Cowork tab you can read real-time progress, send messages, or queue a new task that the desktop picks up the next time it wakes.
A few details from actually using it for a few days:
- Tools that need a local VM still need your desktop running. Mobile commands that depend on them queue until the laptop is awake.
- Push notifications on approval gates and task completion are real. For the first time a background agent feels like it is actually working in the background.
- The handoff between devices is tight enough that mid-sentence context switches do not lose thread state.
- Pro users who missed the feature on March 17 got it by March 19 as the rollout expanded.
The workflow I have been running: kick off a research task at 9am, walk out for coffee at 9:30, approve a gate from my phone at 9:45, come back at 10:15 to finished results. Three hours of elapsed time, maybe ten minutes of attention. The persistent thread is what makes that possible — without it I would either babysit the laptop or return to dead state.
Takeaway
Pick one task you would normally reserve for a deep work block — research, doc drafting, codebase exploration — and kick it off before lunch. Use the phone to nudge it from outside the building. The agent is ready to work while you walk around; the only question is whether you trust it enough to actually leave the room.
2. Shopify Quick Sale Now Works in Every Country (original)
Overview
Quick Sale is Shopify's lightweight in-person payment flow: open the mobile app, tap Quick Sale, enter an amount, take cash, send a payment link, or tap a contactless card where Tap to Pay is available. As of this week it works in every market Shopify operates in, not just the US, UK, Canada, Australia, and a handful of EU countries. The use case is narrow and real — the artist at a market stall, the consultant taking payment over coffee, the e-commerce brand running its first pop-up. If you already operate a POS lane with drawers and receipt printers, this is not for you.
The unlock is that "take money in person" no longer requires hardware anywhere Shopify runs. A payment link is universal: the customer pays on their own phone, which sidesteps both the card reader and any local rules around card-present transactions.
Technical
Quick Sale lives under the Sell tab in the Shopify mobile app. Enter an amount, optionally tag a product or customer, then choose a payment method.
Payment link is the universal path. It generates a one-time checkout URL you send by SMS, email, or QR. The customer completes the sale on their own device using Apple Pay, Google Pay, Shop Pay, or a saved card. The order lands in Admin tagged to the Quick Sale channel.
Cash records a manual cash payment for bookkeeping. Works offline and syncs when you reconnect.
Tap to Pay is the regional upgrade. In supported markets — US, Canada, UK, France, Germany, Spain, Italy, Netherlands, Belgium, Austria, Ireland, Australia, New Zealand, and a few more — you tap a contactless card against the back of the phone and the sale runs through Shopify Payments at in-person rates.
What you gain over full POS: zero hardware, faster path to first sale, and the payment-link flow pushes card-present risk onto the customer's device. What you give up: no multi-line cart with per-line discounts or staff permissions, no drawer or till reconciliation, no barcode scanner or receipt printer integration, and shallower POS-specific reporting.
Two edge cases worth flagging. Tax uses your store's default registration settings, not the customer's location — if you pop up in a jurisdiction where you are not registered, set up a market for it or the tax will be wrong. Refunds on payment-link orders route back to the original method through Admin; cash refunds you mark manually and hand back yourself.
Takeaway
If you have ever taken cash at a pop-up and reconciled it later in a spreadsheet, this is the week to stop. Open Shopify mobile, run a Quick Sale to yourself for $1, refund it from Admin, and you are trained. If you live in a Tap to Pay market, do one contactless test so you know it works. Everyone else, the payment link is your default — the lowest-friction way to take in-person money on Shopify without buying a single piece of hardware.
3. Shopify POS Faster Discount Entry: Real Time Saved (original)
Overview
Anyone who runs physical retail on Shopify POS already knows discount entry was one of the slowest parts of an in-person sale. Apply discount, type the code, wait, confirm, back to cart. On a Saturday afternoon with ten people in line, those extra seconds became walked customers and irritated staff. Shopify shipped a quiet fix in POS app version 9.40 and later: fewer taps per discount, recent codes auto-suggested, and a redesigned number pad that stops fighting your thumb.
It is the kind of update a large retailer would package as "phase two register UX optimization" and a small merchant would just call a relief. Worth reading the patch notes for.
Technical
The old flow was six steps: cart → discount button → choose code or amount → enter → confirm → back. The new modal collapses two of those into one combined view with a code field and an amount-or-percent field side by side. One tap, one entry, one confirm.
Recent codes show as chips at the top of the modal, ordered by frequency of use on that device over the last 7 days. If your store runs the same handful of codes — STAFF15, FRIEND10, LOYALTY20 — your cashiers mostly stop typing. Note that the list is per device, not per store, so a new register starts with an empty row and populates over a few days. Custom dollar-amount discounts do not store as chips, only named codes, which is a hint to create named codes for the amounts your staff actually applies.
The redesigned number pad is wider and taller and puts the decimal and backspace where the thumb lands. If you ever typed a percentage and accidentally hit the close button, you will notice. Per-line discounts now live on a long-press of the line item, surfacing a contextual control without leaving the cart. Cart-wide discounts stay at the bottom. Permissions, stacking rules, and the Admin-side discount engine are unchanged — the UX got faster, the rules engine did not change.
The math the Shopify team published: roughly 4 seconds saved per discount, 20 discounts per register per shift, 6 registers, 7 days a week, works out to about 56 minutes of register time a week. At a busy store that is one fewer person scheduled for the rush.
Takeaway
Today: update every register to POS 9.40 or later. This week: walk every cashier through the new flow in the onboarding huddle — three minutes, no slide deck, point at the recent-codes chips specifically because they are the highest-value change and the easiest to miss. Retire any custom numeric-entry cheat sheets you trained staff on; the new pad is intuitive enough not to need them.
Original sources
- Cowork from Your Phone: Persistent Agent Threads Anywhere — originally published 2026-03-17
- Shopify Quick Sale Now Works in Every Country — originally published 2026-03-18
- Shopify POS Faster Discount Entry: Real Time Saved — originally published 2026-03-19
