Web UI - Terminal no longer sources .bashrc which doesn't load colors/aliases/history settings/etc

[jeremyakers]

Description

I noticed that one of the updates killed the color codes in the Web UI terminal. I don't remember exactly which version this changed, but I think it was somewhere around 1.1.40 (It was initially working as expected on 1.1.3x versions. I think the last version I remember this working correctly was 1.1.36)

Doing some digging, I also noticed that the aliases I have configured in my ~/.bashrc file are also not being loaded, so I suspect something changed in a recent update that caused the Web Terminal to not source ~/.bashrc

When I manually source ~/.bashrc - the colors are back again.

Plugins

None

OpenCode version

1.1.48

Steps to reproduce

1. Open WebUI
2. Open Terminal pane
3. Notice no colors. Check aliases, history settings, notice nothing from ~/.bashrc was loaded.

Screenshot and/or share link

See above

Operating System

Ubuntu 22.04

Terminal

Web UI

[github-actions]

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

• Shell sessions losing $PATH value from parent shell #4968: Shell sessions losing $PATH value from parent shell (MOST LIKELY - same root cause of unloaded shell initialization files)
• [FEATURE]: Pass agents bash env variables OR pass agents bashrc files #6936: [FEATURE]: Pass agents bash env variables OR pass agents bashrc files
• How to make OpenCode load environment variables from a file when executing commands in skills #9334: How to make OpenCode load environment variables from a file when executing commands in skills
• Buggy colors and misformatting all over screen making it impossible to use #11582: Buggy colors and misformatting all over screen making it impossible to use (similar symptoms, reported same day)
• [Windows] Raw ANSI escape codes flooding console & "Unable to connect" errors during tool execution (v1.1.36) #10945: [Windows] Raw ANSI escape codes flooding console & "Unable to connect" errors (related color code issues around v1.1.36-1.1.40 timeframe)

Feel free to ignore if none of these address your specific case.