Solo Builder Framework

Your private
AI workspace.

Han Solo is a persistent cloud environment where Ren lives, remembers, and works alongside you across sessions. Not a chatbot. A partner who doesn't reset.

Explore the docs ↓
Documentation
Architecture
How it works
The full stack — Letta, MCP, Claude, chat UI, PostgreSQL. What each piece does and how they connect.
Daily use
Working with Ren
Sessions, memory, dreaming, costs, what to share and how Ren learns across time.
Vision
Roadmap
Where this is going — how future projects get built with Ren in the loop, who does what.
Interactive
System Architecture
Live flowchart of the full Han Solo stack — MCP server, Letta, auth, DB, dream and synthesis pipelines.
What it is

The framework, made real.

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 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.

By the numbers
$21 Fixed per month
15 MCP tools
108+ Archival passages
The three pieces
01
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.

02
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.

03
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

Three services. One key. Nightly dream.

Three Render services, one Anthropic API key, and a nightly dream script. Private to Scott and Ted — not part of the public Solo Builder Framework.

ItemDetail
Chat URLhan-solo-mcp.onrender.com
Letta (Ren's brain)han-solo-letta.onrender.com — v0.16.7
MCP serverhan-solo-mcp.onrender.com/mcp
Ren modelClaude Haiku 4.5 — pay-per-token
EmbeddingsVoyage AI — voyage-3 (1024-dim)
DatabasePostgreSQL 16 + pgvector on Render
Nightly dream2:00am daily via launchd
Session rolloverAuto at 50 messages, or manual
Repogithub.com/scoots31/han-solo (private)