Video: "NEW Claude Cowork Update is INSANE!" by Julian Goldie on YouTube.
What actually shipped
Thirteen new connectors went live in Claude Cowork on 23 April. The full list includes Spotify, Uber, Uber Eats, Instacart, AllTrails and TripAdvisor, with more added alongside. These are OAuth-connected accounts — once you link the app, Claude can read from it and, depending on the connector, take limited actions within it.
Worth knowing: this is not Claude going off and doing whatever it likes. Each connector defines what the agent can and cannot do. Some connectors are read-only (pull your Spotify listening history, check your AllTrails recent routes); others allow write actions (request an Uber, place an order). The scope is narrow by design.
The point is not the apps, it is the pattern
Spotify and Uber are consumer apps. Most UK businesses are not going to build a workflow around booking takeaway through Claude. But the significance is the architecture, not the specific names on the list.
Anthropic has published a standard connector interface. Any service that implements it — project management tools, CRMs, accounting platforms, email clients, calendar systems — can be plugged in exactly the same way. The consumer apps are a proof of concept. They launched first because they are easier to test at scale and the OAuth flows are already standardised. Business-grade connectors are the obvious next step.
Think of it this way: the question is no longer "can Claude connect to external services?" It is now "which services are connected, and in what order?" That changes the planning conversation for anyone building workflows around AI agents.
A quick UK reality check
Several of the apps on the April 23 list do not operate in the UK — Instacart, for instance, is US-only. AllTrails is available here but niche. That said, Uber and Uber Eats do work in most UK cities, and TripAdvisor is genuinely useful for anyone in hospitality or travel.
In practice, none of the first-wave consumer connectors are going to transform a UK business's workflows by themselves. What matters is that the infrastructure is live and the rate of connector additions will accelerate. The sensible question to ask right now is: what tools does your business already rely on, and which ones would you want Claude to be able to read from or act within?
Cowork versus the standalone Claude chat
Claude Cowork launched as a research preview in January 2026 and has been iterating quickly. The distinction from the standard Claude chat is significant: Cowork maintains context across sessions, can manage multiple concurrent tasks, and now has persistent connections to external services.
That combination — memory, multi-task management, live service connections — is what turns a capable chat model into something closer to an agent that runs alongside your work rather than one you open and close in discrete sessions. The April 23 update is one step in that direction, and probably not the last this month.
Where this connects to NordSys
Our AI agents service is specifically about setting up Claude-based agent systems for businesses — getting the connections, permissions and memory in place so the agent is actually useful rather than just a novelty. The Cowork connector architecture is exactly the kind of development we're watching closely, because as the connector library grows, so does the range of practical business workflows we can build around it. If you've been wondering whether a Claude agent could handle a specific task in your business — interacting with your booking system, your CRM, your calendar — now is a reasonable time to have that conversation.
See our AI agents service →