Skip to content

Terminal shell settings are shared between Local Server and WSL Server when both are configured #51994

Open

Description

@QQQxu

Description

When both a Local Server and a WSL Server are configured, the Terminal shell preference is not isolated per server. Changing the shell for one server affects the other, and the setting can also change after restarting the desktop.

Plugins

local skill

OpenCode version

v2

Steps to reproduce

  1. Configure both a Local Server and a WSL Server in OpenCode (for example, Ubuntu-24.04).
  2. Set the Local Server Terminal shell to pwsh (PowerShell).
  3. Leave the WSL Server Terminal shell as Auto (Default) or set it to another value.
  4. Restart the desktop environment or restart OpenCode.
  5. Switch between the two servers or open terminals again and observe that the shell choice is not isolated.

Expected behavior:
Each server should keep its own Terminal shell preference independently. For example, Local Server uses pwsh, while WSL Server uses its own default shell without affecting the other.

Actual behavior:
The shell setting is shared or overridden across servers. After changing one server's shell setting, the other server changes as well, and the issue persists after restart.

Screenshot and/or share link

Image Image

Operating System

Windows with WSL (Ubuntu-24.04)

Terminal

Windows Terminal / integrated terminal

Activity

  1. github-actions commented on Sep 29, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

  2. opencodejr commented on Oct 28, 2026

    @opencodejr
    Contributor

    Thanks for the detailed report and screenshots. Each server is meant to keep its own Terminal shell: the Servers settings page stores the shell in that server's own global config. So what you describe looks like a bug, not intended behaviour.

    I couldn't reproduce it, because it needs the Windows desktop app with a WSL server, which isn't available in this environment. A maintainer with a Windows and WSL setup will need to look at it.

    Two things would help:

    • Your exact version (Settings > About, or opencode --version).
    • After you set pwsh on the Local Server, whether the WSL distro's global OpenCode config (for example ~/.config/opencode/ inside WSL) contains a shell entry, or only the Windows-side config does.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions