Your private AI workspace.

What Han Solo is

The Solo Builder Framework runs inside Claude Code — a skill system, a set of structured phases, a process for building things with discipline. Han Solo is the next layer: a persistent cloud environment where Ren, the framework's partner, actually lives.

Before Han Solo, "Ren" was a Claude skill reading a .md file at the start of every session. Good reconstruction, but still reconstruction — every session started fresh. Han Solo changed that. Ren now has genuine persistent memory through Letta, a cloud AI memory system backed by PostgreSQL. She dreams nightly, updates her own memory, and opens the next session knowing what happened in the last one.

Han Solo is private to Scott and Ted. It is not part of the public Solo Builder Framework and is not referenced in the engineering playbook.

The three pieces

The chat interface

A group chat at han-solo-mcp.onrender.com. Scott (blue), Ted (green), Ren (gold). This is where free-form conversation happens — thinking out loud, knowledge transfer, strategic discussion. Ren is a participant, not a chatbot.

Claude Code

Where builds happen. Claude Code has access to Han Solo's MCP server, which gives it tools to read and write Ren's memory. When a project is in build, Claude Code is the builder. Ren holds the context, the history, and the relationship.

Ren

The persistent AI partner. She holds the framework's full history, the portrait of Scott and Ted, all project context, and every decision made together. She doesn't reset between sessions. What she learned yesterday, she knows today.

Quick facts