Escribano

Record your screen. Get a structured summary of what you did.

Platform: macOS (Apple Silicon) required. Linux/Windows on the roadmap. Minimum: 16GB unified memory (32GB recommended for best quality)

What you put in

A screen recording. Could be 20 minutes, could be 3 hours. You didn't take notes.

What you get back (~9 minutes later)

# Session Card - Feb 25, 2026

## Escribano Pipeline Optimization
**1h 53m** | coding 22m, debugging 30m, terminal 24m, review 58m, planning 6m

- Optimized the video processing pipeline by evaluating skip-frame strategies 
  and removing scene detection for 180-minute videos.
- Resolved persistent VLM parsing failures and truncation errors by implementing 
  raw response logging and fallback mechanisms.
- Executed database migrations to add the new observations table schema.
- Benchmarked the performance of the GLM-5 and Qwen-VL models.

## Frame Extraction & Scene Detection
**19m** | coding 11m, debugging 4m, terminal 4m

- Developed TypeScript scripts for video frame extraction using FFmpeg.
- Debugged a critical parsing failure at Frame 3.
- Monitored terminal logs to track progress of a 792-second video file.

## Research & System Analysis
**22m** | review 3m, research 2m, coding 7m, terminal 6m

- Reviewed GitHub Copilot pricing and Screenpipe repository architecture.
- Investigated the database schema in TablePlus.

---
*Personal time: 2h 38m (WhatsApp, Instagram, Email)*

That's the card format. Two others:

Standup format

## Standup - Feb 25, 2026

**What I did:**
- Debugged VLM parsing failures by implementing raw response logging
- Optimized video frame extraction pipeline using FFmpeg
- Analyzed GLM-5 and Qwen-VL model performance
- Implemented database schema migrations

**Key outcomes:**
- Resolved truncated response issues with fallback parsing
- Identified scene detection as a latency bottleneck
- Validated new batch extraction strategy

**Next:**
- Merge scene detection optimization branch
- Benchmark qwen3_next model
- Add unit tests for fallback parsing

Paste straight into Slack.

Narrative format

# Session Summary: Sunday, February 22, 2026

## Overview
I spent nearly three hours optimizing the VLM inference pipeline. The main focus 
was resolving JSON parsing errors during batch processing and benchmarking the 
qwen3-vl:4b model against InternVL-14B. By the end, I'd identified the truncation 
root cause, adjusted MAX_TOKENS, and validated the fix against 342 frames — 
resulting in a 4x speedup with continuous batching.

## Timeline
* **0:00** (45m): Terminal work, running benchmark scripts
* **45:00** (60m): Debugging JSON parsing in VS Code
* **1:45:00** (40m): Researching model quantization
* **2:25:00** (34m): Documenting performance metrics
...

Good for retrospectives or blog drafts.

Benchmarks

Architecture Benefits (MLX Migration)

Production Run (March 2026)

Processed 17 real screen recordings with MLX backend:

Everything runs locally. No API keys. Nothing leaves your machine.

Hardware Tiers (March 2026)

Performance varies by hardware:

Minimum viable: 16GB unified memory (slower but functional)

Recommended: 32GB+ for comfortable use, 64GB+ for best quality

Why this exists

Most screen recording tools just give you a video file. If you want to remember what you did, you have to watch it back.

Escribano watches it for you. It extracts frames, runs them through a vision-language model, transcribes any audio, and writes up what happened — broken into topics, with timestamps and time per activity.

Built for developers: understands the difference between debugging, coding, reading docs, and scrolling Slack. Doesn't just OCR text (which produces garbage when every screen has "function" and "const" on it).

How it works

Screen recording
     │
     ├──► Audio: Silero VAD → Whisper → transcripts
     │
     └──► Video: FFmpeg frames → scene detection → adaptive sampling
                                              │
                                              ▼
                                    VLM inference (MLX-VLM, Qwen3-VL-2B)
                                              │
                                              ▼
                                    "Debugging in terminal"
                                    "Reading docs in Chrome"
                                    "Coding in VS Code"
     │
     ▼
Activity segmentation → temporal audio alignment → TopicBlocks
     │
     ▼
LLM summary (MLX-LM, auto-detected) → Markdown artifact

Uses VLM-first visual understanding, not OCR + text clustering. OCR fails for developer work because all code screens produce similar tokens. VLMs understand the activity, not just the text.

Quick Start

Prerequisites

# macOS (Homebrew)
brew install whisper-cpp ffmpeg

# MLX for inference (Apple Silicon) - auto-installed on first run
# Or pre-install with:
pip install mlx-vlm mlx-lm

That's it. No external daemons required. MLX-VLM and MLX-LM run in-process.

(Optional) Ollama Backend

If you prefer Ollama, set ESCRIBANO_LLM_BACKEND=ollama:

brew install ollama
ollama pull qwen3:8b  # or qwen3.5:27b for 64GB+ RAM

Run

# Check prerequisites
npx escribano doctor

# Process a recording
npx escribano --file "~/Desktop/Screen Recording.mov"

Local Development

git clone https://github.com/eduardosanzb/escribano.git
cd escribano
pnpm install
pnpm escribano --file "~/Desktop/Screen Recording.mov"

Output: ~/.escribano/artifacts/

CLI

Flags

Subcommands

Formats

Examples

# Process and copy
npx escribano --file "~/Desktop/Screen Recording.mov" --format standup --copy

# Find latest video in a directory
npx escribano --latest "~/Videos"

# Narrative format
npx escribano --file session.mp4 --format narrative --force

# With external audio
npx escribano --file recording.mov --mic-audio mic.wav

# View configuration
npx escribano config
npx escribano config --path

Supported inputs

Configuration

Escribano auto-creates a config file on first run that persists your settings:

# View current configuration
npx escribano config

# Show path to config file
npx escribano config --path

# Edit manually
vim ~/.escribano/.env

The config file (~/.escribano/.env) is organized by category with inline comments:

Environment variables always take priority over the config file. For full reference, see AGENTS.md.

Architecture

Clean architecture: domain entities, pure services, adapter interfaces for external systems (MLX-VLM, Ollama, Whisper, FFmpeg, SQLite).

Deep dives:

• Why OCR fails for developers
• MLX-VLM migration for 4x speedup
• Benchmarks and learnings

Full architecture: docs/architecture.md

Requirements

• macOS (Apple Silicon for MLX-VLM)
• Node.js 20+
• 16GB+ RAM (see model tiers above)
• ~10GB disk for models

Roadmap

• VLM-first visual pipeline
• MLX-VLM migration
• Activity segmentation
• Multiple artifact formats
• Auto-detect best LLM model
• Auto-detect ffmpeg hardware acceleration
• OCR on keyframes for code/URLs
• MCP server for AI assistants
• Cross-recording queries

License

MIT

Escribano = "The Scribe"