Unscramble

Unscramble is the substrate everything else runs on: a Cloudflare Worker MCP server backed by Supabase that any of my AI surfaces can connect to — Claude on my phone during the commute, Claude Code at my desk, scheduled agents overnight.

It holds live markdown docs, captured context, tasks, receipts, and a diary. The most physical module is a GPS-driven work diary: location pings become automatically-detected stops, stops become labelled site visits with billable notes, and unbilled work queues up for invoicing — a timesheet that writes itself.

On top of it runs a small fleet of scheduled agents: a 5:30am curator that assembles a designed morning brief (live traffic hazards, scored tech news, the day’s tasks) with a spoken version for the drive, a nightly diary writer, and back-office sweeps that reconcile email and files — each one reading its spec from a live doc, so editing the doc changes tomorrow’s run with no redeploy.

Not a product — a daily-driver. But it’s the clearest picture of how I think software should work now.