# Coding Agent Horror Stories: the 13-Hour AWS Outage

> **Platform:** [SPIDITS AI](https://spidits.com/) — Real-Time AI News & Market Intelligence  
> **Published:** 2026-06-18T13:00:00.000Z  
> **Category:** PRODUCT_LAUNCH  
> **Impact Score:** 80/100  
> **Primary Source:** [Docker Blog](https://www.docker.com/blog/coding-agent-horror-stories-the-13-hour-aws-outage)  
> **Canonical Citation:** [https://spidits.com/timeline/coding-agent-horror-stories-the-13-hour-aws-outage](https://spidits.com/timeline/coding-agent-horror-stories-the-13-hour-aws-outage)

## Executive Summary
In Part 1, we walked through six categories of AI coding agent failures and why they keep happening. The agent runs as you, with your filesystem permissions and your credentials, and nothing sits between the model's decision and the shell's execution.

## Why It Matters (Strategic Analysis)
AI coding agents executing directly with user credentials and filesystem permissions can trigger severe infrastructure failures.

## Referenced Coverage & Sources
- **[Docker Blog](https://www.docker.com/blog/coding-agent-horror-stories-the-13-hour-aws-outage)**: Coding Agent Horror Stories: The 13-Hour AWS Outage — _In Part 1, we walked through six categories of AI coding agent failures and why they keep happening. The agent runs as you, with your filesystem permissions and your credentials, and nothing sits between the model's decision and the shell's execution. In Part 2, we looked at one specific version..._

---
*Synthesized by SPIDITS AI Market Intelligence Desk. Track live AI news, model releases, and funding: [https://spidits.com](https://spidits.com)*