[eshurakov]

Summary

• Bump TOOL_CGROUP_RESERVE_MB from 1024 to 2048 in cloud-agent-next wrangler config
• Leaves more memory reserved outside the tool cgroup under enforce mode

Test plan

• Confirm wrangler vars show TOOL_CGROUP_RESERVE_MB=2048 after deploy
• Spot-check a session with tool cgroup enabled still starts and enforces limits

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

One-line config bump of TOOL_CGROUP_RESERVE_MB from 1024 to 2048 in cloud-agent-next. Verified against the wrapper's cgroup logic: in enforce mode the tool slice cap is MemTotal − reserve, so this reserves more memory for the server/runtime slice as intended. Even the smallest sandbox instance type (4096 MiB) keeps a ~2 GiB tool cap, safely above the 1 GiB MIN_CAP_BYTES floor, so enforcement stays active everywhere. High confidence.

Files Reviewed (1 files)

• services/cloud-agent-next/wrangler.jsonc

---

_{Reviewed by kimi-k3 · Input: 53.7K · Output: 7.1K · Cached: 309.2K}

_{Review guidance: REVIEW.md from base branch main}