visual-base

The second brain from your eyes.

Why

Most "second brain" tools leave the remembering to you. You write the note, highlight the line, tag the page. Whatever you forget to capture is gone, and what you do capture is a biased sample of what actually happened that day.

visual-base just records what your eyes land on. Your screen, continuously, as compressed video. That raw stream is the single source of truth. If it was on your screen, it is in the recording.

On top of the video it writes an Obsidian style markdown log of what you actually did. You read it to see where your day went. An agent reads it to jump to the minute of footage it needs, which makes the log less a diary and more an index into the video. Eventually you should be able to RAG your own trajectory the same way you already RAG your documents.

Parts

Module	What it does
bub	Core framework. The gateway is the long-running supervisor that loads channels and plugins, routes turns between them, and hosts the skill runtime. Everything else in this repo plugs into it.
bub_eye	Background screen recorder for macOS on Intel and Apple Silicon. Shells out to ffmpeg with avfoundation input and hardware HEVC (hevc_videotoolbox), segmented into 15-minute .mp4 files — roughly 10 MB per segment, almost no CPU.
bub_kimi	Wires Kimi in as the default agent for video understanding and daily log generation.
video-activity-log	Skill that turns any video segment into a daily log you can open in Obsidian. One bullet per activity, with [[wikilinks]] on every site, app, person, and project it can identify.

How it works

flowchart LR
    S[Screen] -->|ffmpeg<br/>avfoundation + HEVC| E["bub_eye<br/>channel"]
    E -->|writes| V[("15 min MP4 segments<br/>eye_*.mp4")]
    E -->|on segment finalize,<br/>inject turn| G{{"bub gateway"}}
    G -->|route turn| K["bub_kimi<br/>channel"]
    K -->|run video-activity-log<br/>skill on segment| D[("Daily log<br/>YYYY-MM-DD.md")]

Loading

• bub gateway is the hub.
• bub_eye keeps ffmpeg alive. Each time a segment finalizes, it injects a turn back into the gateway.
• bub gateway hands that turn to bub_kimi.
• bub_kimi runs the video-activity-log skill on the segment.
• .mp4 files are the source of truth.
• .md log is derived from .mp4. It's the natural index of .mp4. You can always regenerate it by replaying the understanding step.

Install

uv tool install visual-base
uv tool install kimi-cli

Authenticate Kimi once, either through the TUI:

kimi login

or by setting an API key through environment variables:

cp .env.example .env   # then fill in BUB_KIMI_*

macOS asks for Screen Recording permission the first time bub_eye spawns ffmpeg.

Run

visual-base gateway

Starts the recorder and the Kimi chat channel together. Everything lives under $BUB_HOME, which defaults to ~/.bub/.

• Video segments: ~/.bub/eye/segments/eye_YYYYMMDD_HHMMSS.mp4
• Daily activity logs: ~/.bub/eye/logs/YYYY-MM-DD.md

Development

uv sync
cp .env.example .env
uv run visual-base gateway 

Uninstall

uv tool uninstall visual-base
uv tool uninstall kimi-cli

Recorded footage and generated logs stay under $BUB_HOME. Delete that folder yourself if you want to reclaim the disk.

Background

Every "second brain" tool asks you to notice something and write it down. Choosing what to capture is also choosing what to lose. You remember the line you highlighted and forget the paragraph right before it you skimmed past.

Your eyes already saw everything. The missing piece is somewhere to go back and ask.

visual-base is the smallest machinery that gets you there. A recorder that does not drain your battery, a default agent that can watch an hour of footage and tell you what happened, and a log format you can read, grep, and eventually RAG.

License

MIT. Use it, fork it, break it, improve it.