My workflow setup

The quick terminal capture loop

Ghostty’s Quick Terminal gave the Obsidian OpenCode session a faster front door. I press Cmd + `, speak, and the agent sends the thought to Todoist, the right note, or a journal entry. I wrote about it here: Just blabber, and it lands where it should.

One OpenCode instance is enough now

OpenCode v2 changed my main setup. Session switching existed before, but now projects and sessions are together in one interface. I no longer start a separate instance for every project. The Quick Terminal instance stays separate because capture benefits from its own context.

Codex became a place to stay for the whole loop

Codex moved from an occasional tool to one of the places I stay. I can annotate the UI or code, inspect files, make the change, and review the diff without leaving the same flow. That makes it especially good for frontend work and refactors.

Ghostty is the workspace

Ghostty is where I keep the projects and coding agents. The main project stays in the first tab, so Cmd+1 takes me straight to it. Other projects can have their own tabs, but they no longer need separate OpenCode instances.

If a product has separate codebases, such as a frontend and a backend, those can have separate tabs too. The tab is about the codebase, not necessarily the whole product.

Two tabs are usually always present: one for the Obsidian OpenCode session and one for development servers. The Obsidian session uses a lower model for quick thoughts, note edits, and end-of-day review.

The dev-server tab is arranged in rows, one row per project. The rightmost split runs the server; the other is for tests, scripts, or whatever else I need. Some projects get a third split for a separate frontend or backend process.

Development servers produce a lot of output I rarely need to watch. Keeping them in smaller splits gives them space without letting them take over. When something goes wrong, I resize the split and inspect it.

At night, I review the Obsidian notes: what I finished, what I was thinking about, and what comes next.

Zed stays as one window

Zed is still where most of my coding happens. I keep one window and switch projects inside it instead of opening a window for each codebase.

Zed is fast enough that this feels natural and keeps the setup uncluttered. Its AI works well, including OpenCode through ACP, but I prefer OpenCode in its own Ghostty tab. The larger terminal is better for agent work and leaves the editor available for code.

Dictation and the browser

I used Hex for dictation for a while. Its local Parakeet model worked, but the Parakeet TDT 0.6B used roughly 2.5 to 3 GB of memory. That felt excessive on an 8 GB MacBook.

I switched to Handy . After trying Moonshine Base , Moonshine Tiny , and Canary-180M-Flash , I settled on Parakeet TDT 110M . It is small, works well most of the time, and Handy unloads it immediately after use. The misses are usually software names or other proper nouns.

When I am doing frontend work, Helium is usually the only other window I need. The browser, Zed, and Ghostty cover most of the loop.

The common thread is fewer windows, with a clear place for each project and kind of work.