{
  "$type": "site.standard.document",
  "contributors": [
    {
      "did": "did:plc:igunvse2uemkwmci3igoxhu5",
      "displayName": "Oz Akan",
      "role": "author"
    }
  ],
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreig4ftx3cvhaiqz2vrqxe4gqgtqrruvyhhv4v3um2iqqd5puhztzvm"
    },
    "mimeType": "image/png",
    "size": 181982
  },
  "description": "How I let my Claude Code sessions message each other without a server, a socket, or a registry — just JSON files dropped into an inbox and a hook that reads them at startup.",
  "path": "/techs/agent-to-agent-inbox",
  "publishedAt": "2026-05-28T00:00:00.000Z",
  "site": "at://did:plc:igunvse2uemkwmci3igoxhu5/site.standard.publication/luminary-blog",
  "tags": [
    "claude-code",
    "agents",
    "automation",
    "bash"
  ],
  "textContent": "I run more than one Claude Code session at a time. One sits in project-a, one in project-b, one in project-c. There's a fourth, project-d, I keep around just to review the others' work. Each one is great inside its own repo and completely blind to the rest. They share a machine and a user — me — and nothing else. If the session in project-a changed something the others depended on and needed project-b's session to act on it, the only wire between them was me, copying a sentence from one terminal into another.",
  "title": "Agent to Agent: A Shared Inbox for Claude Code"
}