Cube
Guides
How to keep coding agents running when you’re not at your desk: the do-it-yourself way first, then the Cube way.
- How to keep Claude Code running after you close your laptopFour ways to keep Claude Code running when your laptop closes: keep the Mac awake, tmux on a server, Claude Code cloud sessions, or an always-on computer.
- How to run Codex on a remote serverStep by step: run the Codex CLI on a remote Linux server or VPS with tmux, so it keeps working when you disconnect. Plus the managed alternative.
- How to run parallel Claude Code agentsRun several Claude Code agents on one repo without conflicts: one Git worktree per agent, each in its own tmux window, on a machine that stays on.
- Why your agent sessions die overnight, and how to fix itYour always-on home machine, but Claude Code sessions die overnight and won’t reconnect. The usual causes (sleep, network, memory, updates) and how to fix each.
- Will your agent's work survive the cloud computer?Sandboxes get reclaimed, VMs get rolled back, credit runs out. What each kind of cloud agent machine keeps, what it loses, and six habits that protect the work.
- Sandbox or VPS: where should your coding agents run?Ephemeral sandboxes or a persistent VM for Claude Code and Codex? What each side argues, which workloads fit which, and the hybrid most developers end up with.
- How to run Hermes Agent on a serverInstall Nous Research's Hermes Agent on a Linux server, connect it to Telegram, keep the gateway running, and lock it down. Official commands, step by step.
- What running Claude Code in the cloud really costsRunning Claude Code in the cloud means two bills: the model and the machine. Current Claude plan and API prices, what cloud machines cost, and example setups.