Blog

Deep-dives into why we build what we build.

What one person can ship in a month

Fifteen releases, 226 changelog entries, nearly 90,000 lines of code — shipped solo in evenings and weekends. A retrospective on what Claude Code actually compresses, and what it can't.

Read, diff, and edit without leaving the terminal

AI agents reference files constantly. Instead of alt-tabbing to an editor every time, we built markdown, code, and diff viewers right into the terminal workspace.

Knowing what your agents are doing without looking

When you run 5 agents in parallel, you can't watch every terminal. We built status detection, sound notifications, and an activity dashboard so you don't have to.

One sidebar, all your repos

When you work across 10+ repositories every day, you need a single place to see branches, worktrees, PRs, and diff stats — without switching tools.

From the couch to 5G: how we built remote access

We wanted to check on AI agents without sitting at the desk. After trying session logs, remote proxies, and SSH, we ended up building a full mobile experience.

Why we built Smart Prompts

We were copy-pasting the same instructions to AI agents every day. So we turned them into one-click actions that know your context.

A terminal built for 8-hour sessions

Split panes, detachable windows, persistent sessions, find in content, and up to 50 concurrent terminals. We built a terminal for people who live in it all day.

Tracking your AI usage before the rate limit hits

Running multiple AI agents burns through rate limits fast. We built a usage dashboard so you can see exactly where you stand — and plan your work accordingly.

How we keep it fast with 10 repos and 8 terminals open

A desktop app that manages 10 repos, 8 terminals, and constant git operations can't afford to be slow. Here's the performance work we did under the hood.

Talking to your AI agents instead of typing

Hold a key, speak your instruction, release. The text appears in the terminal. No cloud service, no API key, no latency — Whisper runs locally on your machine.

Extend TUICommander with plugins

Every workflow is different. We built a plugin system so you can extend TUICommander with custom panels, context menu actions, and MCP integrations.