Node command timeout: invokeTimeoutMs vs timeoutMs
Hey! I'm running Clawdbot on a VPS with a Mac connected as a remote node via Tailscale. Node commands work but take ~8-10s round-trip due to network latency.
Issue: When using the nodes tool (action: run), the invokeTimeoutMs parameter doesn't seem to extend the gateway timeout β it still times out at 10s even when I set invokeTimeoutMs: 30000.
Workaround: Using timeoutMs: 30000 instead works correctly and the command completes.
Question: Is this expected behavior? Should invokeTimeoutMs control the gateway-level timeout, or is timeoutMs the correct parameter for this? The docs mention both but it's not clear which one controls the tool call timeout from the agent's perspective.
Setup:
β’ Clawdbot 2026.1.22
β’ Gateway on VPS (bare metal, no Docker)
β’ Mac node via Tailscale
β’ Commands execute successfully (visible in system logs) but tool returns timeout error when using invokeTimeoutMs
Thanks!
Issue: When using the nodes tool (action: run), the invokeTimeoutMs parameter doesn't seem to extend the gateway timeout β it still times out at 10s even when I set invokeTimeoutMs: 30000.
Workaround: Using timeoutMs: 30000 instead works correctly and the command completes.
Question: Is this expected behavior? Should invokeTimeoutMs control the gateway-level timeout, or is timeoutMs the correct parameter for this? The docs mention both but it's not clear which one controls the tool call timeout from the agent's perspective.
Setup:
β’ Clawdbot 2026.1.22
β’ Gateway on VPS (bare metal, no Docker)
β’ Mac node via Tailscale
β’ Commands execute successfully (visible in system logs) but tool returns timeout error when using invokeTimeoutMs
Thanks!
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
86,471Members
Resources
Similar Threads
Was this page helpful?
