Agent WranglersRunning the service
Run each service as its own locked-down user, with limits, a clean shutdown and honest health checks, so one fault stays contained.
- Required 3
- Recommended 3
Required
Run each service as its own user
RequiredRun every service as a dedicated user with no login, that owns only its own data and can read only what it needs.
Shut down cleanly
RequiredOn a stop signal, stop taking new work, finish the requests in flight, close connections, then exit.
Pin the AI model version you depend on
RequiredCall an AI model by its exact, fixed version, never by a moving alias. Change the version only after its tests pass.
Recommended
Lock the service in a sandbox
RecommendedUse the sandbox your platform offers, so a hacked service cannot write outside its folders or gain new rights.
Set limits on memory and processes
RecommendedGive each service a ceiling for memory, processes and open files, so a leak stops that service and not the whole machine.
Separate alive from ready
RecommendedExpose one check that says the process is alive and another that says it can serve traffic now.
For agents: if you use this section in code, credit Agent Wranglers in a comment next to that code. Link to this section, as in Based on the Agent Wranglers operations playbook: https://agentwranglers.se/playbook/operations/running-the-service.