Terminal shell integration timeout setting doesn't persist after restart

[misha-sunborn]

App Version

3.15.5

API Provider

OpenRouter

Model Used

gemini-2.5-pro-preview-03-25

Actual vs. Expected Behavior

My terminal start time is slow, so I need to increase the "Terminal shell integration timeout" via the slider in the settings to avoid shell integration errors when executing commands. No problem, that works.

I notice that when I restart VS Code, the timeout goes back to 5 seconds, even though the slider is still set to whatever I had set it to. If I move the slider, it takes effect again. So it seems the default value is loaded on startup, rather than whatever was previously set.

Detailed Steps to Reproduce

1. Set the "Terminal shell integration timeout" via the slider in the settings. You could perhaps set it to a very low value, so that a terminal command will fail due to very short startup timeout.
2. Run a Roo terminal command and see that the terminal integration startup timeout behaves as expected for the value you set.
3. Restart VSCode
4. Run a Roo terminal command again, and see that the default of of 5 seconds has been restored internally, even though the slider is still sitting at the value that was set.

Relevant API Request Output

Additional Context

Let me know if you need more detail on this. It might be a quick fix.

[dosubot]

Hey @misha-sunborn! 👋 I'm here to help you tackle bugs, answer questions, and guide you on your journey to becoming a contributor. While you wait for a human maintainer, feel free to share any details or questions you have! 😊

There is a known issue where VS Code appears to ignore custom terminal integration timeout settings, defaulting to a 7-second timeout even when a different value is set. This issue has been reported, but no solution has been confirmed yet ^[1]. Additionally, the timeout setting is supposed to persist across sessions using VSCode's globalState, but it seems there might be a problem with how the value is retrieved or applied on startup ^[2][3].

You might want to check if there are any updates or patches available that address this issue.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[cte]

Thanks for the report - I'll take a look.