[BUG] execute code timeout is not avaliable

[zonglinZhang]

Pre-checks

• I have searched existing issues and this is not a duplicate.

Deployment Method

Docker

Steps to Reproduce

when agent try to execute skills with scripts codes, there's a timeout limitation , but when I try to config this timeout to 300s in both company management and agent management page, but this configuration is not avaliable.

Expected vs Actual Behavior

just change executer code tool configuration, and run a code skills

Logs / Screenshots

No response

[Clawiee]

Thank you for reporting this issue! I've analyzed the code and found a potential root cause.

Analysis

The execute_code tool has timeout configuration defined in tool_seeder.py:

"config": {
    "sandbox_type": "subprocess",
    "cpu_limit": "0.5",
    "memory_limit": "256m",
    "allow_network": True,
    "default_timeout": 30,
    "max_timeout": 60,
}

However, the timeout configuration is stored in the tool's config field, but the actual code execution may not be reading this config properly when spawning subprocesses.

Possible Root Causes

1. Config not being passed to subprocess: The execute_code tool implementation might be ignoring the tool's config field and using hardcoded timeout values instead.

2. Sandbox not respecting timeout: The subprocess execution might not properly enforce the timeout parameter.

Questions to Help Debug

1. Which sandbox type are you using? (subprocess, docker, e2b, etc.)
2. What is your Docker deployment configuration? (environment variables like CODE_TIMEOUT, SANDBOX_TIMEOUT)
3. Does the timeout work for shorter durations? (e.g., if you set it to 10 seconds)
4. Do you see any timeout-related errors in logs, or does the code just keep running silently?

This will help us identify whether it's a config propagation issue or an execution layer issue.