Twitter/X

@edwinarbus relays Lex Fridman's setup

2026-04-03 · 20:29 UTC ·@edwinarbus ·1 min read

Brief

@edwinarbus relays Lex Fridman's workflow: combining Obsidian and Cursor (for MD) with vibe-coded web terminals to handle extensive podcast research. He generates dynamic HTML/JS interfaces for sorting, filtering, and visualizations, and spins up temporary mini-knowledge-bases that an LLM uses in voice mode on 7–10 mile runs to create interactive learning sessions.

Why it matters

@edwinarbus relays Lex Fridman's setup: a mix of Obsidian, Cursor (for Markdown), and 'vibe-coded' web terminals as the front end to manage a large, diverse podcast research base.

Key details

  • They generate dynamic HTML with JavaScript to sort/filter and interact with visualizations, and create temporary focused mini-knowledge-bases loaded into an LLM for voice-mode interaction during 7–10 mile runs, turning runs into interactive learning/podcast sessions.
Source evidence

Cursor as your knowledge base:

Lex Fridman (@lexfridman)

Same, I have a similar setup. A mix of Obsidian, Cursor (for md), and vibe-coded web terminals as front-end.

Since I do a podcast, the number/diversity of research interests is very large. But the knowledge-base approach has been working great.

For answers, I often have it generate dynamic html (with js) that allows me to sort/filter data and to tinker with visualizations interactively.

Another useful thing is I have the system generate a temporary focused mini-knowledge-base for a particular topic that I then load into an LLM for voice-mode interaction on a long 7-10 mile run. So it becomes an interactive podcast while I run, where I ask it questions and listen to the answers to learn more.

Anyway, heading out for a run now, thanks for the write-up 👊

— https://nitter.net/lexfridman/status/2039841897066414291#m