Live on Product Hunt Intraface launched today. Less steering, more vacations. See the launch
Start for free

What is a shared workspace?

A shared workspace is one place where several people see and change the same things, with a record of who did what. It began as shared documents and channels. The newer meaning adds people's AI agents as participants: each agent pulls the shared thing, edits it, and puts a new version back where everyone can see it.

Part of Glossary: the terms behind MCP, coding agents and shared pages, defined plainly.

How it works

Two people's agents edit the same page in one shared workspace; every publish becomes a version with a name on it.AnaAna's agentClaude CodeBenBen's agentCursorthe shared pageversions, withwho made eachaskspulls, publishesaskspulls, publishesevery version kept
  1. One copy of the thing lives in the workspace: a page, a board, a document. Nobody emails a file around.

  2. Each person opens it, or their agent pulls it, and makes a change.

  3. The change goes back as a new version. Everyone sees the same current state, and the history says who changed what.

  4. Rules for the space live in it too, so a newcomer, human or agent, reads them before touching anything.

  5. Comments and questions sit next to the work, not in a separate chat, so the context stays with the thing.

Shared workspace versus shared folder

A shared folder holds files. Everyone can open them, but the work happens elsewhere: you download, edit, upload, and hope nobody else did the same in between. A shared workspace is where the work itself happens. The thing you are making lives there, in one copy, and the changes people make are made to it, in place, with a record of who made each one. The folder is storage; the workspace is the room.

That is the old meaning, and Google Docs, Notion pages, Slack channels and Figma files all fit it. The newer meaning adds a second kind of participant. People now do much of their work through coding agents, so a shared workspace has to be a place an agent can enter too: read the current state, learn the rules of the room, make a change, and hand it back where the humans can see it.

Example: a team and its agents on one page

Three people are shaping a launch page. Each works with a different agent: one in Claude Code, one in Cursor, one in Codex. The page lives on a board. Each agent pulls the board, reads a small rules file that says what the page is for and which colors and tone to use, makes its edit locally, and publishes a new version. Publishes queue one at a time, so two agents editing different files both land, and two agents editing the same file get told to pull first. The team sees one page, one history, and one list of comments pinned to the parts people are arguing about. That is a shared workspace in the new sense, and it is what Intraface is built to be.

Why it matters

The failure mode of agent work is isolation. Each person's agent produces something good in a private chat, and then four good things have to be reconciled by hand in a meeting. A shared workspace makes the reconciliation continuous: every change lands in the same place, is visible to everyone, and carries a name. Disagreements show up as comments on the thing, not as rival files.

It also fixes the onboarding problem. When the rules of the room are written down inside the room, a new teammate's agent reads them on its first pull and behaves like the rest. Nobody has to paste the house style into every prompt.

Common mistakes

  • Calling a chat a workspace. Chat is where you talk about the work. If the work is attached to messages, the current state is whatever was posted last, and nobody can be sure.
  • Letting agents write without attribution. If a version says changed by bot, the trail is useless. Each agent should act as a named person, with a token that person can revoke.
  • No rules inside the space. Taste and constraints that live in someone's head get re-explained forever. Put them in the workspace where every participant, human or agent, reads them.
  • One big file. A workspace that is a single document with no files, no history and no comments becomes a scroll of edits. Keep the structure the work needs.

FAQ

What is the difference between a shared workspace and a shared drive?
A drive stores files that you download, edit and upload again. A shared workspace holds the work itself, in one copy, and changes are made to it in place with a record of who made each one.
Can AI coding agents work in a shared workspace?
In the newer kind, yes. Intraface boards are an example: each person's agent connects over MCP, pulls the board, edits locally and publishes a new version. Every version is kept with the name of the person whose agent made it.
Does a shared workspace replace chat?
No. Chat is for talking about the work; the workspace is where the work lives. The useful split is comments pinned to the thing for decisions about it, and chat for everything else.

Stop sending HTMLover Slack.

Create an account in a minute, connect your coding agent, and make your first board.