Agent IAP – Little Snitch Meets 1Password for AI Agents
These days I run all my agents in ephemeral VMs on a dedicated VLAN, managed with Terraform and Ansible on top of Proxmox. Each VM runs Claude Code and Codex, talks to a dedicated GitHub account that only the agents use, and signs its commits with its own SSH key. I orchestrate the whole thing through Multica, which lets me manage agents a bit like a Kanban board.
- ▪These days I run all my agents in ephemeral VMs on a dedicated VLAN, managed with Terraform and Ansible on top of Proxmox.
- ▪Each VM runs Claude Code and Codex, talks to a dedicated GitHub account that only the agents use, and signs its commits with its own SSH key.
- ▪I orchestrate the whole thing through Multica, which lets me manage agents a bit like a Kanban board.
Hacker News (AI / LLM) files mainly under ai. We currently carry 6,263 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 | Viktor's Tech Musings & Security Paranoia |
| Canonical URL | https://vpetersson.com/2026/09/23/little-snitch-meets-1password-for-ai-agents/ |
| Publication time | Thu, 24 Sep 2026 10:40:59 +0000 |
| Retrieval time | 2026-09-24T10:45:26.703Z |
| Last seen | 2026-09-24T10:45:26.703Z |
| 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 | SIGDWXtdytwO · 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
These days I run all my agents in ephemeral VMs on a dedicated VLAN, managed with Terraform and Ansible on top of Proxmox. Each VM runs Claude Code and Codex, talks to a dedicated GitHub account that only the agents use, and signs its commits with its own SSH key. I orchestrate the whole thing through Multica, which lets me manage agents a bit like a Kanban board. Queue up a task, review the findings, move on.The reason I’m comfortable letting that run unattended is that there’s nothing on that VLAN worth stealing. No API keys, no secrets, nothing. If an agent goes off the rails or swallows a prompt injection, the blast radius is a throwaway VM and a repo I can revert.That worked great right up until the tasks stopped being about code. Build me a report from Google Analytics.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Viktor's Tech Musings & Security Paranoia.
Discussion
0 comments![AI progress is speeding up dramatically – here's why you should care [video]](/img-proxy?url=https%3A%2F%2Fi.ytimg.com%2Fvi%2FDKA5AkrQfxo%2Fmaxresdefault.jpg&w=320)
