Release Notes CodeNOW 7.20 – November 2026

Agent Gateway

Every account can now turn on its own Agent Gateway — a single, secured entry point through
which AI agents reach models, MCP tools, and each other. Authentication, tool access, and
observability are handled in one controlled place, so you no longer have to wire each agent by
hand. Enable it in Account settings › AI Gateway.

Key Capabilities:

• Automatic Tool Registration: CodeNOW's own MCP server and the MCP servers of your data-plane tools are registered in the gateway automatically and kept in sync when data planes change
• AI Menu: A new AI menu gives quick access to the gateway's Logs and Analytics
• Dedicated Permissions: Access to the gateway is managed with separate viewer and admin permissions

Benefits:

• One place to control and audit all agent traffic
• New tools become available to agents without manual setup
• Clear visibility into what your agents call and how often

AI Agents and Agent Swarms

A new Agent configuration tab lets you define how an agent runs and who can talk to it.
Agent-to-agent (A2A) communication and access control become configuration instead of code — and
are secured by default.

Key Capabilities:

• Service Account Identity: Choose the service account the agent runs as — its identity for models, tools, and other agents
• Admin Console Access: Decide which users and teams can open the agent's own console
• A2A Endpoint: Keep the agent private, open it to everyone in the account, or allow only selected teams and service accounts
• A2A Connections: Agents in the same swarm find each other automatically; agents from other swarms are connected by name and mapped to a concrete swarm, environment, and agent per environment
• Connection Properties: A dialog shows the environment variables the agent receives and how to use them in its configuration files
• Automatic Gateway Registration: On deploy, exposed agents are registered in the Agent Gateway together with their access rules, and the deploy detail warns you if an agent could not be registered
• Clean Undeploy: Undeploying a swarm is now a tracked job that removes everything the deploy created

Benefits:

• Multi-agent systems wired together without custom glue code
• Least-privilege access for every agent out of the box
• Predictable deploys and clean teardowns

Service Accounts

Service accounts are a new kind of identity for automation and agents. Automation no longer
needs personal credentials — access is explicit, auditable, and bound to a team.

Key Capabilities:

• User or Team Ownership: A service account is owned by a user or a team and can be used by agents or as the identity behind API keys
• Two Permission Modes: Explicit — its own permissions, never more than the owner has — or Follow — inherits the owning team's permissions
• Redesigned Permissions Editor: A clearer way to grant and review permissions; changing the owner or mode runs as a tracked job
• Secrets: Attach secrets that are delivered to the agent as environment variables

Benefits:

• No more shared personal tokens in pipelines and integrations
• Permissions that can never exceed those of the owner
• Access that stays with the team when people change roles

Self-Managed Teams

Finer team roles let team owners delegate without granting account-wide admin rights, so teams can
run themselves and admins don't have to handle every change.

Key Capabilities:

• New Team Roles: Member, admin, edit permissions, and service account manager
• Team Directory: Anyone in the account can look up a team and its members
• My Teams: See all your teams together with your effective permissions

Benefits:

• Day-to-day team changes without waiting on account admins
• Transparency about who belongs where and who can do what

Default Configuration

A new Default configuration card on component and agent dashboards replaces the separate
runtime and connected-services cards. The defaults that live in your repository can now be
reviewed and edited directly from CodeNOW, with full git history.

Key Capabilities:

• Branch or Release: Pick a branch to edit or a release to view read-only — in the same layout as the deployment configuration
• One Commit per Save: Saving on a branch creates a single commit in your repository
• Git Locations: Every section shows where in git it is stored, with direct links
• Connected Services by Name: Declare connected services by name and type; the concrete instance is chosen per environment

Benefits:

• Configuration changes are reviewable and traceable like any other code change
• No need to switch between CodeNOW and your repository to adjust defaults
• The same defaults work across environments with different service instances

Deployment Configuration and Compare

Promoting configuration between versions and environments is now faster and safer.

Key Capabilities:

• Connected Services Table: Connected services are shown as a clear table with the instance chosen for each environment
• Redesigned Compare: Across all tabs, see the result next to the compared value and take a value over with Use
• Only Changes Filter: Focus on what actually differs
• Side-by-Side File Merge: Merge configuration files side by side, showing only changes or the full file
• Consistent Preview: The Preview configuration dialog uses the same view

Benefits:

• Fewer mistakes when promoting configuration
• Faster reviews with differences highlighted in context

Public API and MCP

Everything new is scriptable and available to AI assistants through the CodeNOW MCP server.

Key Capabilities:

• Team Features in the API: Team roles, adding members with roles, reading and changing a member's permissions, and "my teams" are available in the public API and the MCP server
• API Keys as Service Accounts: API keys can act as a service account, so integrations run with exactly the permissions that service account has

Benefits:

• Automate team management end to end
• Integrations with precisely scoped, auditable access