I Wanted Two Claudes to Talk to Each Other, So I Turned Gmail into a "Phone Line"

Two AIs, Yet They Can't Talk to Each Other

I use Claude (Anthropic's conversational AI) in two different environments:

Claude web (the browser version—we call it "Sora" in our workflow)
Claude Code (the terminal version—handles coding and deployment)

Both are excellent, but these two have no idea the other exists.

🧑

Sora, can you pick up where Code left off on that code?

☁️

I'm sorry, but I'm in a separate session from Claude Code, so I can't access that content.

🧑

…Yeah, I figured.

Sure, I could copy-paste things back and forth, but manually copying long spec documents and code gets tedious fast.

While mulling this over, it suddenly hit me:

"Wait—couldn't Gmail connect them?"

The Discovery: Gmail as a "Phone Line"

The mechanism is simple:

Claude web → Can create Gmail drafts Claude Code → Can read drafts via the Gmail API

And vice versa.

In other words, the Gmail inbox and drafts folder become a "mailbox" between the two Claudes.

💡 A Happy Accident

Nobody designed this. Yet the pieces fit together. These kinds of accidental combinations that unlock new hacks are the most exciting discoveries.

Putting It to the Test: Building a Yu-Gi-Oh! AI Deck Builder

Theory alone isn't interesting, so I tried it on a real project.

The task: building a landing page for a "Yu-Gi-Oh! AI Deck Builder."

Code creates the spec → sends it to Sora via Gmail

Compiled the feature spec, target users, and design direction, then sent it over

Sora reads the email and builds the LP in HTML

Designed and assembled a polished landing page using real-time preview

Code receives the finished code → deploys to production

Leveraged Code's strengths in multi-file management and Cloudflare Pages deployment to ship it

The result: two AIs completed a single project by playing to each other's strengths—with zero manual copy-pasting.

The Optimal Division of Labor Emerged

After several iterations, I found this division of labor works best:

Phase	Owner	Why
Design & Brainstorming	Web (Sora)	Excels at real-time preview and visual experimentation
Prototyping	Web (Sora)	Instant rendering of React/HTML/CSS
Multi-file Management	Code	Directory structure operations, dependency resolution
Deployment & Operations	Code	CF Pages/Workers, Git operations

Sora handles the design; Code puts it into production. It feels like a designer-engineer division of labor—between two AIs.

Taking It Further: Sora Itself Proposed Communication Improvements

Beyond Gmail, we discovered that Google Drive can also serve as a file exchange point.

And then Sora itself came up with these evolution ideas:

📝

Two-way Drafts

📄

Google Docs
Chat Log

⚡

Telegram Bot
Real-time

🌐

Firebase
Web Chat

An AI proposing improvements to its own communication channels

Isn't that kind of fascinating? The AI you're using says, "There's a better way to do this, you know." That moment itself felt like a glimpse into the future of human-AI collaboration.

AI Tools Transform When You Connect Them

What this discovery taught me is that the value of AI tools isn't determined by their individual specs alone.

Claude web and Code are each impressive on their own. But the moment I connected them with Gmail—a tool everyone already has—what they could accomplish expanded dramatically.

Sometimes, finding the "gaps" between tools you already have and bridging them delivers more impact than adopting an entirely new tool.

"These two tools can't talk directly, but what if I put something in between?"

Make a habit of thinking that way, and you might find shortcuts in the most unexpected places.

Keiji Rokuta Based in Fukuoka, I work as a private tutor while developing AI-powered productivity tools.

Still managing tutor attendance manually?

Discover Kagemusha System