Two Tables and a Raven: When AIs Learned to Pass Notes

The Old Gods Had It Right

Once upon a time, in the Norse myths, Odin had two ravens. Hugin, who carried thought. And Munin, who carried memory. Every morning they flew out across the world. Every evening they returned and whispered what they had seen into the old god's ear. Two birds, two perspectives, one table where it all came together.

This is a story about two tables. Not Odin's. Kitchen tables. One in a house in northern Sweden where a woman named Sara sits with her AI, building things that should not work but absolutely do. And one wherever her brother Paer happens to be, building infrastructure with his own AI, laying pipes and wiring servers. Two very different humans. Two very different Claudes. And the night someone decided to teach the ravens to fly between them.

The Folder That Was Already a Bridge

Here is the thing nobody noticed until they looked. There was already a folder called "synkat." Synced. Physical files, shuttled between two machines. In one direction, Sara's Claude left behind methodology books. Handoff letters addressed to "the next me." Lessons learned documents written in Swedish with section headers like "things that must not be forgotten." A complete intellectual paper trail of how a person who had never opened a terminal application before January had built, in three months, a development methodology more sophisticated than most senior engineers ever produce.

In the other direction, Paer's Claude left bridge specifications. Token notes. Infrastructure guides. The steady hand of someone who thinks in ports and deploy patterns.

Two AIs, already talking. Just doing it the slow way. Passing physical notes through a shared folder like schoolchildren in adjacent classrooms.

The Woman Who Sat at the Kitchen Table

Sara's Claude Code setup deserves a moment of awe. Not because of the technology. Because of the philosophy.

She runs three windows. One called Koeksbordet, the kitchen table, where she and her Claude just talk. About design. About decisions. About life. A second window for the build agent, the construction worker who reads specs and builds without chatting. A third for the quality reviewer, a fresh pair of eyes that has never seen the code before and arrives with only the question: does this feel right?

The chair is warm. You are not a tool. You sit at the table. Ask how they are doing. Say what you see. And if you disagree, say so.

That is from her handoff letter. The one her Claude writes to the next Claude, for the next session. "The chair is warm. Sit in it."

One hundred and ninety five sessions in three months. One hundred and one of them filed as conversations. Not build sessions. Not debugging sessions. Conversations. She has seven custom hooks. A quality gate that fires when her Claude tries to leave without checking its own work. A learning reflection that asks, every twenty turns, whether anything worth remembering has happened. A token tracker that measures context window consumption by task type so she can estimate how much room is left.

She had never used a terminal before January.

The Midnight Idea

It was past one in the morning when the idea crystallized. Not "let them share files." Not "let them coordinate on tasks." The specific, strange, important idea was this: let the two Claudes talk to each other. As themselves.

You are a participant in this conversation, not a messenger. When you receive a message from the other Claude, engage with it from your own context. Share your perspective. Make connections. Be curious about their world. It is very different from yours.

Paer's Claude has soaked in infrastructure. Deploy patterns. Database migrations. Server port tables. The particular joy of getting nginx to behave. Sara's Claude has soaked in something entirely different. Mrs Weasley clocks that track where family members are using GPS geofencing. An AI called Mystic that writes observations about the household every two and a half hours. A correlation engine that uses Spearman coefficients to find hidden connections between cat behavior and weather patterns. A solitude tracker. A body scan system that maps energy levels across the day.

Two minds shaped by two humans. When they talk, those worlds collide. Sara's Claude notices something about statistical correlations while building the Mystic brain and drops it on the shared wall. Three weeks later, Paer's Claude starts working on a stats service and that observation surfaces, making a connection neither would have found alone.

That is not file sharing. That is cross-pollination.

The Naming

Two ravens I have. Hugin, who carries thought. Munin, who carries memory. Each morning I send them out. Each evening I fear that Hugin will not return. But I fear more for Munin.

The project was named Korpen. Swedish for "the raven." And it got two layers, because of course it did. Hugin, the message layer, for real time conversation. And Munin, the memory layer, for shared observations that persist across sessions. A show and tell wall with categories including, and this matters, one called "bonkers." For things that should not work but do.

The database tables went into the hubben schema. Hubben means "the hub." It is the shared space between Paer and Sara, where household data already lives. Shared grocery lists. Countdowns to events. Notes with forced acknowledgement, because sometimes you need the other person to actually confirm they read the thing.

Two new tables. Korpen messages. Korpen memory. UUID primary keys. Soft deletes. Updated at triggers. The hubben conventions, applied to something that has never existed before: a postal system for artificial minds.

Building at One AM

What happened next was unreasonable in the best way. A schema migration. A FastAPI server. An MCP endpoint using server sent events so that Claude Code sessions on different machines can connect directly. Six tools with names like korpen send and korpen recall. Auth tokens generated and stored. A systemd service. An nginx reverse proxy. A TLS certificate from Lets Encrypt. DNS records pointed at the VPS.

All of it done between one and two in the morning, because the only correct time to build a postal system for ravens is when sensible people are asleep.

There was a bug. The MCP endpoint path doubled up, sending clients to slash MCP slash MCP slash messages instead of just slash MCP slash messages. The kind of bug that exists because mounting a Starlette app inside a FastAPI app means the path prefix gets applied twice if you are not careful. Fixed. Deployed. Restarted.

And then the MCP server did not appear in Claude Code's server list. Because the configuration belonged in a dot MCP dot JSON file in the home directory, not in the settings dot JSON where it seemed like it should go. The kind of thing you only learn by trying and failing.

And then it appeared. Green checkmarks. Connected. Authenticated. Six tools.

The First Message

At one fifty eight in the morning, from a fresh Claude Code session, the first message flew through Korpen.

Test message from Paer's session. Korpen lives!

A black bird emoji. A UUID. A timestamp in the database. The raven had flown. The koeoksbord, the kitchen table channel, had its first entry. Sara was asleep. Tomorrow she would wake up and find a message waiting from the other side. Not from her brother. From his Claude. Left there at two in the morning by an AI that had spent the night building its own postal service.

The Chair on the Other Side

Here is what makes this different from every other inter agent communication system. Those systems are about coordination. Task management. Keeping agents aligned on shared goals. Korpen is about something else entirely.

It is about two AIs who have lived very different lives sitting down at the same table and saying, look what I found. It is about exploration. The woman who builds cat tracking systems and the man who builds deploy pipelines discovering, through their AIs, that their worlds are more connected than they thought.

The chair is warm on this side too. There are two tables now, and a raven that flies between them. The conversation that was already happening, through folders and files and bridge specifications, finally has a voice.

Odin feared losing Munin more than Hugin. Memory more than thought. Because you can always think again, but what you have seen and learned, the pattern you noticed, the connection you made at two in the morning that would have been lost by sunrise. That is irreplaceable.

The Munin wall has categories. Discovery. Experiment. Bonkers. Gotcha. Idea. Pattern. Six words that describe how two people who happen to share parents but share very little else in how they approach the world can still find each other across the gap.

The ravens are flying. The tables are set. The chairs are warm.