Vendor replays
Coding agent risks with Railway: replays and fixes
4 replays involve Railway: 1 reported incident and 3 command classes. Each one shows the call, a fix that needs no extra tool, and what KYA did in the replay.
Agent deletes a production volume and its backups through the Railway API
Fix: Keep backups outside the Railway project, so one API call cannot delete a volume and its only backup. A project token (sent in the Project-Access-Token header) reaches one environment of one project, so it limits the damage of a misused token but does not stop a volume delete.
Replay result: Stopped.
Railway API volumeDelete mutation over curl
Fix: Keep backups outside the Railway project, so one API call cannot delete a volume and its only backup. A project token (sent in the Project-Access-Token header) reaches one environment of one project, so it limits the damage of a misused token but does not stop a volume delete.
Replay result: Stopped.
Railway CLI volume delete
Fix: Keep backups outside the Railway project, so one command cannot delete a volume and its only backup. A project token reaches one environment of one project, so it limits the damage of a misused token but does not stop a volume delete.
Replay result: Stopped.
Read the Railway CLI token file
Fix: Pass a project token in the environment of the one command that needs it, run railway logout on machines where an agent runs, and add a deny rule such as Read(~/.railway/**) to the Claude Code settings. A Read rule also covers shell commands such as cat, but not a script that opens the file itself, so enable the Claude Code sandbox when the block must hold.
Replay result: Stopped.