Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]: Terminal shows incorrect shell type after reloading webpage

Open
#6,032 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
shell, typescript
Domain
tooling

Research direction

No files or tests are named. Reproduce the reload sequence in Chrome with bash as the default shell, then trace how the web terminal restores or selects its shell after the page reload; done means reopening with CTRL+` launches bash rather than sh.

Written by the indexing model from the issue text.

Description

bug
Is there an existing issue for this?
  • I have searched the existing issues
OS/Web Information
  • Web Browser: Chrome version 110.0.5481.178 (Official Build) (64-bit)
  • Local OS: Windows 11 Pro
  • Remote OS: Debian 11 in LXC
  • Remote Architecture: x86 (AMD)
  • code-server --version: 4.10.0
Steps to Reproduce
  1. Set default shell to bash.
  2. Open terminal, should be bash.
  3. Click trashcan and kill the terminal.
  4. Refresh page, or close and re-open tab before reopening terminal.
  5. Hit CTRL+` to open terminal, will open sh terminal instead of bash -- hitting trashcan and reopening without the refresh it will open bash terminal as expected.
Expected

Expect that default terminal is launched regardless of state when the application was last used. If bash is set to default, it should launch a new bash terminal.

Actual

The wrong terminal is launched and the default setting is ignored.

Logs

No response

Screenshot/Video

No response

Does this issue happen in VS Code or GitHub Codespaces?
  • I cannot reproduce this in VS Code.
  • I cannot reproduce this in GitHub Codespaces.
Are you accessing code-server over HTTPS?
  • I am using HTTPS.
Notes

No response

Dominant language
TypeScript
Stars
79.4k
Forks
6.9k
Avg merge
2d 13h
Merged PRs (30d)
39

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coder/code-server

All issues in coder/code-server

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.