Changelog

New updates and product improvements

Changelog

New updates and product improvements across AgentNexus product surfaces, billing, runtime operations, public documentation, and launch-readiness work.

Release model

Public-safe product updates

The changelog records meaningful product, billing, runtime, security, documentation, and operational updates. It avoids private IDs, customer-specific evidence, credentials, and unsupported compliance or uptime claims.

Access ControlAgent BuilderAgent WorkspaceApproval ActionsApproval GatesBillingCapability Tiers

Categories

Product

Updates are published only when there is user-visible impact or public-safe release evidence.

Billing

Updates are published only when there is user-visible impact or public-safe release evidence.

Runtime

Updates are published only when there is user-visible impact or public-safe release evidence.

Security

Updates are published only when there is user-visible impact or public-safe release evidence.

Docs

Updates are published only when there is user-visible impact or public-safe release evidence.

Operations

Updates are published only when there is user-visible impact or public-safe release evidence.

Updates

New updates and product improvements

Listed in reverse chronological order. Detail pages keep each update shareable and preserve legacy links.

RuntimeProduction pilot evidenceLatest

Runtime Tool Gateway evidence refresh

Managed runtimes now have clearer public evidence for Tool Gateway-mediated search, repository reads, and Google Workspace Sheets review.

Read update

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.

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.

RuntimeTool GatewayEvidence
OperationsGoverned baseline

Gateway-governed capability baseline

Channel publishing, managed browser work, Developer Mode, runtime cron, runtime skills, and runtime memory now have clearer pilot boundaries.

Read update

Impact

Customers and technical reviewers get a more accurate view of which agent powers are default, which require approval, and which remain production pilots.

What changed

AgentNexus clarified the Channel Publish webhook pilot, Managed Browser approval-gated pilot, and Developer Mode diagnostic request path.

Why it matters

High-impact agent capabilities should be easy to evaluate without making every powerful action available by default. The baseline keeps routine read workflows fast while routing browser, shell, publishing, scheduled, and memory-backed work through explicit control points.

What to do

Use default read capabilities for cited search, public repository context, and approved Google Workspace review.

OperationsRuntimeGovernance
SecurityAccess mode added

Private beta access controls

AgentNexus now has an invite-first access mode so approved workspaces keep product access while new requests enter a clear private beta queue.

Read update

Impact

Operators can run AgentNexus in an invite-based launch posture without breaking approved customer or test workspaces.

What changed

AgentNexus added approval states for organizations and users, plus a request-access path for new private beta applicants.

Why it matters

Invite-first launches need a clean boundary between public marketing pages and production actions such as agent creation, billing checkout, managed deploys, sandbox jobs, runtime tool calls, and approved workspace actions.

What to do

Existing approved workspaces continue using the product normally. New users can request access through the gate page or use an issued invite before entering the dashboard.

AccessPrivate BetaSecurity
SecurityKeyless path added

Keyless Google Cloud sandbox dispatch

Ephemeral sandbox dispatch now has a keyless Cloud Run Dispatcher path so AgentNexus can run disposable jobs without storing Google service account JSON in the Worker.

Read update

Impact

Operators can keep organization policies that block service account key creation while still preparing a durable sandbox dispatch path.

What changed

AgentNexus added a signed Worker-to-Cloud-Run dispatcher path for ephemeral sandbox jobs. The Worker can now use a dispatcher URL and HMAC secret instead of a Google access token or service account JSON.

Why it matters

This keeps sandbox execution aligned with Google Cloud organization policies that prohibit service account key creation and reduces the blast radius of Worker configuration.

What to do

Deploy the dispatcher service, grant it permission to run only the approved sandbox job, then configure the Worker with `GCP_SANDBOX_DISPATCHER_URL` and `GCP_SANDBOX_DISPATCHER_SECRET`.

SandboxGoogle CloudSecurity
DocsMetadata shipped

Public SEO metadata and social previews

Public pages now use page-specific canonical URLs, social previews, and structured data for clearer search and sharing signals.

Read update

Impact

Search engines and social platforms receive cleaner page-level signals for AgentNexus public resources without changing product capability claims.

What changed

Public pages now define self-canonical metadata instead of inheriting the homepage canonical. The docs, changelog, research, about, privacy, terms, and status pages also expose page-specific Open Graph and Twitter metadata.

Why it matters

Canonical URLs, social previews, and structured data help crawlers and sharing surfaces understand which page they are seeing, what it describes, and how it relates to the rest of the public resource library.

What to do

Share resource pages directly instead of relying on homepage previews.

SEOPublic SiteMetadata
SecurityApproval-gated beta

Google Workspace approval actions with audited execution

Calendar, Sheets, Drive, and Gmail send actions now use approval-gated server-side execution instead of runtime token access.

Read update

Impact

Teams can prepare business-file workflows without giving managed runtimes Google OAuth tokens or making Gmail send a default capability.

What changed

AgentNexus added server-side approval actions for Calendar, Sheets, and Drive writes, plus a more conservative Gmail send path for enterprise review. Google Workspace read actions remain the default GA surface.

Why it matters

Business workflow automation often needs calendar, spreadsheet, file, or email actions. Separating read actions from approval-based writes lets teams review sensitive work without exposing provider credentials to agent runtimes.

What to do

Use Google Workspace read actions for GA search and review workflows.

SecurityGoogle WorkspaceApprovals
RuntimeDirect answers shipped

Direct Tool Gateway answers for cited search and calendar reads

Tool Gateway results can now answer supported requests directly when the tool output is already complete.

Read update

Impact

Users get faster cited web search and Google Calendar read answers when the server-side tool result is already sufficient.

What changed

When the Tool Gateway produces a complete cited web search answer or Google Calendar read result, the chat route can return that answer directly without waiting for an external model pass.

Why it matters

Tool-backed answers are often already structured, cited, and ready for the user. Returning them directly reduces avoidable latency and keeps transient model capacity issues from blocking supported tool workflows.

What to do

Use cited web search for source-backed public web questions.

RuntimeTool GatewayReliability
RuntimeOne-click fallback added

Provider capacity diagnostics for agent chat

Agent chat now distinguishes temporary model capacity from deployment failures.

Read update

Impact

Operators can tell the difference between a temporary upstream model capacity issue and an AgentNexus deployment or configuration problem.

What changed

Agent chat now classifies provider capacity and overload errors as retryable provider availability events. The API returns a structured capacity code, and the dashboard explains that the issue is transient and not a deployment failure.

Why it matters

Model providers can occasionally run out of serving capacity. Clear classification keeps teams from debugging healthy deployments when the right action is to retry or select a fallback model.

What to do

Retry the chat request after a short wait when a provider-capacity message appears.

RuntimeReliabilityAgent Workspace
ProductPublished

Agent capability tiers and safe tool gateways

Pricing and workspace copy now explain which agent capabilities are generally available, gated, or enterprise-reviewed.

Read update

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.

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.

ProductSecurityPricing
RuntimeLifecycle proof added

Runtime lifecycle proof and console shortcuts

Agent Workspace now shows managed health proof, runtime-aware AA steps, and direct AgentC Runtime Control shortcuts.

Read update

Impact

Teams running managed AgentC Runtime or Hermes agents can diagnose health, gateway status, logs, and generated config faster without leaving the deployment lifecycle context.

What changed

The Runtime lifecycle card now keeps the high-level AgentNexus deployment status while adding a health proof block with health path, last check, config hash, image reference, and full instance URL copy.

Why it matters

Operators previously had to infer whether an active cloud badge meant health actually passed, which URL to copy, and where to look next. The workspace now exposes non-sensitive runtime proof and maps common deployment questions to the right inspection destination.

What to do

Use Runtime chat for a quick smoke test after a deployment turns active.

RuntimeWorkspaceOperations
SecurityReadiness controls added

Privacy controls for GDPR/CCPA readiness

AgentNexus added privacy choices, data request APIs, and clearer trust documentation for controlled beta review.

Read update

Impact

Customers and reviewers get clearer privacy controls, request paths, and review boundaries without unsupported certification claims.

What changed

Privacy choices now keep optional product analytics off until a user opts in, and browser DNT or Global Privacy Control signals keep analytics capture disabled.

Why it matters

Privacy review depends on product behavior, not only policy copy. These controls make consent, data portability, deletion intake, and retained-record boundaries visible before enterprise review.

What to do

Use Privacy choices on the privacy page or dashboard settings to manage optional analytics.

SecurityPrivacyReadiness
DocsShipped

Public Docs IA and resource navigation cleanup

The public documentation surface now uses one canonical docs entry under Resources and a search-first documentation portal.

Read update

Impact

Visitors now have one obvious path into product documentation and a clearer route from quickstart to launch review.

What changed

The landing navigation no longer shows Docs as both a top-level item and a Resources item. Resources remains the public entry point for Docs, Research, Changelog, and About.

Why it matters

A public docs portal should help buyers and builders find the right next step quickly. The new structure reduces navigation ambiguity and makes setup, testing, and launch guidance easier to scan.

What to do

Use the Quickstart when creating a first governed agent.

DocsIAResources