Codex Made Open Source Accessible to Me

Terminal precision used to stop me in my tracks. Asking Codex to fix one bug has changed what I am able to do with open-source tools. I built Typewriter as a starter kit: bring an idea, develop it through a supported interview, and leave with a written piece or presentation you can use. In this video, I share how repairing a first-user bug helped me participate in open source, and how the interview produced this presentation. The Typewriter system saves interviews and outputs in a local archive. That work is indexed, compiled and updated with each new production run, with a wiki that informs future questions—including “How is this different from what you've said before?” The key is the archive stays on my computer. Codex and Claude Code still use cloud models and send relevant material online for processing. Keeping the work locally gives me something to build on as I use different services. Chapters 0:00 Typewriter and a positive first experience 0:39 Why Terminal stopped me 1:12 The first-user challenge-gate bug 1:45 A repair that put open source within reach 2:17 A starter kit for users and developers 2:49 An interview that develops my ideas 3:19 Saving the work in a local archive and wiki 3:57 Local storage and cloud processing 4:30 Finding a new angle in familiar material 5:00 Building on earlier interviews 5:31 Bring an idea, leave with useful work Substack article: https://johnduhring.substack.com/p/op... Explore Typewriter on GitHub: https://github.com/duhring/typewriter