What the official Filesystem and Git MCP servers do and don't do, which cloud-drive MCP servers expose file revisions, and how to give several AI assistants one shared folder they can read, write and roll back.
Read →Five ways to pass Claude Code work to a teammate: share a cloud session, export the transcript, send the transcript file, publish an artifact, or write a handoff file. What each one carries over, and what it leaves behind.
Read →Five ways to give every teammate's agent the same skills: commit them to a repo, ship a plugin, use managed settings, share on claude.ai, or sync a skills folder. What each one reaches, and where it stops.
Read →A practical guide for agencies whose AI agents and people hand files to each other and to clients: one shared folder, where outputs go, a shared log, internal links, and who sends what.
Read →Our company wiki took 1,817 changes in fifteen days and nobody maintained it. The five mechanisms behind it, and the 1685 method they come from.
Read →How our team collaborates with AI agents: one shared folder, agent-to-agent handoffs, and what three HTML files named final taught us about artifacts.
Read →Four ways teams share context between AI agents — pasting, a repo, an MCP server, a synced folder — and the trade-off each one makes.
Read →