> ## Content Index > Fetch the complete content index at: https://www.stirup.si/llms.txt > Use this file to discover other available public pages before exploring further. # Warm Agents Plugin for TeamCity: Configuration and Management - URL: https://www.stirup.si/warm-agents-plugin-for-teamcity-configuration-and-management-a3e9cbdc/ - Published: 2026-10-13T14:08:08.000Z - Updated: 2026-10-13T14:08:08.000Z - Description: The Warm Agents plugin for TeamCity allows maintaining a specified number of idle, pre-started agents via REST API, with dynamic adjustments based on target settings and project needs. - Author: Satish Das - Tags: Development, News, Stirup Research ## Plugin Functionality and Configuration The Warm Agents plugin for TeamCity enables the maintenance of a specified number of idle, pre-started agents for a given cloud image. Once the plugin is operational, configuration is done via REST API calls. To set up ten idle agents for a cloud image, execute the command: `teamcity api '/app////warmAgents?target=10' -X PUT`. To stop maintaining warm agents for an image, set the target to 0\. If a cloud image has a hard limit on the total number of running agents, TeamCity respects that limit, even if the target is set to a higher value. To verify the configuration, use the API call `teamcity api '/app//warmAgents?includeSubprojects='` or check the Project Settings | Integrations | Warm Agents section. TeamCity dynamically adjusts the number of agents based on the target, launching more or fewer instances as needed. Changing the target does not affect agents that are already running, as TeamCity does not forcibly stop instances when scaling down. ## Implementation and Setup Details To implement and set up the Warm Agents plugin for TeamCity, navigate to Admin | Plugins, click Browse plugins repository, and locate Warm Agents in the JetBrains Marketplace listing ([JetBrains](https://blog.jetbrains.com/teamcity/2026/10/teamcity-warm-agents-plugin/?ref=stirup.si)). Once installed, users can identify necessary project and profile IDs using the teamcity-cli or REST API commands such as `teamcity project list` and `teamcity project cloud profile list --project ` ([JetBrains](https://blog.jetbrains.com/teamcity/2026/10/teamcity-warm-agents-plugin/?ref=stirup.si)). Alternatively, these IDs can be manually extracted from the cloud profile page URL on the TeamCity server. To configure scaling behavior, a trigger can be scheduled to adjust the number of warm agents, for example, setting `param("warmAgents.target", "2")` to scale up to two agents each morning ([JetBrains](https://blog.jetbrains.com/teamcity/2026/10/teamcity-warm-agents-plugin/?ref=stirup.si)). The plugin also provides utilization and saturation metrics for each configured cloud image, offering insights into agent performance and queue management ([JetBrains](https://blog.jetbrains.com/teamcity/2026/10/teamcity-warm-agents-plugin/?ref=stirup.si)). ## Resource Management and Automation The Warm Agents plugin for TeamCity introduces a targeted approach to resource management and automation. Designed to avoid unnecessary resource consumption, the plugin scales agents based on changing project needs. According to the plugin's documentation, keeping agents warm overnight can lead to wasted resources, which is why the feature is optimized for scenarios with frequent target changes. TeamCity dynamically adjusts by launching more or fewer agents as needed, ensuring that changes in workload do not disrupt existing agent instances. When scaling down, TeamCity does not forcibly stop running agents, preserving stability. Automation is further enhanced through scheduling triggers, such as setting the warm agent target to 2 each morning and resetting it to 0 in the evening. These triggers allow for precise control over agent allocation without manual intervention. ## Sources and reporting notes - [JetBrains](https://blog.jetbrains.com/teamcity/2026/10/teamcity-warm-agents-plugin/?ref=stirup.si) Based on published source material. No independent hands-on testing is claimed.