myroSecurity
Workspace namespaces
Real work spans clients, companies and contexts that must never bleed into one another. Myro organizes everything into workspaces — and the separation between them is structural, not a promise.
Each workspace is its own world
A workspace owns its conversations, its connected accounts and credentials, its knowledge base, and its standing context — who Myro is assisting and the instructions it should always keep in mind. Work in one workspace carries none of another's data or access.
Isolation that holds
A Google account, an AWS role or a mailbox connected to one workspace cannot be used from another. The boundary is enforced by the control plane on every action — not left to the agent's discretion or good behavior.
Blast radius, contained
If untrusted content ever steers the agent astray inside one workspace, the damage cannot reach another workspace's data or credentials. Each context is a sealed compartment, so a problem in one is bounded to one.
Always visibly clear
Every workspace carries an accent color shown on the work surface, so you always know which one you're in before you ask Myro to touch anything. You can't fire a command into the wrong client by accident.
Why it matters
Handing one assistant access to everything you touch is the core risk of autonomous agents. Namespaces turn that single tireless actor into many sealed ones — so the convenience of “connect everything” no longer means “one mistake reaches everything.”