shedix

Blog

Posts about claude code

  1. Claude Code's cloud sessions or your own machine: which to use when

    What Claude Code's cloud sessions do well, where they stop, and when a Linux machine of your own fits better, checked against Anthropic's docs.

  2. Three ways to code from your phone, and what each costs

    A home computer over Tailscale, an always-on VM with mosh and tmux, or an hourly VM that sleeps: what each needs, how it copes with lost signal, and the cost.

  3. Seven coding-agent disasters, and which ones a separate machine would have stopped

    Seven real incidents where coding agents deleted files, disks or databases, where each agent ran, and which ones a separate machine would have stopped.

  4. Container, microVM or full VM: choosing a box for a coding agent

    What containers, gVisor, microVMs and full VMs each put between a coding agent and your computer, when the agent needs Docker, and what none of them fix.

  5. Move a Claude Code conversation to another machine

    Where Claude Code stores each conversation, how to copy one to another machine and resume it with claude --resume, and what doesn't come along.

  6. Keep Claude Code running after you close your laptop

    Why a laptop agent stops when the lid closes or the Wi-Fi drops, and how to keep Claude Code working on a remote machine inside tmux.

  7. Use Claude Code from your phone with Remote Control

    How Claude Code's Remote Control lets you continue a session running on a remote machine from the Claude app, what it needs, and how shedix sets it up.

  8. Give your coding agent its own machine

    What a coding agent can reach on your main computer, what Claude Code and Codex permission modes and sandboxes cover, and why a separate VM is cleaner.