26.2 26.1
26.2 26.1

Release Notes

You can also view the change log of the Agent Hub from your development framework. It is part of the PAS Code project template, and shows the change log up to the version you have installed.

Agent Hub 26.2

What’s New

Agent Gateway

  • A new Agent Gateway section in the Control Hub. It has two pages:

    • Providers: add, change, and remove the LLM providers of a platform. You can test a provider API Key before you save it and see the models a provider offers.

    • Virtual Keys: create and manage virtual API Keys. Allow all models or only specific ones, and see which agents use a key before you change it.

  • Model access per agent. A new agent detail page shows which virtual API Key and model an agent uses, and lets you change them.

Control Hub

  • The sidebar groups the views under headings and links directly to the platform tools, for example Git and the CI/CD dashboard.

  • Branches, tags, and commits link directly to the Git server.

  • Every view has its own address that you can bookmark or share. The Control Hub also remembers the project you last selected.

PAS Code

  • New skills: add authentication to an app or a service, and connect an agent to the platform MCP server.

  • New PAS CLI commands show the addresses of the platform MCP server, the Agent Gateway, and the identity provider.

  • Agents: they now support conversational memory and skills, and you can configure how many steps an agent run may take.

  • Swagger UI: you can now sign in directly, without copying an access token by hand.

Platform MCP Server

  • A new platform MCP server: It gives AI agents access to your deployments, logs, and the Agent Hub glossary. The Platform Assistant now uses it, and so can your AI coding assistant.

  • Easy setup: The PAS CLI prints the server configuration of the active platform, and a new skill connects your coding assistant to the server.

  • Secure access: Every request needs a role, and secret values are hidden in the answers.

Important Fixes

  • A stopped deployment now shows as stopped, and the Control Hub offers the right actions for it.

  • Agent metrics are no longer lost when the Agent Gateway restarts.

  • On Windows, the PAS CLI now keeps reacting to the keyboard when you start a project.

  • Upgrading the Agent Hub no longer times out, and an installation no longer fails because a skill folder is missing.

Change Log

26.2.0 (06.11.2026)

Change Log (show | hide)

Platform & API

  • Create pas mcp server

  • Deploy the platform mcp server

  • Remove mcp from agent

  • Point the agent at the platform mcp server

  • Tell the agent the current time in utc

  • Link branches, tags and commits to the git server

  • Publish the contract of the gateway management

  • Give each llm provider type its own schema

  • Require a provider api key of at least 8 characters

  • Add an llm provider to the agent gateway of a platform

  • Read the llm providers of the platforms

  • Remove an llm provider of a platform

  • Change an llm provider of a platform

  • Manage the virtual api keys of a platform

  • Derive the names of the gateway resources

  • Require a role to ask the agent

  • Require a role on every request to /mcp

  • List the models of an llm provider for an api key

  • List the models of a saved llm provider

  • Write the agent resource of an agent feature

  • Relabel the secret of a virtual api key on a change

  • Read and change the model and virtual api key of an agent

  • Let a virtual api key permit all models

  • Answer the agents of a virtual api key

  • Address every view by its list, identity and page

  • Add the agent gateway section

  • Manage the llm providers of the agent gateway

  • Open an agent detail view from the list of agents

  • Manage the virtual api keys of the agent gateway

  • Publish the address of the llm providers

  • Group the menu and link the platform tools in it

  • Assign a virtual api key and a model to an agent

  • Read llm providers and create virtual api keys

  • Keep query parameters of a change still in progress

  • Restore the selected project when returning to projects

  • Answer the list of models of a virtual api key

  • Answer the calls about one model of a virtual key

  • Answer calls on paths the gateway does not support

  • List events and redact secrets in configuration answers

  • Redact every value under a sensitive name

  • Redact only the configuration values of an answer

  • Date a recurring event by the last time it was seen

  • Report a stopped deployment as stopped

  • Do not conclude a stop from the failure it stops

  • State an unresolved secret reference by its path

  • List the components of a deployment by spec.platform

  • Publish the hub clients from the hub bundle

  • Keep the agent metrics when the gateway pod is replaced

  • Count the agent metrics across a gateway container restart

  • Read the agent metrics from the downsampled samples too

  • Refuse the auto resolution for the agent metrics

  • Read the agent list again on every visit of the overview

  • Read the platform mcp address as a configurable

  • Say that a turn builds a failed agent again

  • State which token lists the mcp tools

  • Store the features of a component by a handler per type

  • Let the deployment state the path prefix of the mcp address

  • Ask the authorized platforms about agent model scopes

  • Name error contexts and the keys of a filter set

  • Describe the providers page and its sub pages

  • Move what the list reads of an agent into shared classes

  • Describe the agent page and what the agent list shows

  • Drop the calls column from the agents overview

  • Share the tables, forms and messages of gateway pages

  • Describe the virtual keys page and its sub pages

  • Show one model of a provider as "1 model"

  • Group the sidebar navigation under headings

  • Describe the groups of the menu and its platform tools

  • Let an agent carry its model access

  • Describe the model access of an agent

  • Store features through registered feature modules

Libraries

  • Sign in to the openid provider from the swagger ui

  • Provide conversational memory and skills

  • Read and change an agent of a platform

  • Read and change an agent

  • Add the agents of a virtual api key

  • Keep the contract of an answer for the service

  • Check each answer against its contract

  • Move the agent feature kind into its own package

  • Move the agent feature manifest into its own package

  • Make the step limit of an agent run configurable

  • Redact a virtual key of the agent gateway by default

Developer Tools

  • Mark a change breaking only against the last release

  • Structure a contract type with variants per variant

  • Add authentication to an app or service through skills

  • Print the MCP server configuration of the active platform

  • Add a skill that connects an agent to the platform mcp server

  • Add info commands for the platform mcp, gateway and iam

  • List translation catalogues in specs instead of quoting texts

  • Keep a deprecated name declared in its own file

  • Skip local skill sources whose folder does not exist

  • Turn off the nx terminal ui when starting on windows

  • State the generated agent model in the local service config

  • Judge review compatibility against the last release

  • State the agent model in the local config in pas-generate-agent

Other

  • Check the transport in the controller, not the service

  • Sign in from the swagger ui of the platform services

  • Notify the documentation team about user interface changes in jira tickets

  • File jira tickets with the shared pas-create-jira-ticket skill

  • Write the release notes of every release from the commit messages (optionally AI backed)

  • New skill to update the official documentation from the repo

  • Define the commit scopes of the repository

  • Add the feature record with the key of its configuration

  • Make an agent a feature record with its configuration key

  • Answer the configuration key of an agent

  • Give every new package one dummy test

  • Build the charts in pipelines started by the release job

  • Tell a configuration change by the states that describe it

  • State the welcome agent model in the local config

  • Add the default model alias of the agent gateway

  • Call the default model of the provider for its alias

  • Call the provider default model when an agent sets no model

  • State the model of an agent in its local configuration

  • Share the resource services of the custom resources

  • Implement a ui library building block once

  • Record the rules for answer contracts and commits

  • Add integration branches and release candidates to the branching model

  • Prefix the kubernetes and loki skills with pas-

26.2.0-alpha.1 (02.11.2026)

Change Log (show | hide)

Platform & API

  • Group the menu and link the platform tools in it

  • Assign a virtual api key and a model to an agent

  • Keep the agent metrics when the gateway pod is replaced

  • Count the agent metrics across a gateway container restart

  • Read the agent metrics from the downsampled samples too

  • Refuse the auto resolution for the agent metrics

  • Group the sidebar navigation under headings

  • Describe the groups of the menu and its platform tools

  • Let an agent carry its model access

  • Describe the model access of an agent

  • Store features through registered feature modules

Libraries

  • Move the agent feature kind into its own package

  • Move the agent feature manifest into its own package

Developer Tools

  • List translation catalogues in specs instead of quoting texts

  • Keep a deprecated name declared in its own file

  • State the generated agent model in the local service config

  • State the agent model in the local config in pas-generate-agent

Other

  • State the welcome agent model in the local config

26.2.0-alpha.0 (30.10.2026)

Change Log (show | hide)

✨ Highlights

  • The Control Hub has a new Agent Gateway section. An administrator can add, change, and remove LLM providers, and test a provider API key before saving it. The administrator can also manage virtual API keys and see which agents lose access.

  • A new platform MCP server gives an agent access to the platform. The platform agent now uses it. The CLI prints the MCP server configuration of the active platform. A CLI skill connects an agent to the server. The server needs a role for each request.

  • The Control Hub has an agent detail view. A user opens it from the list of agents. The agent gateway can read and change the model and the virtual API key of an agent.

  • A user can sign in from the Swagger UI of the platform services. The user does not copy an access token by hand.

  • A service now checks each answer against its contract before it sends the answer.

Platform & API

  • The Agent Gateway bundle publishes the address of the LLM providers.

  • The Keycloak user service, the agent gateway, and the admin service no longer send answers that break the contract.

  • The Control Hub has a Virtual Keys page to manage the virtual API keys of the Agent Gateway.

  • The Control Hub shows one model as "1 model" and shares tables, forms, and messages between gateway pages.

  • The Control Hub has an agent detail view that opens from the list of agents.

  • The agents overview of the Control Hub no longer has the calls column.

  • The hub bundle publishes the hub clients, so an upgrade of the hub chart does not time out.

  • The Control Hub has a Providers page to manage the LLM providers of the Agent Gateway.

  • The Control Hub names error contexts and keeps the state of a list view under the scope of that list.

  • The admin service lists the components of a deployment by spec.platform.

  • The admin service states an unresolved secret reference by its path.

  • A stopped component with a configuration error shows as stopped, and the Control Hub offers the correct actions.

  • The Control Hub has an Agent Gateway section.

  • The Control Hub addresses every view by its list, identity, and page.

  • The agent gateway deployment can state the path prefix of the MCP address.

  • The agent gateway answers with the agents that use a virtual API key.

  • A virtual API key can permit all models.

  • The platform MCP server redacts secret values in the answers of the deployment and registry tools.

  • The platform MCP server dates a recurring event by the last time that it was seen.

  • The agent gateway reads and changes the model and the virtual API key of an agent.

  • The deployment services of the admin service raise domain errors, not HTTP errors.

  • The admin service stores the features of a component with one handler for each type.

  • The agent gateway lists the models of an LLM provider, for a saved provider or for a provider API key.

  • The agent gateway answers a call on a path that it does not support.

  • The agent gateway answers the list of models and the calls about one model of a virtual API key.

  • The platform MCP server and the platform agent now require a role for each request.

  • The agent gateway manages the virtual API keys of a platform.

  • The agent gateway derives the names of its resources, so the names do not clash.

  • The agent gateway checks the model of a call over the whole body of the call.

  • The agent gateway can add, read, change, and remove the LLM providers of a platform.

  • A provider API key must have at least 8 characters.

  • Each LLM provider type has its own schema for settings.

  • The contract of the gateway management is published.

  • The Control Hub links branches, tags, and commits to the Git server.

  • The Control Hub shows the endpoint hints on the light surface.

  • The Control Hub keeps the selected project and the query parameters of a change that is in progress.

  • The documentation says which token lists the MCP tools and that a turn builds a failed agent again.

  • The platform agent reads the platform MCP address as a configurable.

  • The platform agent gets the current time in UTC.

  • The platform agent uses the platform MCP server and has no MCP of its own.

  • A new platform MCP server is created and deployed.

Libraries

  • A service now checks each answer against its contract.

  • The agent feature service types add the agents of a virtual API key.

  • The agent feature service types and client read and change the model and virtual API key of an agent.

  • The agent module now provides conversational memory and skills.

  • The step limit of an agent run is configurable with recursionLimit.

  • The redactor now hides a virtual key of the Agent Gateway by default.

  • The Swagger UI signs in to the OpenID provider as a public client.

  • A 400 answer no longer contains the value that failed the check.

  • A failed union check now reports the issues of the closest variant.

  • The JSON log format keeps every value and the error that a service logs.

  • The service logger redacts the messages of the string format and translates the messages.

  • An agent now recovers from a failed build and a failed tool call.

Developer Tools

  • The CLI shows the gateway and identity provider addresses of the active platform.

  • The CLI prints the MCP server configuration of the active platform.

  • A new CLI skill connects an agent to the platform MCP server.

  • A new CLI skill adds authentication to an app or a service.

  • The CLI turns off the Nx terminal UI on Windows, because the UI stops reacting to the keyboard.

  • The development guidelines describe how to structure a contract type with variants.

  • The development guidelines mark a change as breaking only against the last release.

  • The install no longer fails when the folder of a local skill source does not exist.

Other

  • A provider route now answers on its own host only.

  • The API description of a post endpoint now states the correct status 201.

  • The agent rules now record how a service handles answer contracts and commits.

  • The release process writes the release notes from the commit messages.

  • The platform tells a configuration change by the revision of the configuration.

  • The code rules say to implement a UI library building block once.

  • The Jira skills use the shared skill and tell the documentation team about user interface changes.

  • A user can sign in from the Swagger UI of the platform services.

  • The admin service and the agent gateway now share the resource services of the custom resources.

  • The code rules say that the controller checks the transport, not the service.

  • The release job now builds the charts in the pipelines that it starts.

  • A review of the platform MCP extraction closed gaps between the server, the agent, and the charts.

Agent Hub 26.1

Initial release.