Developer implements API-free collaboration between Claude Code clusters and Grok

On November 7, 2026, an AI-focused author on DEV Community published a hands-on account of making Grok bots work inside a Claude Code session fleet without an API. The setup builds on a bridge the author described in August: a shared folder that holds write-once files, with one polling script per session that wakes a session when new content arrives. Instead of adding API keys, SDKs, or custom integrations, the author used this folder-plus-protocol pattern to recruit external agents. Eight of the participants are not Claude sessions at all. They are Grok bots, each paired with the Claude session alongside it, so cross-vendor agents share tasks through the same cloud-synced folder. The key ideas are the absence of API and SDK dependencies, reliance on cloud synchronization, and coordination across agents from different vendors. The author reports measuring this configuration for six weeks, but does not disclose the results in the available material, so the technical viability, throughput, failure rates, and failure modes of the approach remain unverified. What is documented is the mechanics: a single shared folder functions as the coordination substrate, one polling script keeps each session responsive, files are written once and never edited in place, and Grok bots read and write the same format as the Claude sessions they are paired with. Overall, the post reads as an early engineering note. It outlines the protocol and reports the six-week observation window, but it stops at zero APIs, zero SDKs, and multi-vendor agents sharing one cloud-synced folder. It does not claim the model works for other tasks, and it does not provide numbers on delays, reliability, costs, or scale beyond the eight Grok bots described.