My Daily Driver

I use Zed with ACP connected to OpenCode, giving me access to multiple model providers.

My usual Zed terminal layout:

Left: Dev server
Right: Claude Code and Codex CLI Multi-terminals

Sometimes I work entirely in WezTerm, with one tab for dev servers and another for Claude/Codex sessions. I've found that around eight projects per tab is the limit before things become too cramped.

About the tools

Zed is a high-performance, GPU-accelerated code editor built in Rust. It's fast to open, fast to navigate, and has first-class multi-buffer and terminal support. ACP (Agent Control Protocol) lets Zed hand tasks off to AI agents directly from the editor.

OpenCode is a terminal-native AI coding assistant that connects to multiple model providers — Anthropic, OpenAI, Google, and others — through a single interface. Running it inside Zed's terminal means I can swap models without leaving the editor.

Claude Code is Anthropic's official CLI for Claude. It reads the full repository, maintains context across a session, and handles multi-file edits, debugging, and architectural tasks. It's the tool I reach for when a task requires understanding the whole codebase.

Codex CLI is OpenAI's terminal agent. It's faster on narrow, well-defined tasks — generate a function, scaffold a file, apply a specific transformation. I run it alongside Claude Code in a split terminal and route tasks based on scope.

WezTerm is a GPU-accelerated terminal emulator with a programmable config in Lua. Tabs, panes, and multiplexing make it practical for running multiple projects and AI sessions simultaneously without a window manager.

Keep reading