Undo what Claude Code changed with /rewind and checkpoints, see what rewind can't restore (files only Bash changed, background subagent edits, other sessions), and cover the rest with Git and a synced folder's file history.
Read →Why an HTML file won't open as a page from email, Google Drive or Dropbox, and five ways to turn it into a link someone can open: GitHub Pages, Netlify Drop, Claude Code artifacts, a shared-folder link, or plain attachment.
Read →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 →What actually reaches a teammate's machine in Claude Code (committed CLAUDE.md, rules and skills) and what stays behind (auto memory, CLAUDE.local.md, transcripts), plus how to hand work from one person's agent to another's.
Read →