The "VM Memory" line item is not the same as Agent Usage (LLM tokens). Agent Usage on your last invoice was only $0.52. VM Memory is the compute cost of a sandbox (VM) that was created on 2026-08-13 and has been running continuously since then, billing memory just like any other running service. On the last invoice it covered only ~3 days and came to $5.04, but the current cycle has a full month of runtime, which aligns with the ~$43 you're seeing now. If you're no longer using that sandbox, removing it will stop those charges immediately. To prevent future Agent-related charges, you can set your Agent hard limit to $0 from your workspace usage page under "Update limits."

Your most recent invoice was $177.57. Here is the breakdown:

Memory:          $127.25
Network egress:   $23.01
Pro plan:         $20.00
vCPU:             $17.55
VM Memory:         $5.04
Disk:              $4.07
Agent Usage:       $0.52
VM vCPU:           $0.13
─────────────────────────
Subtotal:        $197.57
Pro included:    -$20.00
Total:           $177.57

The largest driver is regular Memory at $127.25. You can set up usage alerts, limits, and view your usage breakdown - including per service costs - by heading to railway.com/workspace/usage.

okay so the sandbox VM, if it is running and im not using it how is it incurring charges? I'm assuming the VM sandbox is what spawns when you create a "cloud agent" but again, I used it once to run a claude code prompt and haven't touched it since. I also thought it had sleeping functionality?

Cloud agents have no idle timeout. Disconnecting leaves the VM running and billing continues, even with no client connected. You need to explicitly sleep or delete the agent to stop compute charges (railway ca sleep <agent-name> or railway ca delete <agent-name>). This is different from sandboxes, which do auto-tear-down after inactivity. Sleeping the agent retains your files but stops billing; deleting it removes everything and stops billing permanently.

okay then there is an issue as I have never created a VM ?

This is what i have created previously. Does this spawn a VM Sanbox? because I am confused, by what you are stating and to my understanding I've not created a VM, I have only created the cloud agent and if what you are stating about the sanboxes is true then why did it continue to incur charges if im not using it ?

A cloud agent is a VM. Creating one through railway ca provisions a virtual machine, which is where the "VM Memory" and "VM vCPU" charges on your bill come from. Cloud agents have no idle timeout and keep running after you disconnect, so compute billing continues until you explicitly stop them. Sandboxes are different and do have an idle timeout, but cloud agents do not. You can stop it now with railway ca sleep <agent-name> (retains files, stops billing) or railway ca delete <agent-name> (removes everything, stops billing permanently).