TeamCity Roadmap

See what's in the pipeline

Release cycle

TeamCity has three major product releases per year. We also have several bug fixes after each major release.

TeamCity Cloud follows a different release pattern, with releases happening every few weeks.

2026.1

April 2026

2026.2

August 2026

2026.3

November 2026

TeamCity vision

As software shifts to collaboration between humans and AI agents, TeamCity still ensures reliable building, testing, and delivery – now at a new scale and supporting the new workflows AI brings.

Yarik Aleksandrov, July 8, 2026

What's Next for TeamCity – CI/CD by JetBrains

A look at where TeamCity is today, where we believe CI/CD is heading, and what we are building next.

Our focus for 2026

Agentic interfaces and scenarios

2026.12026.22026.3

Enjoy an end-to-end experience of working with TeamCity via AI agents, including:

CLI, MCP, and agent skills compatibility.
Configuration, migration, observability, build running, failure analysis, and fix options.

Viktor Tiulpin, March 19, 2026

$ teamcity From the Command Line

Start builds, tail logs, and manage agents and queues – without switching windows.

Improving DevEx

2026.22026.3

Work with TeamCity without leaving your environment:

From the TeamCity plugin for JetBrains IDEs (through the UI, AI chat, and AI agents).
From the terminal (through the CLI and AI agents).
From AIR – the agentic development environment by JetBrains (through AI agents).

Agentic automations

2026.3

Run AI agents as TeamCity build steps with built-in recipes for common scenarios.

AI governance

BYOK in TeamCity

2026.2

Support for the use of local LLMs or approved AI providers in TeamCity’s in-product AI features and AI workflows launched from TeamCity.

Integration with JetBrains Central

2026.3

A new JetBrains product that provides AI governance capabilities to help with AI adoption: token quotas, analytics on token usage problems, and policies for LLM usage.

TeamCity Pipelines GA

2026.2

Modern pipeline configuration for teams of any size, with fully branchable configuration as code (YAML and the Kotlin DSL), a visual drag-and-drop editor, and UI configuration.

Initial EAP release in 2025.7, followed by improvements in 2025.11 and 2026.1.

Compatibility

Existing build configurations and build chains continue to evolve. Pipelines can be integrated into build chains, and the Kotlin DSL is supported in both pipelines and build configurations.

Performance monitor for jobs

2026.2

Real-time pipeline debugging

2026.2

Full support for protected branches

2026.2

Coverage of all use cases supported by current build configurations

2026.3

Full support for TeamCity’s runners and build features

2026.3

Core CI/CD capabilities

2026

Performance and scalability improvements

The introduction of a minimum number of running cloud agents. TW-41207

The ability to retry failed builds within a build chain without restarting the entire chain. TW-96371
Architectural changes to enable native horizontal scalability.
Continuous usability and performance improvements related to Sakura UI.

Flexibility

Dynamic build chains (EAP in 2026.2; GA in 2026.3). TW-44489

Expanded support for developer tools and integrations

Maven 4 support. TW-96812
Support for SARIF static analysis reports. TW-86642
Perforce support improvements.
GitHub integration improvements.
Expanded cloud integrations (reworked Azure integration; improved AWS integration).

Looking ahead

On our implementation to-do list are proactive CI/CD, AI workflow orchestration, merge trains, enhanced CD capabilities, stronger game development support, deeper integration with the JetBrains ecosystem, and much more.