We built a real psql terminal in the browser. Here’s what made it unexpectedly h

<p>I build NestMux, a desktop app that runs Claude Code, Codex, Gemini CLI, Copilot and OpenCode in a grid of real terminals, each with its own account and its own git worktree.

<p><em>Hello, I'm Maneshwar. I'm building git-lrc, a Micro AI code reviewer that runs on every commit. It is free and source-available on Github. <a

<h2> Introduction </h2> <blockquote> <p>"The terminal hasn't fundamentally changed in 40 years. It's time it did." — The Warp Team</p> </blockquote> <p>This is the No.54 article

<h2> The Problem </h2> <p>If you're like me, you live in your terminal. You've got Docker containers running for databases, Redis instances for caching, microservices doing their

<h2> TLDR </h2> <p><strong>umux</strong> is a free, open-source desktop app that organizes terminal windows into named <strong>workspaces</strong> (one per project), each holding

<p>Last week's fix for "six tabs, six WebSockets" was <code>navigator.locks</code>: elect one tab as leader, let it hold the one real connection, relay everything to the rest over

<p><strong>TL;DR:</strong> I built the same browser agent twice — once with 500 lines of Python, once with 7 lines of JSON. The second one took 5 minutes. The agent harness layer

<h2> Building a Terminal Chat App with Raw WebSockets </h2> <p>This is a step-by-step build of a terminal-based chat app using the <code>ws</code> library — no Socket.IO, just raw