openclaw - 💡(How to fix) Fix Bundled openshell module crashes exec tool — requires TELEGRAM_BOT_TOKEN even when standalone CLI is used [1 comments, 1 participants]

[tools] exec failed: [openshell] Failed to start: Error: TELEGRAM_BOT_TOKEN is required. at loadConfig (file:///usr/lib/node_modules/openclaw/node_modules/openshell/dist/config.js:37:15)

Fix Plan

To resolve the issue, we need to modify the openshell module to not require the TELEGRAM_BOT_TOKEN environment variable when Telegram integration is not configured. We can achieve this by updating the config.js file in the openshell module.

Code Changes

We need to update the loadConfig function in config.js to check if Telegram integration is configured before requiring the TELEGRAM_BOT_TOKEN environment variable.

// config.js
function loadConfig() {
  // ... existing code ...

  if (process.env.TELEGRAM_INTEGRATION_ENABLED === 'true') {
    if (!process.env.TELEGRAM_BOT_TOKEN) {
      throw new Error('TELEGRAM_BOT_TOKEN is required.');
    }
  }

  // ... existing code ...
}

Alternatively, we can modify the OpenClaw configuration to prefer the standalone OpenShell CLI when sandbox.backend is set to "openshell" and the standalone CLI is available.

// openclaw.config.js
module.exports = {
  // ... existing config ...
  sandbox: {
    backend: 'openshell',
    useStandaloneCli: true,
  },
};

Verification

To verify the fix, restart the OpenClaw service and check if the exec tool calls are working as expected in sandboxed sessions. You can also check the logs to ensure that the TELEGRAM_BOT_TOKEN error is no longer present.

Extra Tips

To prevent regressions, make sure to update the openshell module to the latest version and test the changes thoroughly. Additionally, consider adding a check to ensure that the standalone OpenShell CLI is available before attempting to use it.