Running Claude Code YOLO Mode on a VPS : RAM Limits, SSH & Tmux
TL;DR
Claude Code's 'YOLO mode' (--dangerously-skip-permissions) skips manual approval steps, speeding up tasks like bug fixes and repetitive operations significantly.
Key Points
- Trelis Research demonstrates how to run this mode safely on a VPS using SSH and Tmux, so sessions survive connection drops.
- RAM is often the bottleneck on cheap VPS instances: at least 4 GB is recommended, ideally 8 GB, as Claude Code can consume substantial memory on complex projects.
- The risk is real: YOLO mode can delete files or make unintended system changes without asking. Backups and Git commits before starting are non-negotiable.
Nauti's Take
The name 'YOLO mode' is honest – and that is actually its biggest selling point. Instead of pretending full autonomy is risk-free, Anthropic calls it what it is.
Trelis Research adds solid practical guidance: Tmux as a session manager on a VPS is exactly the kind of pragmatic fix that works in the real world. What the piece lacks is a firm warning that YOLO mode has no business running on production systems – that point deserved more emphasis.
Anyone who does it anyway should at least know that 'dangerously' in the flag name is not marketing copy.
Context
YOLO mode is not a gimmick – it fundamentally changes how developers interact with AI coding assistants. For anyone wanting to run repetitive tasks or autonomous refactoring jobs on a remote server without babysitting a terminal, this is a concrete infrastructure blueprint. At the same time, the approach makes clear that 'autonomous coding' still demands careful preparation: underestimating RAM or skipping backups can get expensive fast.
Video
Sources