opencode with multi-agent sessions on any os

frequently asked questions

• +Does running OpenCode inside Pane break its LSP integration?

  No. OpenCode's language server integration works through the project directory it is pointed at. Running inside a Pane terminal does not change how OpenCode resolves files, imports, or LSP diagnostics — it still reads from the same worktree root.

• +Can I run multiple OpenCode sessions in parallel?

  Yes. Start one OpenCode session per pane, each against its own worktree. They run as separate processes with separate working directories and do not share state.

• +Can I mix OpenCode with other agents in the same workspace?

  Yes. Pane does not care which CLI agent is in each terminal. Put OpenCode in one pane, Claude Code in another, and Aider in a third. Each session runs on its own branch via worktrees.

• +Does OpenCode's share-link feature work when running inside Pane?

  Yes. OpenCode's share link is generated by the OpenCode process itself, not by the terminal host. The link works the same whether you run OpenCode in Pane, in a stock terminal, or in tmux.

• +Can I use different model providers in different OpenCode sessions?

  Yes. Each OpenCode session is a separate process with its own configuration. One session can use Anthropic, another can use OpenAI, and a third can use a local Ollama model — all running in parallel inside Pane.

• +Does Pane work on Windows without WSL?

  Yes. Pane is a native Windows desktop app. OpenCode runs in a Pane terminal on Windows without needing WSL, though Pane works inside WSL too if that is your setup.

• +How does Pane handle OpenCode's TUI rendering?

  Pane hosts a full terminal emulator for each session. OpenCode's TUI renders normally — the same as it would in any terminal that supports ANSI sequences.

• +Does Pane integrate with OpenCode's git workflow?

  OpenCode manages its own git operations. Pane manages the workspace around it: which worktrees exist, how sessions are named, and where diffs get reviewed. The two layers do not conflict.

• +What does Pane add over using a terminal multiplexer with OpenCode?

  Terminal multiplexers manage panes of text. Pane manages agent sessions: worktree creation, session naming, diff review, and git actions are all part of the interface — not something you script yourself.

• +When is a single OpenCode session enough?

  If you work on one branch at a time and one terminal covers your workflow, you do not need Pane. Pane is useful when you want to run multiple OpenCode sessions in parallel, or combine OpenCode with other CLI agents, and need isolation between them.