8000 Terminal shell integration timeout setting doesn't persist after restart · Issue #3181 · RooVetGit/Roo-Code · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Terminal shell integration timeout setting doesn't persist after restart #3181

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
misha-sunborn opened this issue May 5, 2025 · 2 comments
Assignees
Labels
bug Something isn't working in progress Actively being worked on

Comments

@misha-sunborn
Copy link
misha-sunborn commented May 5, 2025

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.

@misha-sunborn misha-sunborn added the bug Something isn't working label May 5, 2025
Copy link
dosubot bot commented May 5, 2025

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

@dosubot dosubot bot added the needs scoping Needs up-front scoping to be actionable label May 5, 2025
@cte
Copy link
Collaborator
cte commented May 5, 2025

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

@cte cte self-assigned this May 5, 2025
@hannesrudolph hannesrudolph moved this from New to Issue [In Progress] in Roo Code Roadmap May 5, 2025
SmartManoj pushed a commit to SmartManoj/Roo-Code that referenced this issue May 6, 2025
* wip

* updated api tiered pricing schema for vertex and gemini to support tiered cache prices

* vertex too

* changeset

* pushing claude implementation

* addressing aras comments

* cleaning up caches

* linter complaining

* enabling total price for gemini provider

* Fixing Gemini Caching mechanism

* Update src/api/providers/vertex.ts

Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>

---------

Co-authored-by: Cline Evaluation <cline@example.com>
Co-authored-by: arafatkatze <arafat.da.khan@gmail.com>
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
@hannesrudolph hannesrudolph added in progress Actively being worked on and removed needs scoping Needs up-front scoping to be actionable labels May 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working in progress Actively being worked on
Projects
Status: Issue [In Progress]
Development

No branches or pull requests

3 participants
0