AgentNexus clarified how cited search, public GitHub import, Google Workspace actions, managed runtimes, sandboxing, managed browser sessions, and Developer Mode are separated by plan and safety boundary.
Status
Published
Category
Product
Date
May 11, 2026
Read time
4 min read
Impact
Teams can compare plans by safe agent capability instead of only credits, while high-risk shell and browser actions stay explicit and gated.
What changed
Pricing and support copy now separate GA capabilities from beta and enterprise capabilities. GA defaults include cited web search, public GitHub repository import, Google Workspace OAuth read actions, and AgentC Runtime/Hermes managed runtimes without raw shell or browser access.
Advanced positions approval-based Calendar, Sheets, and Drive write actions plus beta ephemeral cloud sandbox access as controlled paths for business workflows and disposable repository demos. Enterprise positions Gmail send approval, managed browser sessions, and Developer Mode live shell/browser as reviewed, audited, and kill-switch controlled capabilities.
Why it matters
Hosted cloud agents are more valuable when they can use search, repositories, business files, and managed runtimes. Those same powers need clear boundaries so customers know what is available by default and what requires approval.
What to do
- Use the updated pricing cards when comparing Starter, Advanced, and Enterprise.
- Treat Calendar, Sheets, Drive, and Gmail writes as approval actions executed by AgentNexus, not ordinary runtime tools.
- Import public repositories into Knowledge instead of granting runtime shell access by default.
- Request sandbox, managed browser, or Developer Mode access only for workflows that need those higher-risk surfaces.