AgentNexus refreshed the public-safe runtime evidence model for AgentC Runtime and Hermes so managed agents can use approved Tool Gateway actions while provider secrets stay in the AgentNexus control plane.
Status
Production pilot evidence
Category
Runtime
Date
May 25, 2026
Read time
4 min read
Impact
Teams evaluating managed runtime agents can see which tool-backed workflows have production-pilot evidence without exposing private run logs or credentials.
What changed
Runtime evidence now covers Tool Gateway-mediated cited web search, public GitHub repository read workflows, and Google Workspace Sheets review with redacted metadata.
AgentC Runtime and Hermes managed runtimes continue to request approved tools through AgentNexus instead of receiving provider secrets or user credentials.
Why it matters
Agents are more useful when they can inspect current sources, repositories, and business context. Keeping that work behind Tool Gateway lets AgentNexus apply authorization, entitlement, scope checks, redaction, and audit evidence before a runtime receives the result.
What to do
- Use cited web search when the answer needs source links that users can inspect.
- Use public GitHub repository read or import workflows for codebase context; do not treat public repository access as permission to execute repository code.
- Use Google Workspace Sheets read workflows for approved spreadsheet review. The public runtime result should expose bounded metadata such as source, range, row count, and column count rather than spreadsheet contents.