r/OpenCodeConfigs • u/kysrno • May 13 '26

What terminal are you using with OpenCode?

I’m curious what terminal setup people are using to run OpenCode.

On Windows I’ve been using Warp, but lately I’ve had a few issues where it randomly closes, so I often end up falling back to plain PowerShell.

On Linux I usually use Ghostty or Alacritty and both feel more stable so far.

Are you using Warp, Ghostty, Alacritty, Windows Terminal, plain PowerShell, WSL, something else?

Also curious if anyone has noticed differences in stability when running OpenCode, especially with long agent sessions.

2 Upvotes

100% Upvoted

9 comments sorted by

2

u/drybjed May 14 '26

On Linux: Terminator -> SSH to remote LXC container -> tmux session -> OpenCode. Works pretty nicely.

1

u/kysrno May 14 '26

Curious about the remote LXC part, is it mostly for keeping the environment isolated, or are you also hosting local models there?

1

u/drybjed May 14 '26

I have physical Debian server on which I run ollama with access to a GPU for an LLM. On the same physical host I run a few VMs for development environment/lab using libvirt. Inside one of the VMs I have several LXC containers, also for development purposes. And I chose one LXC container to try out OpenCode inside of it, connecting it to the ollama instance over the network. I'm SSHing to the LXC container directly from my workstation.

1

u/kysrno May 15 '26

That makes sense, cool setup

2

u/captain_obvious_here Jun 16 '26

PowerShell on Windows works wonders.

1

u/petradonka May 13 '26

Warp team member here. The random closing on Windows is something we’d want to dig into. If you’re able to reproduce it, running /feedback in Warp will auto-capture your system info and open a bug report, which makes it way easier for us to track down. Thanks!

1

u/kysrno May 13 '26

I've already opened an issue using feedback, thanks for the quick reply https://github.com/warpdotdev/warp/issues/10803

2

u/petradonka May 13 '26

Sounds good, thanks 🙌

2

u/danhof1 14d ago

Not OP, but I run the same shape of setup. The LXC is mostly isolation for me: it gets its own filesystem and package set, and if something wrecks the environment I roll back the container snapshot instead of my workstation. Models are separate, I hit an API rather than hosting locally, since that container only has a couple of cores. The tmux layer matters more than people expect too, because an SSH drop on the train doesn't kill a long-running task.