How it works

Real-world use: Claude Code + casty "GUI isn't an option." — Anonymous In Part 1, I built bcon — a GPU-accelerated terminal emulator for the Linux console. But there's one thing you can't escape as a developer: AI coding agents can handle research just fine. But what about checking your own web app renders correctly? Or GitHub Actions, PR reviews, and other things gh can't cover? For those, you need a real browser. I looked for existing options. Here's what I found: Nothing checked all the boxes: JavaScript + CSS + high fidelity + text copy + no GUI required. → github.com/sanohiro/casty casty running on the Linux console inside bcon YouTube video playback inside casty on bcon casty works with any Kitty Graphics-compatible terminal — not just bcon. Ghostty and Kitty both work too. The concept is simple: connect to Chrome headless-shell via CDP (Chrome DevTools Protocol), stream frames to the terminal using Kitty Graphics Protocol, and forward keyboard/mouse events back to Chrome. Chrome downloads itself automatically on first run to ~/.casty/ — no manual setup needed. Cookies and storage are preserved, so you can log in to Google and other services normally. The moment I actually wanted this: editing a React app with Claude Code while watching changes live in casty. Claude Code rewriting a React+Vite app — UI is in Japanese, but you get the idea 😄 Changes reflected instantly in casty Starting to think you might be able to live on the Linux console after all? Templates let you quickly answer FAQs or store snippets for re-use. Hide child comments as well For further actions, you may consider blocking this person and/or reporting abuse