The "early React" analogy resonates. I've been seeing the same pattern with MCP (Model Context Protocol) — the primitive is powerful (AI assistants calling tools via a standard protocol), but most implementations are still gluing things together ad-hoc. There's a gap between "I can build an MCP server" and "this is a polished, opinionated product."

The DuckDB choice is smart for local-first. I use ClickHouse for production analytics and the difference in operational complexity is night and day — DuckDB just works for single-node use cases without any infrastructure overhead.

Curious about the Chrome profile cloning approach. That's clever for importing auth state, but does it create any issues with cookie/session conflicts if both profiles try to access the same service simultaneously?