We Deleted Every Disk in Our AI Agent Fleet
AI AgentAi Agent DevelopmentWhy We Deleted Every Disk in Our AI Agent Fleet (Hint: Object Storage)Naveen Gupta7 min read·6 days ago--ListenSharePress enter or click to view image in full sizeOur storage bill was upside down.We run hundreds of dedicated AI-agent VMs. Each agent has its own /workspace, where chats, files, cloned repositories, and credentials need to survive a restart. The normal answer is a persistent disk per machine.
- ▪AI AgentAi Agent DevelopmentWhy We Deleted Every Disk in Our AI Agent Fleet (Hint: Object Storage)Naveen Gupta7 min read·6 days ago--ListenSharePress enter or click to view image in full sizeOur storage bill was upside down.We run hundreds
- ▪Each agent has its own /workspace, where chats, files, cloned repositories, and credentials need to survive a restart.
- ▪The normal answer is a persistent disk per machine.
Hacker News (AI / LLM) files mainly under ai. We currently carry 4,328 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Medium |
| Canonical URL | https://medium.com/@naveensky/why-we-deleted-every-disk-in-our-ai-agent-fleet-hint-object-storage-9ba99b3e6ad8 |
| Publication time | Mon, 10 Aug 2026 17:52:34 +0000 |
| Retrieval time | 2026-08-10T18:00:44.247Z |
| Last seen | 2026-08-10T18:00:44.247Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | l-VGE5LoK1uQ · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
AI AgentAi Agent DevelopmentWhy We Deleted Every Disk in Our AI Agent Fleet (Hint: Object Storage)Naveen Gupta7 min read·6 days ago--ListenSharePress enter or click to view image in full sizeOur storage bill was upside down.We run hundreds of dedicated AI-agent VMs. Each agent has its own /workspace, where chats, files, cloned repositories, and credentials need to survive a restart. The normal answer is a persistent disk per machine. We did that. It worked.Then we looked at the invoice.We had provisioned roughly 900 GB of persistent disk across a fleet that spent most of its time asleep. Those disks cost $137.93 in a $152.93 month.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Medium.