Open Video Guide

Open Video Guide converts a tutorial video into an illustrated guide.

The project is local-first and open source. It does not require a paid AI API. Users supply the computer, storage, network bandwidth, and electricity.

Product goal

The product must make each generated step easy to verify. Each step must include a timestamp, visual evidence, confidence data, and a review state.

The alpha processes user-owned video files. It exports Markdown, Hypertext Markup Language (HTML), and structured JavaScript Object Notation (JSON). The local editor lets users correct and export each guide.

Narrated-video smoke tests pass. Silent-video quality does not yet meet a release gate.

Related MCP server: MathMind MCP Server

Product difference

Most products extract a transcript and make a summary. Open Video Guide will connect each instruction to evidence from the source video.

The product will:

• Keep all processing on the local computer after model download.

• Mark uncertain instructions for review.

• Keep source timestamps with each step.

• Select useful screenshots for each instruction.

• Let the user correct the result before export.

• Use replaceable model and platform adapters.

Local alpha pipeline

Video file
  |
  +-- FFmpeg: media inspection and extraction
  +-- faster-whisper: narrated speech and timestamps
  +-- Fixed windows: candidate frame selection
  +-- Qwen3-VL through MLX-VLM: visual step proposals
  |
Evidence merge and verification
  |
Editable guide
  |
Markdown, HTML, JSON, and screenshots

The architecture also permits other runtimes. For example, Linux systems can use faster-whisper and a CUDA model server.

Integration plan

One Model Context Protocol (MCP) server will expose the product functions. Transport adapters will support these clients:

• ChatGPT and Codex plugins

• Claude and other MCP clients

• Odysseus local workspaces

• Command-line and local web clients

Odysseus is the correct name of the PewDiePie project. It is a self-hosted AI workspace that can connect to MCP servers.

See docs/INTEGRATIONS.md for the verified plan.

Repository map

Current commands

Use Python 3.11 or a later compatible version.

python -m pip install -e ".[dev]"
ovg validate examples/example-guide.json
python scripts/validate_benchmark.py
pytest
python scripts/check_ste.py

The validate command checks a guide against the public JSON schema. The inspect command returns local video facts. The generate command creates a local illustrated guide.

Run a fast file test without model inference:

ovg generate /path/to/tutorial.mp4 \
  --output outputs/my-first-guide \
  --profile frame-only

Install the local model dependencies:

python -m pip install -e ".[dev,local-ai,mcp]"

Run the local Artificial Intelligence (AI) profile:

ovg generate /path/to/tutorial.mp4 \
  --output outputs/my-ai-guide \
  --profile local-ai

See the local alpha test for complete instructions.

Local review editor

Install the local web adapter:

python -m pip install -e ".[web]"

Start the editor:

ovg-web

Open http://127.0.0.1:8765 in a browser. Select the fast draft to test without a model.

Install the local model dependencies for the local AI draft:

python -m pip install -e ".[web,local-ai]"

The editor stores private job data in .ovg-data. Git ignores this directory.

See the local editor guide for the complete workflow.

Shared Codex and Claude work

The repository has one shared project state for Codex and Claude. Each agent reads the same goals, verified capabilities, limits, and task queue.

Refresh the current project context:

python scripts/project_context.py

Create a verified handoff:

make handoff

The generated handoff is .project-context/PROJECT_CONTEXT.md. Git ignores this file because it contains live repository data.

See the shared agent handoff for operating instructions.

The benchmark validator checks public records without the source videos. Use its media option to check local source digests.

Development status

The project has a testable alpha pipeline. The complete benchmark and silent-video release gates remain open.

The local Model Context Protocol adapter exposes two tested tools. The Odysseus integration passed local tests with both model profiles. The local review editor passed its service and browser tests.

See these documents:

• Product requirements

• System architecture

• AI system plan

• MCP tool contract

• Development workflow

• Quality plan

• Roadmap

Writing standard

Project technical text must obey ASD-STE100 Simplified Technical English, Issue 9. The project uses an approved terminology list for software terms.

The automated checker finds only some rule violations. A trained reviewer must do the final language review.

Legal text and exact source text are not changed. See docs/STE_STYLE_GUIDE.md.

License

The project source uses the Apache License 2.0. Model files and third-party programs keep their own licenses.

See LICENSE and docs/MODEL_LICENSE_POLICY.md.