FOUR ORIGINAL TIDBYT DISPLAYS · ONE LOCAL CODEX AUTOMATION

When something needs me, I just look up.

I already owned four original Tidbyt displays. With Codex, I turned them into a living status wall—a local automation that shows what’s running, what finished, and what needs me.

Explore the live wall

Local operatorPrivate by default64×32 pixels

An original walnut Tidbyt display showing the TIDBYTS All Clear system state in a real room — ON MY DESK · ORIGINAL TIDBYT HARDWARE

REAL PIXLET RENDERS

Codex Control Tower showing current work — Codex

System monitor showing that every check is healthy — System

Codex Control Tower showing that one task needs a response — Needs me

Pull requests landed over three time windows — Delivery

Tidbyt made the hardware and operates the platform. TIDBYTS supplies the Codex-driven views and refresh loop.

EXPLORE THE WALL

See the wall in action.

Pick a screen, then switch through what it can show. Every image comes straight from the same software that drives the hardware.

Codex Control Tower showing current, recent, and background work

Rendered from the same Pixlet apps that run on a Tidbyt. No mockups.

A LIVING MONITOR · A QUIET WALL

The wall changes. The question stays simple.

TIDBYTS is a passive information radiator with a living Codex operator behind it. As my work changes, Codex can learn a new check and tailor what the displays show—while every screen stays quiet and glanceable. This static tour proves the same views without hardware, credentials, or private data.

npm ci
npm test
npm run test:pixlet
npm run demo:assets