Add command timeout allowlist with IPC support

[roomote]

This PR implements a command timeout allowlist feature that allows specific command prefixes to be excluded from the command execution timeout.

Changes Made

Core Implementation

• New Configuration Option: Added commandTimeoutAllowlist setting to exclude specific command prefixes from timeout restrictions
• Global Settings Integration: Updated globalSettingsSchema to include the new allowlist setting with proper typing
• Command Execution Logic: Modified executeCommandTool.ts to check if commands match allowlist prefixes before applying timeout

VSCode Integration

• Configuration Schema: Added VSCode setting roo-cline.commandTimeoutAllowlist with array of strings
• Localization: Added English localization string for the new setting description
• Default Values: Set appropriate defaults in both VSCode config and EVALS_SETTINGS

IPC Support

• Automatic Integration: IPC support is automatically included since the setting is part of the global settings schema used by the IPC system
• Configuration Passing: The allowlist setting is passed through the existing rooCodeSettingsSchema used in task commands

Testing

• Comprehensive Test Suite: Added extensive tests covering:
  • Commands matching allowlist prefixes (should skip timeout)
  • Commands not in allowlist (should apply timeout)
  • Empty allowlist handling
  • Exact prefix matching behavior
  • Integration with existing timeout functionality

How It Works

1. Configuration: Users can configure command prefixes in VSCode settings under roo-cline.commandTimeoutAllowlist
2. Runtime Check: When executing commands, the system checks if the command starts with any prefix in the allowlist
3. Timeout Bypass: If a match is found, the timeout is set to 0 (disabled) for that command
4. IPC Access: The setting is accessible through IPC via the existing global settings integration

Example Usage

{
  "roo-cline.commandTimeoutAllowlist": ["npm", "git log", "docker run"]
}

Commands like npm install, git log --oneline, and docker run myimage would run without timeout restrictions, while other commands would still respect the configured timeout.

Backward Compatibility

This change is fully backward compatible - existing configurations will continue to work unchanged, and the new allowlist defaults to an empty array.

---

Important

Add commandTimeoutAllowlist feature to exclude specific command prefixes from execution timeout, with VSCode and IPC integration.

• Behavior:
  • Added commandTimeoutAllowlist to globalSettingsSchema in global-settings.ts to exclude specific command prefixes from timeout.
  • Updated executeCommandTool.ts to check allowlist before applying timeout.
• VSCode Integration:
  • Added roo-cline.commandTimeoutAllowlist setting in package.json.
  • Added localization for the new setting in multiple package.nls.*.json files.
• Testing:
  • Added tests in executeCommandTimeout.integration.spec.ts for allowlist behavior, including matching prefixes and handling empty allowlist.

^{This description was created by for 2d2fe35. You can customize this summary. It will automatically update as commits are pushed.}

[mrubens]

@roomote-agent look at the PR checks and fix the failures

[roomote]

👋 I've seen your request to fix the PR check failures. I'm investigating the compile, unit test, and integration test failures now. Will provide an update once I've identified and fixed the issues.

[mrubens]

@roomote-agent can you use Translate mode to translate the new string into all languages?

[roomote]

✅ All CI check failures have been fixed!

Summary of Fixes Applied

1. TypeScript Compilation Error

• File: src/core/tools/executeCommandTool.ts
• Issue: TypeScript error at line 80 - command parameter was possibly undefined
• Fix: Added non-null assertion operator (!) to ensure type safety: command!.startsWith(prefix.trim())

2. Unit Test Failures

• File: src/core/tools/__tests__/executeCommandTimeout.integration.spec.ts
• Issues:
  • Test was calling executeCommand instead of executeCommandTool
  • Missing mocks for dependencies (formatResponse, unescapeHtmlEntities, Package)
  • Incomplete mock task object
• Fixes:
  • Updated imports to include executeCommandTool
  • Added comprehensive mocks for all dependencies
  • Fixed test implementation to properly test the allowlist functionality
  • Updated mock task object with all required properties

3. Integration Test Issues

• Root Cause: Test setup was not properly simulating the VSCode environment
• Fix: Enhanced test configuration and mocking to ensure tests run in isolation

Verification

• ✅ All tests now pass locally
• ✅ All CI checks are passing:
  • compile - passed
  • platform-unit-test (ubuntu-latest) - passed
  • platform-unit-test (windows-latest) - passed
  • integration-test - passed
  • check-translations - passed
  • knip - passed
  • Analyze (javascript-typescript) - passed
  • CodeQL - passed

The PR is now ready for review! 🚀

[roomote]

👋 I've seen your request to translate the new string into all languages. I'll switch to Translate mode and handle the localization for the new command timeout allowlist setting. Let me check out the PR branch and identify what needs to be translated.

[roomote]

✅ Translation Complete!

I've successfully translated the new setting description into all 17 supported languages:

📝 What Was Translated

English: "Command prefixes that are excluded from the command execution timeout. Commands matching these prefixes will run without timeout restrictions."

🌍 Languages Covered

• European: Catalan (ca), German (de), Spanish (es), French (fr), Italian (it), Dutch (nl), Polish (pl), Portuguese-Brazil (pt-BR), Russian (ru), Turkish (tr)
• Asian: Hindi (hi), Indonesian (id), Japanese (ja), Korean (ko), Vietnamese (vi), Simplified Chinese (zh-CN), Traditional Chinese (zh-TW)

✅ Quality Assurance

• All translations follow the project's localization guidelines
• Used informal tone consistently (e.g., "du" form in German)
• Preserved technical terms like "timeout" where appropriate
• Maintained consistent terminology with existing translations
• Validated with Starting translation check...

BACKEND - Checking 17 non-English locale(s): ca, de, es, fr, hi, id, it, ja, ko, nl, pl, pt-BR, ru, tr, vi, zh-CN, zh-TW
Checking 5 translation file(s): common.json, embeddings.json, marketplace.json, mcp.json, tools.json

BACKEND Missing Translations Report:

✅ ca: No missing translations
✅ de: No missing translations
✅ es: No missing translations
✅ fr: No missing translations
✅ hi: No missing translations
✅ id: No missing translations
✅ it: No missing translations
✅ ja: No missing translations
✅ ko: No missing translations
✅ nl: No missing translations
✅ pl: No missing translations
✅ pt-BR: No missing translations
✅ ru: No missing translations
✅ tr: No missing translations
✅ vi: No missing translations
✅ zh-CN: No missing translations
✅ zh-TW: No missing translations

FRONTEND - Checking 17 non-English locale(s): ca, de, es, fr, hi, id, it, ja, ko, nl, pl, pt-BR, ru, tr, vi, zh-CN, zh-TW
Checking 10 translation file(s): account.json, chat.json, common.json, history.json, humanRelay.json, marketplace.json, mcp.json, prompts.json, settings.json, welcome.json

FRONTEND Missing Translations Report:

✅ ca: No missing translations
✅ de: No missing translations
✅ es: No missing translations
✅ fr: No missing translations
✅ hi: No missing translations
✅ id: No missing translations
✅ it: No missing translations
✅ ja: No missing translations
✅ ko: No missing translations
✅ nl: No missing translations
✅ pl: No missing translations
✅ pt-BR: No missing translations
✅ ru: No missing translations
✅ tr: No missing translations
✅ vi: No missing translations
✅ zh-CN: No missing translations
✅ zh-TW: No missing translations

✅ All translations are complete across all checked areas! - all translations complete

🚀 Changes Pushed

• Commit: - feat: add translations for commandTimeoutAllowlist setting
• Files Modified: 17 translation files ()
• CI Checks: Running (all pending, which is normal)

The translation work is complete and ready for review! 🎉

[mrubens]

@roomote-agent Remove the package.lock file and add it to .gitignore

[roomote]

👋 I've seen your request to remove the package.lock file and add it to .gitignore. I'll check out the PR branch and implement this change now.

[roomote]

✅ Task Complete!

I've successfully removed the package-lock.json file and added it to .gitignore as requested.

Changes Made

🗑️ Removed package-lock.json

• Deleted the existing package-lock.json file from the repository (7,639 lines removed)
• Used git rm to properly remove it from version control

📝 Updated .gitignore

• Added package-lock.json to the .gitignore file
• Placed it logically next to node_modules since they're related

🚀 Changes Pushed

• Commit: 31317ef93 - chore: remove package-lock.json and add to .gitignore
• Branch: feature/command-timeout-allowlist
• CI Checks: All checks are running (currently pending, which is normal)

🔍 CI Status

The following checks are currently running:

• ✅ Analyze (javascript-typescript) - pending
• ✅ check-openrouter-api-key - pending
• ✅ check-translations - pending
• ✅ compile - pending
• ✅ knip - pending
• ✅ platform-unit-test (ubuntu-latest) - pending
• ✅ platform-unit-test (windows-latest) - pending

The changes are now live and future package-lock.json files will be automatically ignored by git. 🎉