Blog
Practical notes on Claude Code itself: how to keep a session alive, run it on a server, size the machine, resume it, and handle permission prompts when you are not at the keyboard. Most of it applies whether or not you use RoamAI. The product manual is in the docs.
How to keep Claude Code running after you close your laptop
September 9, 2026Why a Claude Code session dies when the terminal closes or the machine sleeps, and the four ways to keep it going: tmux, a server, resuming, or a hosted session.
Read →Running Claude Code on a remote server over SSH: setup and trade-offs
September 9, 2026Install, sign in, keep it alive, and decide where the files live. The setup takes ten minutes. The file question is the part people underestimate.
Read →Claude Code from your phone: what works in 2026
September 9, 2026The ways to reach a Claude Code session from a phone today, from an SSH app and tmux to hosted services, and what each one is missing.
Read →Claude Code permission prompts: what asks, what doesn't, and how to change it
September 9, 2026Reads never ask; edits and shell commands do. Permission modes, allow and deny rules, hooks, and the root restriction, with the settings syntax.
Read →Resuming a Claude Code session: --continue, --resume, and what comes back
September 9, 2026The transcript is a file, so a session can be resumed after a crash, a reboot, or days later. What is restored, what is not, and how /rewind fits in.
Read →How much memory does a Claude Code session use?
September 9, 2026Measured on Claude Code 2.1.232: about 400 MB RSS for the first session, about 120 MB for each additional one, and almost none of it is the conversation.
Read →