CLAWSOLATOR ALPHABeta release planned · License under considerationRead what is verified
Resources / Multi-agent operations

One runaway worker should not own the whole house.

Resource governance is different from repairing a memory leak. Operators need enforceable limits, headroom visibility and honest reporting about which workloads are actually controlled.

Historical public incidents · XMAN 0.4.76a1 resource policy alpha · Not a universal OOM cure

The problems operators experienced

Feature request/bug report · Closed as not planned (stale)

Worker processes exhaust a VPS

Reporter described four worker processes exhausting a 7.5GB host and asked for memory ceilings/spawn caps.

XMAN controls enrolled container allocations; not all host processes or arbitrary gateway leaks.

Read the primary source
Bug report · Closed as not planned

Gateway memory leak leading to repeated OOM

Reporter documented RSS growth and periodic OOM on an older Gateway build.

XMAN does not fix this leak.

Read the primary source
Bug report · Closed/fixed

QMD memory contention in multi-agent deployments

Reporter described embedding initialization for disabled agents increasing memory demand.

Upstream issue closed; Clawsolator is not the fix.

Read the primary source

A bounded answer rather than a magical cure

XMAN’s resource path is designed for finite, enrolled container budgets, readback and policy boundaries. A manager can authorize CPU/RAM changes only within the operator’s recorded constraints. The system does not automatically control every host workload, reserve RAM that the kernel has not reserved, or repair arbitrary JavaScript memory leaks.

That distinction is a selling point: making exact promises rather than pretending any green dashboard controls the whole machine.

The family checks the house budget

The next proof obligation

Demonstrate an allowed resource.prepare/commit and a denied over-limit request on the actual rootless Podman host. Include the before/after cgroup resource values and clarify how many containers are enrolled versus unrelated host processes.