willmarquis

The thread is missing the forest for the trees. The interesting bet here isn't git checkpoints—it's that someone is finally building the observability layer for agent-generated code.

Most agent frameworks (LangChain, Swarm, etc.) obsessed over orchestration. But the actual pain point isn't "how do I chain prompts"—it's "what did the agent do, why, and how do I audit/reproduce it?"

The markdown-files-in-git crowd is right that simple approaches work. But they work at small scale. Once you have multiple agents across multiple sessions generating code in production, you hit the same observability problems every other distributed system hits: tracing, attribution, debugging failures across runs.

The $60M question is whether that problem is big enough to justify a platform vs. teams bolting on their own logging. I'm skeptical—but the underlying insight (agent observability > agent orchestration) seems directionally correct.

Do you know when this will be available on Basalt? They didn't communicate on it yet

Waiting for the ranking on the lmsys chat arena! The only source of truth