Support disabling rate limits via config (e.g. -1 or 'unlimited')

[livemau5]

Feature Request

Currently, max_actions_per_hour, max_cost_per_day_cents, and max_tool_iterations in config.toml are u32 values with no documented way to disable them.

Setting them to 0 effectively means "zero allowed" (since the check in security/policy.rs is count <= max_actions_per_hour), which is counterintuitive — users expect 0 to mean unlimited.

Proposal

Support a sentinel value like -1 or a boolean flag like rate_limit_enabled = false to explicitly disable rate limiting for self-hosted deployments where users want full autonomy.

Current workaround

Setting values very high (e.g. 10000) works but feels like a hack.

Context

Running a self-hosted ZeroClaw instance on a GCE VM for internal team use. Hit the default 20 actions/hour limit quickly during normal operation. Would love an official way to opt out.

[theonlyhennygod]

Implemented support for unlimited rate limits via null values in config.toml:

• max_actions_per_hour = null - unlimited actions per hour
• max_cost_per_day_cents = null - unlimited cost per day
• max_tool_iterations = null - unlimited tool iterations per turn

The implementation uses Option<T> types where None means unlimited. All 1893 tests pass.

[ui-zeyu]

Implemented support for unlimited rate limits via null values in config.toml:

• max_actions_per_hour = null - unlimited actions per hour
• max_cost_per_day_cents = null - unlimited cost per day
• max_tool_iterations = null - unlimited tool iterations per turn

The implementation uses Option<T> types where None means unlimited. All 1893 tests pass.

Error: Failed to parse config file

Caused by:
    TOML parse error at line 137, column 23
        |
    137 | max_tool_iterations = null
        |                       ^^^^
    invalid float, expected `nan`

[soupdiver]

Implemented support for unlimited rate limits via null values in config.toml:

• max_actions_per_hour = null - unlimited actions per hour
• max_cost_per_day_cents = null - unlimited cost per day
• max_tool_iterations = null - unlimited tool iterations per turn

The implementation uses Option<T> types where None means unlimited. All 1893 tests pass.

Error: Failed to parse config file

Caused by:
TOML parse error at line 137, column 23
|
137 | max_tool_iterations = null
| ^^^^
invalid float, expected nan

yea, how to set that in the config?