HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
kstenerud
yoloai
Go2026–2026
kstenerud / yoloai

yoloai

Your agent is a security risk, so treat it like one. yoloAI does AI agent sandboxing right.

4Distinct people
52Mentions
0Explicit recommenders
255GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Your agent is a security risk, so treat it like one. yoloAI does AI agent sandboxing right.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:57:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week52 dated mentions

Observed mentions: 2026-02-25 20:23:05 UTC to 2026-08-20 10:59:24 UTC. Weeks start Monday, UTC.

024682026-02-23 00:00:00 UTC to 2026-03-02 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsFeb 232026-03-02 00:00:00 UTC to 2026-03-09 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-03-09 00:00:00 UTC to 2026-03-16 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2026-03-16 00:00:00 UTC to 2026-03-23 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-03-23 00:00:00 UTC to 2026-03-30 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2026-03-30 00:00:00 UTC to 2026-04-06 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-04-06 00:00:00 UTC to 2026-04-13 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-04-13 00:00:00 UTC to 2026-04-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-20 00:00:00 UTC to 2026-04-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-27 00:00:00 UTC to 2026-05-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-04 00:00:00 UTC to 2026-05-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-11 00:00:00 UTC to 2026-05-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-18 00:00:00 UTC to 2026-05-25 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 commentsMay 182026-05-25 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-06-01 00:00:00 UTC to 2026-06-08 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-06-08 00:00:00 UTC to 2026-06-15 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2026-06-15 00:00:00 UTC to 2026-06-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-22 00:00:00 UTC to 2026-06-29 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-06-29 00:00:00 UTC to 2026-07-06 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-07-06 00:00:00 UTC to 2026-07-13 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-07-13 00:00:00 UTC to 2026-07-20 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2026-07-20 00:00:00 UTC to 2026-07-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-27 00:00:00 UTC to 2026-08-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-03 00:00:00 UTC to 2026-08-10 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-08-10 00:00:00 UTC to 2026-08-17 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-08-17 00:00:00 UTC to 2026-08-24 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 17

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 232026-02-23 00:00:00 UTC2026-03-02 00:00:00 UTC202
Mar 22026-03-02 00:00:00 UTC2026-03-09 00:00:00 UTC101
Mar 92026-03-09 00:00:00 UTC2026-03-16 00:00:00 UTC615
Mar 162026-03-16 00:00:00 UTC2026-03-23 00:00:00 UTC202
Mar 232026-03-23 00:00:00 UTC2026-03-30 00:00:00 UTC606
Mar 302026-03-30 00:00:00 UTC2026-04-06 00:00:00 UTC202
Apr 62026-04-06 00:00:00 UTC2026-04-13 00:00:00 UTC303
Apr 132026-04-13 00:00:00 UTC2026-04-20 00:00:00 UTC000
Apr 202026-04-20 00:00:00 UTC2026-04-27 00:00:00 UTC000
Apr 272026-04-27 00:00:00 UTC2026-05-04 00:00:00 UTC000
May 42026-05-04 00:00:00 UTC2026-05-11 00:00:00 UTC000
May 112026-05-11 00:00:00 UTC2026-05-18 00:00:00 UTC000
May 182026-05-18 00:00:00 UTC2026-05-25 00:00:00 UTC404
May 252026-05-25 00:00:00 UTC2026-06-01 00:00:00 UTC101
Jun 12026-06-01 00:00:00 UTC2026-06-08 00:00:00 UTC303
Jun 82026-06-08 00:00:00 UTC2026-06-15 00:00:00 UTC404
Jun 152026-06-15 00:00:00 UTC2026-06-22 00:00:00 UTC000
Jun 222026-06-22 00:00:00 UTC2026-06-29 00:00:00 UTC303
Jun 292026-06-29 00:00:00 UTC2026-07-06 00:00:00 UTC101
Jul 62026-07-06 00:00:00 UTC2026-07-13 00:00:00 UTC101
Jul 132026-07-13 00:00:00 UTC2026-07-20 00:00:00 UTC808
Jul 202026-07-20 00:00:00 UTC2026-07-27 00:00:00 UTC000
Jul 272026-07-27 00:00:00 UTC2026-08-03 00:00:00 UTC000
Aug 32026-08-03 00:00:00 UTC2026-08-10 00:00:00 UTC101
Aug 102026-08-10 00:00:00 UTC2026-08-17 00:00:00 UTC303
Aug 172026-08-17 00:00:00 UTC2026-08-24 00:00:00 UTC101

What Hacker News says

6 sources
Not famous last words ;-) I've already shipped this and use it myself every day. I'm the author of yoloAI (https://github.com/kstenerud/yoloai), which is built around exactly this model. The agent runs inside a Docker container or containerd vm (or seatbelt container or Tart vm on mac), against a full copy of your project directory. When it's done, `yoloai diff` gives you a unified diff of everything it changed. `yoloai apply` lands it. `yoloai reset` throws it away so you can make the agent try again. The copy lives in the sandbox, so your working tree is untouched until you explicitly say so. The merge step turned out to be straightforward: just use git under the hood. The harder parts were: (a) making it fast enough that the copy doesn't add annoying startup overhead, (b) handling the .pyc/.venv/.git/hooks concern you raised (they're e
Read the rest
xcluded from the diff surface by default), and (c) credential injection so the agent can actually reach its API without you mounting your whole home dir. Leveraging existing tech is where it's at. Each does one thing and does it well. Network isolation is done via iptables in Docker, for example. Still early/beta but it's working. Happy to compare notes if you're building something similar.
In Go hard on agents, not on your filesystem
There are two primary issues to solve: 1: Protecting against bad things (prompt injections, overeager agents, etc) 2: Containing the blast radius (preventing agents from even reaching sensitive things) The companies building the agents make a best-effort attempt against #1 (guardrails, permissions, etc), and nothing against #2. It's why I use https://github.com/kstenerud/yoloai for everything now.
In "Disregard That" Attacks
That's a bit better, but the subtleties of even the basic shell commands is enough that you still need to be conservative. Plus there's still the issue of the approve/deny mechanism being part of the agent process, and thus subvertable by the agent. I took a different approach with https://github.com/kstenerud/yoloai - The agent is put entirely in a container or VM sandbox (docker, podman, gvisor, kata, seatbelt, tart) - The agent safely runs with --dangerously-skip-permissions because it can't touch your files or system directly. You can even restrict its network access. - You review the results of its work using "yoloai diff mysandbox" - You selectively apply the results of its work using "yoloai apply mysandbox". Commits it makes are available to cherry pick or just accept whole.
In Claude Code auto mode: a safer way to skip permissions

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.