shedix

Blog

Posts about costs

  1. Auto-sleep for agent machines: telling busy from idle

    How shedix decides an agent's machine is idle: what it counts every 30 seconds, what it refuses to count, how quiet idle really is, and how others decide.

  2. 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.

  3. 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.

  4. What a coding agent's computer costs, compared hour for hour

    A 4 vCPU, 8 GB agent machine priced across sandboxes, devboxes, VPSes and shedix as of 2026-11-02, with idle rules, what survives a stop, and caps.

  5. Home server, VPS or cloud VM: where to keep your coding agent

    A computer at home, a monthly VPS or an hourly cloud VM for your coding agent: the cost at 4 hours a day, 8 hours a day and always on, and what can break.

  6. What an always-on agent machine costs

    What an agent machine costs by the hour and month at shedix's prices, what leaving it on adds up to, and how auto-sleep, stopping and deleting change it.

  7. Run your test suite on a bigger machine

    Send a slow test suite from a laptop agent to a remote Linux machine with rsync, ssh and tmux, bring the results back, and work out the cost of each run.