Skip to Main Content

Chromo

Built at Meta Global AI Developer Hackathon · Oct 26, 2026 · Remote

Chromo — Demo video

I built Chrono because AI coding agents now write code for hours without supervision and nobody can see what they actually did. When an agent stalls in an edit loop or breaks something, you are left scrolling a terminal log trying to guess what happened. Chrono records every agent event as it happens. Tool calls, file diffs, state transitions go through a lock free ring buffer into an append only SHA-256 Merkle chain built in C++. The log cannot be tampered with and I can prove it with a verify command. The cockpit scrubs through thousands of recorded steps at 60 FPS with 520 nanosecond seeks. The main feature is the Why button. Click any checkpoint and Muse Spark reads the full context and explains in plain English what the agent was trying to do, where it derailed, and whether its claims were true. On my first live test it caught the agent claiming it had verified a change when it had not. Chrono also detects stalls in real time and suggests the fix. I recorded Chrono's own construction, 2973 sealed blocks, plus a real Muse Code session, in the same ledger.

Team