Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Self-Recording Workflow

One of amem’s foundational features: amem is its own best demo. The extension records itself being used, producing the marketing video and Chrome Web Store listing assets automatically.

How it works

  1. An orchestrator (human or agent) sends {cmd: 'start_recording'} to the extension’s background service worker.
  2. The background worker opens an offscreen.html document with a MediaRecorder consuming tabCapture.
  3. The agent then drives the extension UI through the bridge — clicking the side panel, capturing pages, showing the wiki.
  4. {cmd: 'stop_recording'} finalizes the .webm and saves to Downloads as amem-recording-<iso>.webm.

Why this matters

  • Demos stay in sync with reality — the recording shows the current UI, not a stale screenshot
  • Chrome Web Store listings can be refreshed in minutes
  • Agents learn to operate amem by watching their own recordings

Status

The recording skeleton is shipped. The agent-driven recording scenarios are Day 2 work. The complete workflow ships alongside the Chrome Web Store submission.