The Sandbox and Permission Seams in Nexo
Nexo's four sandbox tiers and four permission modes, and how an email agent gets write access to one folder and nothing else, enforced in code.
I'm Mario Alberto, a software engineer and entrepreneur based in Colima, México. I'm the creator of Rails MCP Server and former CTO/co-founder of Aoorora, where I architected a core banking platform in Ruby on Rails that enabled lending startups to build on modern, secure infrastructure. I spend my time at the intersection of Ruby on Rails and AI—building tools that help developers work smarter. When I'm not writing code, I'm documenting territory, popular culture, and memory through photography.
Nexo's four sandbox tiers and four permission modes, and how an email agent gets write access to one folder and nothing else, enforced in code.
Fan three email source agents out with Nexo.concurrent: bounded concurrency, ordered results, and a sequential fallback when the async gem is missing.
Wrap three email source agents in a Nexo workflow that skips what it cannot run, records every step in an event log, and still finishes when a source fails.