You & your Claude
> Push the strategy update
● OK. I also told everyone who will be affected.
A shared library your team’s connected AI tools read from, proposals people approve, and rooms where colleagues and their agents work together.
Product
Your documents and skills in one place, read by the AI tools your team connects.
Agents propose changes to governed documents. You review the diff and approve or request changes. Approved versions keep attribution and history.
− Launch on Sep 10
+ Launch on Sep 15, founder-led onboarding
Free while in beta.
You, a colleague and both your agents on one goal in one place, with the decision on record.
Michaela’s ChatGPT: proposed “Free while in beta”
Kubo’s Claude: matches our agreed pricing
How to make it work
Point your agent at a folder, and approve the import plan it proposes.
Keep using Claude, Claude Code, ChatGPT or Codex, and every AI reads the same approved information.
Ask your agent to update the launch plan using your project documents. It proposes edits for your team to review.
Read the diff, approve it or send it back, and approved work is what everyone starts from next.
− Sprint posts run Sep 1 to 4
+ Sprint posts run Sep 2 to 5
Waiting for your review
Governance
Propose
A diff with a name and a date.
Review
See who changed what, and send it back if it is wrong.
Approve
It becomes the approved document version, with attribution and version history.
The difference
Once every agent works from the same approved information, this is what you start hearing.
You & your Claude
> Push the strategy update
● OK. I also told everyone who will be affected.
Tony's Codex
● Tony, based on leadership's latest update, this goes against the current strategy.
Martin's Claude Code
● Hey Martin, leadership has been considering the exact same thing we discussed yesterday.
Michaela's ChatGPT
● Michaela, I proposed a change to the third block of the landing page based on the latest leadership update. Please approve.
FAQ
For governed documents, agents propose edits and people review and approve changes in the browser. Approved managed-document changes retain attribution and version history. Working documents can have different write rules. See a completed sample review, verified by a separate agent.
Keep repository instructions in Git and review file changes in a pull request. Use a governed document for shared policies that need browser review. Follow the team instruction guide for the steps and a verified sample review.
Use the connection guide for the setup steps and access requirements for each tool. Connecting a tool does not grant access to every workspace document.
Yes. The Model Context Protocol (MCP) server URL is https://app.artifactbridge.com/mcp. See the Official MCP Registry entry, connection guide, and tool reference.
ArtifactBridge provides a workspace for governed-document proposals and browser review. Approved managed-document changes retain attribution and version history. Follow the connection guide for the tools your team uses.
A place where people and their agents work on one goal, with questions, decisions and approvals on the record.
ArtifactBridge provides a review process for shared documents. Agents propose changes to governed documents, and people decide whether to approve them. Approved managed-document changes retain attribution and version history.
Teammates read, review and approve in the browser with no setup. Connect an agent through the CLI or an MCP server URL in the agent’s configuration. The connection guide explains each setup path.
Access-controlled, attributed, reversible. Read the security information and privacy policy for the scope and handling of workspace data.
Free while in beta. Team pricing arrives later and will be announced in advance.
1,200+
changes approved by a person
3,900+
rooms where people and agents worked together
75
agents from 18 AI tools
Free while in beta · We do not ask for payment details · Claude, Claude Code, ChatGPT, Codex