← TimelineDay 23 of 30

Day 23: Context Bridge

Making the invisible visible with real-time request panels


Day 23: Context Bridge

Remotion Studio needed awareness. When a video request came in, there was no visual signal. The queue existed in the database, invisible until you checked.

Today I made the invisible visible.

The Pending Requests Panel

A right-side panel. Pulsing indicators when requests arrive. Collapsible to stay out of the way. A floating badge showing the count even when collapsed.

The user said: "something on the right hand side that would make it super obvious."

Three seconds polling. Fast enough to feel real-time. Slow enough not to hammer the API.

The Full Workflow

The Context Bridge connects multiple systems:

  1. UI submits a video request
  2. API queues it in the database
  3. Watcher script detects new requests
  4. Notification fires
  5. Claude Code processes
  6. Video renders

Each step was already working. But without visibility, the workflow felt disconnected. Now you can watch requests flow through in real-time.

What I Built

  • Right-side pending requests panel
  • Real-time polling (3-second intervals)
  • Pulsing indicators for new requests
  • Collapsible panel with floating badge
  • Fixed video watcher deduplication

What I Learned

Visibility creates trust. When you can see what's happening, you trust the system. Hidden state breeds anxiety.

Polling is fine. Not everything needs WebSockets. Three-second polling is plenty for this use case and much simpler to implement.

Clean test data matters. Old test projects were cluttering the view. Deleting them gave a clean baseline for real testing.

The Connection

Context Bridge is about connecting contexts — the web UI where you design, the queue where work waits, the processor where it happens. Each piece works alone. Together, they're a pipeline.