Skip to content

v0.6.2

Latest
Latest

Choose a tag to compare

View all tags
@tomkis tomkis released this 10 Mar 12:57
· 272 commits to main since this release
v0.6.2
6dcd1e2

Agent Stack version 0.6.2

This release introduces an experimental TypeScript SDK server, a redesigned trajectory visualization in the UI, new interactive agent capabilities, Windows CLI support, and several Helm chart improvements for production deployments.

Major Changes

Experimental TypeScript SDK Server

A new experimental server component has been added to the TypeScript SDK, enabling developers to define and host agents directly. It includes agent auto-registration with the platform (with retry logic), an AgentExecutorImpl for managing execution, and a flexible extension system for integrating LLMs and UI configurations. A hello-world example is included to get started quickly. (#1842)

Reworked Trajectory Visualization

The trajectory UI has been completely redesigned with character-by-character text animations, a dynamic header that shows the latest trajectory step when the list is collapsed, and improved content handling during agent streaming. The result is a smoother, more informative experience when watching agents work. (#2051)

Text Input Required

Agents can now request free-form text input from users during a run via a new TextInputRequired event type. The UI renders a dedicated MessageTextInput component with auto-focus, enabling better integration with plain A2A agents. (#2079)

Client Side Agent builds on Windows

The agentstack import command now works on Windows through the WSL driver. Image import logic has been refactored into a shared base driver with platform-specific path handling for both Lima (macOS/Linux) and WSL (Windows). (#2088)

CLI: Improved agentstack update UX

Agent updates now feature better GitHub origin recognition (including git+ prefixes), interactive tag selection, and standardized origin handling. (#1990)

Helm: Separate Internal/Public OIDC Issuer URLs

The Helm chart now supports configuring separate internal and public issuer URLs for Keycloak. This allows the backend to communicate with Keycloak over an internal HTTP channel while exposing a public HTTPS URL to clients. (#2059)

Helm: Optional Keycloak Init Container

The Keycloak database schema initialization container can now be disabled via keycloak.persistence.initSchemaContainer.enabled. This is useful when database schema management is handled externally. The schema creation command has also been simplified. (#2050, #2057)

What's changed

Assets 2
Loading