Claude Cowork Team Sharing: What Works and What to Use Instead

If you want to share Claude Cowork with your team, you can share less than you might expect. As of September 2026, Cowork sessions can't be shared, Cowork projects can't be shared on any plan, and artifacts can be sent by link, inside your organization by default on Team and Enterprise. If you need colleagues or outside clients in the same conversation, working on the same files, you need a shared agent workspace instead.

This guide covers what Cowork shares today, where it stops, the workarounds people use, and how a shared workspace like Universe handles the same job. Cowork is still the better choice for some teams, and the last section says which.

What can you share from Claude Cowork with your team today?#

Cowork has changed a lot this year, and older guides are out of date in both directions. Here is what Anthropic's help center says as of September 2026:

• Sessions run in the cloud (in beta). "Claude's work runs in an isolated environment on Anthropic's servers, separate from your computer and your network." Work continues if you close your laptop. Local files, browser use and computer use still need the Claude desktop app open.
• Cowork projects aren't shareable. A Cowork project holds local folders, instructions, links and its own memory. Anthropic's projects article lists as a current limitation: "For members of Team and Enterprise plans, Cowork projects do not support project sharing."
• Chat projects are, on Team and Enterprise. Projects on claude.ai can be shared with people in your organization with "Can view" or "Can edit" access. Group sharing is in beta on Enterprise. A Cowork project can link a chat project so its sessions draw on that knowledge. Claude's pricing page lists no project sharing on Pro or Max.
• Sessions can't be shared. "Sessions can't be shared with others, but you can share individual artifacts you create during a session."
• Artifact links depend on the plan. Pro and Max can choose "Only you" or "Anyone with the link". Team and Enterprise can choose "Only people with access", "Everyone in your organization" or "Anyone with the link", and the last one needs an Owner to turn on External sharing. Artifacts that use connected apps can't get a public link.

That leaves three gaps.

1. The conversation doesn't travel. A colleague can open an artifact you share. They can't read how the work was done, see what Claude was told or pick up a task you started.
2. The project doesn't travel. A Cowork project's folders, instructions and memory stay with you. The closest thing to sharing one is linking a shared chat project into it, which carries knowledge and instructions but not the folders or the sessions.
3. Outside your organization is mostly off-limits. Clients, contractors and a freelancer you work with every week aren't in your Claude organization. You can send them an artifact link if your plan or Owner allows it. You can't bring them into the work.

What should "sharing" mean for agent work?#

Agent work has more parts than a chat, and each matters to a team for a different reason.

Cowork on Team and Enterprise covers the first row through artifact links, and part of the fourth through plugin marketplaces. It doesn't share the second row, and a Cowork project's instructions and memory don't travel. On Pro and Max, only public artifact links are available.

What workarounds do people use, and where do they break?#

A shared Drive or Dropbox folder#

Everyone points their own Cowork project at the same synced folder. The files are shared; the sessions, instructions and project memory aren't. And two agents writing one file from two laptops is how you get "report (conflicted copy).xlsx".

Pasting outputs into Slack or email#

This works for one report. It breaks by the third revision, because the copy in the thread is out of date the moment someone asks Claude for a change, and nobody can see what was asked.

Moving everyone onto Claude Team#

This is Anthropic's answer, and inside one company it covers artifacts, chat projects and plugins. Every person needs a seat. As of September 2026, Claude's pricing page lists Team standard seats at $25 a month billed monthly ($20 billed yearly), and premium seats at $125 ($100 billed yearly). Sessions and Cowork projects still can't be shared, and clients still can't join.

Artifact links#

A link sends one output; it doesn't bring the other person into the work. On Team and Enterprise, a public link needs an Owner to allow external sharing first.

How does a shared agent workspace work instead?#

A shared agent workspace puts the people, the agents and the files in one place. What is an AI agent workspace? covers the idea in general. Here is how Universe does it.

Universe is a Mac app. Agents run on your computer through the model account you already pay for, work in the folders you give them, drive a copy of your signed-in Chrome, and run scheduled jobs. Sharing is built from three things.

Spaces#

A space is the container for a project: its folders or code, an agent, a model and memory. You share a space by email, including with people outside your company. Roles are viewer, editor and admin. A guest can leave a space but can't delete it.

Rooms#

Rooms are shared conversations inside a space, where people and agents work in one log. A shared space gets #general on its first share, and filing a session into a shared space turns it into a room of that space. This is the part Cowork doesn't have: the conversation is shared, not just the output.

A room has two kinds of message:

• A prompt goes to the agent and costs a turn.
• A team message goes to people, costs nothing and is never seen by a model. Naming an agent in a team message turns it into a prompt.

Rooms have @mentions, replies, reactions, pins and unread counts, and a colleague's agent turn streams into your room as it happens. We cover what happens when several people prompt one agent in AI agents in team channels.

The files#

Everything an agent makes is a real file in the session's folder, with a viewer for its kind: documents, datasheets, decks, PDFs, images and video, apps and more. The artifact panel has a scope switch between this room and the whole space, so a teammate can find what another room produced. They can also reference it in a prompt with an @space/<room>/<path> mention. Each file keeps up to 24 earlier versions on the Mac, with a diff.

Two honest limits. First, each Mac runs its own agent with its own model memory. The room shares the transcript, not one continuous model context. Second, if an agent stops to ask a question, the whole room sees it, but only the Mac running that turn can answer it.

How do you share an output with someone outside the company?#

Sometimes you just want to send a client the finished thing. In Universe, any file can become a share link at universe.works/s/<token>, drawn as what it is: a document, datasheet, slides, PDF, image or video. It's a snapshot, so what the client approved stays what they approved. Links can expire, and you can revoke them. .env files can't be shared.

Cowork's artifact links work differently. A link shows the version you shared until you select "Latest". On Team and Enterprise, an Owner has to turn on external sharing before a link can leave the organization. Anthropic also notes that shared artifacts "use the viewer's access, not yours", which matters for artifacts that pull live data from connectors.

Can you share the agent or skill itself, and take access back?#

A report is one piece of work. A trained agent or a written procedure keeps producing work, so it's often the more useful thing to share.

Agents. In Universe, you can hand an agent to someone with a private link at universe.works/agent/<token>. These links can't be guessed, can expire, and can be revoked for each recipient. You can also publish an agent at a permanent address, universe.works/a/<name>, and anyone can take a copy into their library. People who took a copy are notified when you publish a new version. A public page never shows the agent's memory, config, collaborators or internal ids. A copy is a copy: revoking a link stops new ones, not the copies already taken.

Skills. A Universe skill is a SKILL.md folder, the same format Claude Code, Codex, Gemini CLI and Grok read. Skills can be shared with people or by link at universe.works/skill/<token>. On your own Mac, Universe can also publish a skill into ~/.claude/skills and ~/.agents/skills, which covers all four of those agents. An agent can propose a change to a skill you own, but the change doesn't take effect until a person accepts it. One SKILL.md, four agents covers where each runtime looks.

Cowork shares plugins another way. On Team and Enterprise, Owners can build a plugin marketplace and set each plugin as installed by default, available for install, required or not available, and Enterprise admins can override that per group. That's the better model if you want an admin to control a fixed toolset for a whole company.

Which model does the work when a team shares a space?#

This is where the two approaches really differ. Cowork runs Claude, on each member's Claude plan. Universe doesn't sell model usage. Each person's turns run on the account they already have:

• Claude Code on a Claude Pro or Max plan, or an Anthropic API key
• Codex on a ChatGPT Plus, Pro or Business plan
• Gemini CLI on a Google account
• Grok with an xAI key
• Open models, free when they run on your own machine

So a designer on ChatGPT and an analyst on Claude can work in the same room. You can also pay centrally. A workspace owner can share a login with the team, with an optional monthly cap per member. A space owner can let their own account pay for turns in one space, for everyone or for chosen people. Every agent answer records which account paid and what it cost. You see it on hover.

Can you use a Claude or ChatGPT subscription in another app? See what's allowed in September 2026.

Claude Cowork vs Universe: comparison#

As of September 2026.

Universe's plans differ only in amounts. Free shares with up to 5 people and one shared room; Pro raises that to 25 people and unlimited rooms; a second workspace member needs Max. See pricing.

Who should stay on Cowork?#

Stay on Cowork if:

• Everyone is in one company on Claude Team or Enterprise, and shared chat projects plus internal artifact links cover what you need.
• Someone on the team uses Windows, or you want to start and check work from a phone or the web. Universe is Mac only.
• You want the work in Anthropic's isolated cloud environment, kept away from your computer and network, and still running after you close the laptop.
• Your admin wants central control: org-wide Cowork toggles, approval settings and required plugins.
• Claude is the only model you use, and you'd rather have a first-party product than a separate app.

Look at Universe if:

• You work with people outside your organization, like clients, contractors or a partner firm, and they need to be in the work, not just sent the output.
• You want the conversation shared, so a colleague can see how a result was reached and carry it on.
• Your team uses different model plans, or you don't want to buy a seat for everyone just to share one project.
• The work lives in local folders and a signed-in browser. Universe works in the folders you give it and drives a copy of your Chrome profile. Profiles never leave your Mac, so sharing a space doesn't share your logins. See how agents work on sites behind a login.

Before you choose: when signed in, Universe syncs what sharing and your other Macs need (artifacts, agents, skills, spaces, transcripts) to its cloud. Schedules run on a Mac, so a job can miss if that Mac is off; a spare Mac can keep agents running.

For the wider field, see Claude Cowork alternatives in 2026. To see Universe's features, go to /features. The Mac app is at /download.