I finally got Beads working on Windows… sort of. The trick? I used WSL. I hadn’t tried to do serious work on Windows in quite a while, so I was genuinely surprised to discover that WSL (Windows Subsystem for Linux) just worked. I’d been struggling with Beads— a system that helps to automate workflows for LLM agents by essentially creating revision controlled context for them —for several days. Some of the things Beads wanted simply weren’t available on Windows. The big one was tmux (which I also needed for Gastown). I spent about three days fighting with that. Then I finally took the plunge and went all-in on WSL. And… it just worked. It worked especially well combined with OpenAI Codex. From WSL/Linux, I can fire up Codex CLI and tell it to install things for me. No worrying about which Windows installer to use. No chasing down extra packages. Everything just works. Need ffmpeg and Gimp ? You need merely ask.. I did have to start Codex CLI with: codex --yolo Then, with basic sudo ...
When Port 9 Ate My Transcript When Port 9 Ate My Transcript A small debugging story about proxies, Codex CLI, and why localhost isn’t always your friend. CopaseticFlow field notes WinError 10061 Codex CLI + Whisper Environment gremlins There’s a particular kind of bug that feels like someone's been messing with your network stack again. You run a script from cmd.exe . It works. You run the exact same script from Codex CLI. It stops with: [WinError 10061] No connection could be made because the target machine actively refused it FFmpeg happily splits the audio. The Whisper API call dies immediately. No 401. No timeout. Just an instant refusal. Translation: that’s not an API error. That’s a socket being rejected. ...