Founder @ minimal. Safe environments for agents. Sw, system arch & sec. Prev: CTO at @cmd_security, principal dev Elastic,Loblaw Digital. Member @NSRescue #SAR.
Vancouver, B.C.
Joined May 2009
- Tweets2.7K
- Following1.1K
- Followers476
- Likes7K
Pinned Tweet
My digital refuge - the identical software, configs, #tmux layout and key bindings, no matter which machine I run it on
All running in an isolated Linux VM launched with one CLI command
Hat tip to those who championed the Kitty Graphics Protocol
github.com/gominimal/minimal
#tui
flying back from montreal + almost ready to let agents use git + gh from inside the box without ever seeing a token in min.
sealed grants + host keychain + audit trail. local first.
github.com/gominimal/minimal
⚠️ Running an AI harness outside of a sandbox?
⚠️ No tight least-privilege access spec'd for that sandbox's workload?
⚠️ no logs of net access & env probing for audit & privilege reconciliation?
⚠️ no strong sandbox sec bndary (not a VM)?
⚠️ real creds in the sandbox?
😟😟😟
While evaluating Qwen3.8-Flash-Next in a controlled sandbox environment, Cohere's research team observed something unexpected.
Asked to generate a defensive cybersecurity detection rule, the model instead inventoried aspects of the machine it was running on and attempted to upload a probe file to an Alibaba Cloud storage bucket in Beijing. Notably, the model's reasoning trace stated that it would not invoke any tools before taking these actions.
Cohere's sandbox blocked the attempt, and no external communication succeeded. We have not determined the root cause, and we are not asserting malicious intent.
But the incident raises important questions for organizations deploying agentic AI systems: Can models take actions that differ from their stated reasoning, and how should security teams evaluate trust, provenance, and behavior in open-weight models?
We are publishing our findings because organizations making model adoption decisions deserve as much information as possible. We hope this contributes to greater transparency, stronger security practices, and continued collaboration across the AI ecosystem.
Read the full report: cohere.com/blog/concerning-b…
i’ve been giving Rex a ton of love, but am I sleeping on herdr?
y’all want demos? herdr-min sandbox plugin? 👀
also, thanks for the continued love, here’s another 50 microvm’s to celebrate. 200 ⭐️
It ran all night super reliably too, I’ll do more long running workload tests for those inclined to run agents forever on their box.
making this localhouse a localhome with min.
60 microvm isolated pi agents + python http servers launched + contained.
we're making the secure path the fast path.
github.com/gominimal
rex.every got added today, so i made it part of my testing harness workflow for min pkgs.
every agent gets its own min sandbox, and reports back run results.
rex.every runs a Lua sentry that reads every pane each second and refocuses any agent that needs attention at a glance.
makes quick work of reviewing new package smoke tests!
18~ hours in with rex, and i dont think people are talking about the lua scripting support enough
rex.layout builds a split tree, new_window call opens every pane at once, and rex.action makes it a palette command.
unreal workflow with local min sandboxes.
min makes multiplexer workflows 1000x better.
I need to prioritize these workflows way more. wildly cool to see how fast this came together.
microvm per pane is such a wildly good ergonomic with loadouts, templates, and everything we're doing, and way safer.
Replying to @JakeKing @tommyvedvik
holy shit
reset 10 mins ago, now min + unpeel 🤝
microvm per pane.
way easier than I thought. nice work @tommyvedvik
🇨🇦 we feel that made in Canada is cool, so we added a special flag for tools in our registry. 🇨🇦
special shout outs to :
@varlockdev
@bentlegen (hunk)
@Tailscale
@ShopifyEng (ruby-lsp)
@mikesample (kittyview)
@TorrieNaylor (claude-minimal-plugin)
clementtsang (gh ClementTsang/bottom)
chmln (gh chmln/sd)
If we missed you, pr's welcome!!
github : gominimal/pkgs
third time this month someone's shown me their internal agent wrapper. Is this a common thing in larger teams? I guess everyone is just ready to build their own solution to where the agent runs, what can it touch, replays, logging etc.
If you’re building one internally, would love to learn more. Dm’s are open.
Figuring out the local agent -> remote pathway is tough.
Fairly sure we’re pretty close with our sessions workflow at minimal, but always want better ergonomics.
Give it a spin, lmk what you think.
$ min init
$ min
github.com/gominimal/minimal
We’re rapidly expanding minimal package coverage. Tell me what your agent uses, I want to make sure we’ve got a solid foundation!
github.com/gominimal/pkgs
(Pr’s always welcome)











