openclaw - 💡(How to fix) Fix Feature: config flag to disable shouldFailClosedInterpreterPreflight (complex interpreter invocation check) [2 comments, 3 participants]

with error: exec preflight: complex interpreter invocation detected

TL;DR

Add a configuration flag to gate the shouldFailClosedInterpreterPreflight check, allowing chained commands like cd && node script.js to execute without errors.

Guidance

• Identify the specific use cases where the shouldFailClosedInterpreterPreflight check is blocking necessary commands, such as cron sessions running LLM agents.
• Consider adding a configuration flag like tools.exec.skipInterpreterPreflight or tools.exec.allowChainedCommands to gate this check, similar to strictInlineEval.
• Verify that the proposed flag does not introduce security vulnerabilities by reviewing the code and testing it thoroughly.
• In the meantime, apply the existing workaround of adding explicit instructions to avoid generating chained commands in cron payloads.

Example

No code snippet is provided as it is not clearly supported by the issue, but an example of the proposed configuration flag could be:

// proposed config flag
tools: {
  exec: {
    skipInterpreterPreflight: true
  }
}

Notes

The proposed solution assumes that adding a configuration flag to gate the shouldFailClosedInterpreterPreflight check is feasible and does not introduce security risks. Further review and testing are necessary to confirm this.

Recommendation

Apply the workaround of adding explicit instructions to avoid generating chained commands in cron payloads until a configuration flag is implemented to gate the shouldFailClosedInterpreterPreflight check.