Never Trust Your AI Agent's Own Sandbox
For the last few weeks I’ve been trying to sandbox agents on my machine. Coding agents and other autonomous ones that fire on a trigger and run a workflow while I’m not watching. Every day Claude Code updates itself and pulls 300 to 400 MB, sometimes a gigabyte.
- ▪For the last few weeks I’ve been trying to sandbox agents on my machine.
- ▪Coding agents and other autonomous ones that fire on a trigger and run a workflow while I’m not watching.
- ▪Every day Claude Code updates itself and pulls 300 to 400 MB, sometimes a gigabyte.
Hacker News (AI / LLM) files mainly under ai. We currently carry 4,573 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 | Chandrapal Badshah |
| Canonical URL | https://badshah.io/blog/never-trust-your-ai-agents-sandbox/ |
| Publication time | Wed, 12 Aug 2026 11:02:25 +0000 |
| Retrieval time | 2026-08-12T11:11:30.463Z |
| Last seen | 2026-08-12T11:11:30.463Z |
| 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 | Lh_iOpfdGQZ3 · 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
For the last few weeks I’ve been trying to sandbox agents on my machine. Coding agents and other autonomous ones that fire on a trigger and run a workflow while I’m not watching. I have Little Snitch on my laptop. Every day Claude Code updates itself and pulls 300 to 400 MB, sometimes a gigabyte. Some of that is probably several instances grabbing the same update at once. 1.41 GB down from claude.ai just after connecting to the internet. Then I ran it under nono, which sandboxes a process at the kernel level and tells you what it denied. That’s how I found it reaching for markdown files in my notes, because a skill still had references pointing there. It was also trying to talk to Chrome, because I have the Claude for Chrome browser extension installed. nono blocked both.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Chandrapal Badshah.
Discussion
0 commentsMore from Chandrapal Badshah
