Skip to content
Back to search

teamcity-cli

TeamCity from your terminal – or your AI's. Builds, logs, agents, agent terminals, queues.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/jetbrains/teamcity-cli with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/jetbrains/teamcity-cli'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/jetbrains-teamcity-cli/badge.svg)](/listings/jetbrains-teamcity-cli)

HTML

<a href="/listings/jetbrains-teamcity-cli"><img src="/api/listings/jetbrains-teamcity-cli/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

**macOS (Homebrew):**

brew install jetbrains/utils/teamcity

**Linux:**

curl -fsSL https://jb.gg/tc/install | bash

The install script also works on macOS. New installs use `~/.local/bin` without sudo; rerunning it updates an existing unmanaged installation in place. Missing Bash/Zsh PATH entries are added automatically. Restart your shell afterward, or use the printed PATH command.

**Windows (Winget):**

winget install JetBrains.TeamCityCLI

**npm:**

npm install -g @jetbrains/teamcity-cli

<details> <summary>More installation methods (deb, rpm, Chocolatey, Scoop, build from source)</summary>

**Debian/Ubuntu:**

curl -fsSLO https://github.com/JetBrains/teamcity-cli/releases/latest/download/teamcity_linux_amd64.deb
sudo dpkg -i teamcity_linux_amd64.deb

**RHEL/Fedora:**

sudo rpm -i https://github.com/JetBrains/teamcity-cli/releases/latest/download/teamcity_linux_amd64.rpm

**Arch Linux (AUR):**

yay -S teamcity-bin

**PowerShell:**

irm https://jb.gg/tc/install.ps1 | iex

**CMD:**

curl -fsSL https://jb.gg/tc/install.cmd -o install.cmd && install.cmd && del install.cmd

**Chocolatey:**

choco install teamcitycli

**Scoop:**

scoop bucket add jetbrains https://github.com/JetBrains/scoop-utils
scoop install teamcity

**Build from source:**

go install github.com/JetBrains/teamcity-cli/tc@latest

See the [getting started guide](https://www.jetbrains.com/help/teamcity/teamcity-cli-get-started.html) for the full walkthrough.

</details>

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 185 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # TeamCity CLI
  2. [![](https://camo.githubusercontent.com/078d7efd31e09afaa403fc886eac57d43ece79ad24fb75be8e05ac2b13175bef/68747470733a2f2f6a622e67672f6261646765732f6f6666696369616c2d706c61737469632e737667)](https://github.com/JetBrains)
  3. [![GitHub Release](https://img.shields.io/github/v/release/JetBrains/teamcity-cli?style=plastic)](https://github.com/JetBrains/teamcity-cli/releases/latest)
  4. `teamcity` is the official command-line client for [TeamCity](https://www.jetbrains.com/teamcity/). Use it to start builds, tail logs, and check the queue, as well as for less frequent tasks such as opening a shell on a build agent, editing job settings, or calling the REST API directly.
  5. ![cli](./docs/images/showcase_dark.gif#gh-dark-mode-only)
  6. ![cli](./docs/images/showcase.gif#gh-light-mode-only)
  7. Full documentation, including installation, authentication, and a command reference, is at [jb.gg/tc/docs](https://jb.gg/tc/docs).
  8. ## Install
  9. **macOS (Homebrew):**
  10. ```bash
  11. brew install jetbrains/utils/teamcity
  12. ```
  13. **Linux:**
  14. ```bash
  15. curl -fsSL https://jb.gg/tc/install | bash
  16. ```
  17. The install script also works on macOS. New installs use `~/.local/bin` without sudo; rerunning it updates an existing unmanaged installation in place. Missing Bash/Zsh PATH entries are added automatically. Restart your shell afterward, or use the printed PATH command.
  18. **Windows (Winget):**
  19. ```powershell
  20. winget install JetBrains.TeamCityCLI
  21. ```
  22. <details>
  23. <summary>More installation methods (deb, rpm, Chocolatey, Scoop, build from source)</summary>
  24. **Debian/Ubuntu:**
  25. ```bash
  26. curl -fsSLO https://github.com/JetBrains/teamcity-cli/releases/latest/download/teamcity_linux_amd64.deb
  27. sudo dpkg -i teamcity_linux_amd64.deb
  28. ```
  29. **RHEL/Fedora:**
  30. ```bash
  31. sudo rpm -i https://github.com/JetBrains/teamcity-cli/releases/latest/download/teamcity_linux_amd64.rpm
  32. ```
  33. **Arch Linux (AUR):**
  34. ```bash
  35. yay -S teamcity-bin
  36. ```
  37. **PowerShell:**
  38. ```powershell
  39. irm https://jb.gg/tc/install.ps1 | iex
  40. ```
  41. **CMD:**
  42. ```cmd
  43. curl -fsSL https://jb.gg/tc/install.cmd -o install.cmd && install.cmd && del install.cmd
  44. ```
  45. **Chocolatey:**
  46. ```powershell
  47. choco install teamcitycli
  48. ```
  49. **Scoop:**
  50. ```powershell
  51. scoop bucket add jetbrains https://github.com/JetBrains/scoop-utils
  52. scoop install teamcity
  53. ```
  54. **Build from source:**
  55. ```bash
  56. go install github.com/JetBrains/teamcity-cli/tc@latest
  57. ```
  58. See the [getting started guide](https://www.jetbrains.com/help/teamcity/teamcity-cli-get-started.html) for the full walkthrough.
  59. </details>
  60. ## Usage
  61. Log in once and the CLI remembers the server:
  62. ```bash
  63. teamcity auth login
  64. ```
  65. Scripts and desktop apps can sign in through the browser without a terminal: `teamcity auth login --server <url> --web --json` never prompts and prints the authorization URL as a JSON line.
  66. Then:
  67. ```bash
  68. # my latest build on this branch
  69. teamcity run list --user @me --branch @this --limit 1
  70. # start a build and stay attached to it
  71. teamcity run start MyProject_Build --branch main --watch
  72. # pin different revisions in a job with multiple VCS roots
  73. teamcity run start MyProject_Build --revision AppRepo=abc123 --revision AssetsRepo=@main
  74. # logs from the latest build of a job
  75. teamcity run log --job MyProject_Build
  76. # what's sitting in the queue
  77. teamcity queue list
  78. # shell into a build agent
  79. teamcity agent term Agent-Linux-01
  80. ```
  81. TeamCity says *build* and *build configuration*; the CLI says `run` and `job`. The [glossary](https://www.jetbrains.com/help/teamcity/teamcity-cli-glossary.html) has the full mapping.
  82. Set `TEAMCITY_RO=1` to block writes and remote shells (`agent exec` and `agent term`). Use server-side permissions for a security boundary. Redirects never downgrade HTTPS or forward request headers to another origin, and cross-origin artifact downloads are made without credentials.
  83. Every command takes `--json` or `--plain` for [scripting](https://www.jetbrains.com/help/teamcity/teamcity-cli-scripting.html), and `--web` opens the matching page in the TeamCity UI. When no command covers what you need, `teamcity api` calls the REST API directly with your stored credentials. You can also log in to several servers and switch between them; see [configuration](https://www.jetbrains.com/help/teamcity/teamcity-cli-configuration.html).
  84. For a queued run, `teamcity run view <id>` reports agent and cloud-image compatibility, including unmet requirements, when the server supports it. Large pools are summarized; use `--json` and read `.compatibility` for every entry.
  85. `teamcity run download` writes only inside `--output`, and a failed or incomplete transfer leaves existing files untouched.
  86. ## Commands
  87. | Group | Commands |
  88. |--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
  89. | **auth** | `login`, `logout`, `status` |
  90. | **run** | `list`, `start`, `view`, `watch`, `log`, `tree`, `changes`, `tests`, `diff`, `cancel`, `download`, `artifacts`, `restart`, `pin`/`unpin`, `tag`/`untag`, `comment` |
  91. | **job** | `list`, `view`, `create`, `tree`, `pause`/`resume`, `step list`/`view`/`add`/`delete`, `param list`/`get`/`set`/`delete`, `settings list`/`get`/`set` |
  92. | **project** | `list`, `view`, `create`, `tree`, `vcs list`/`view`/`create`/`test`/`delete`, `ssh list`/`generate`/`upload`/`delete`, `cloud profile`/`image`/`instance`, `connection list`/`view`/`create github-app`/`create docker`/`authorize`/`delete`, `param`, `token get`/`put`, `settings export`/`status`/`validate` |
  93. | **pipeline** | `list`, `view`, `create`, `validate`, `pull`, `push`, `schema` (enabled runners/features), `delete` |
  94. | **queue** | `list`, `approve`, `remove`, `top` |
  95. | **agent** | `list`, `view`, `term`, `exec`, `jobs`, `authorize`/`deauthorize`, `enable`/`disable`, `move`, `reboot` |
  96. | **pool** | `list`, `view`, `link`/`unlink` |
  97. | **server** | `plugin upload` (optionally with `--hot-reload`) |
  98. | **api** | Raw REST API access |
  99. | **link** | Bind this repository to a TeamCity project via `teamcity.toml` |
  100. | **config** | `list`, `get`, `set` |
  101. | **alias** | `set`, `list`, `delete` |
  102. | **skill** | `list`, `install`, `remove`, `update`, `guide` |
  103. | **update** | Check for and install CLI updates (`--check`/`--json` for status only, `--yes` for non-interactive installation) |
  104. Run `teamcity <command> --help` for usage, or see the [command reference](https://www.jetbrains.com/help/teamcity/teamcity-cli-commands.html).
  105. ## For AI agents
  106. The CLI ships with an [Agent Skill](https://agentskills.io) that teaches coding agents (Claude Code, Cursor, and others) how to drive `teamcity`:
  107. ```bash
  108. teamcity skill install # auto-detects installed agents
  109. teamcity skill install --project # install to current project only
  110. teamcity skill update # update to the version bundled with teamcity
  111. teamcity skill remove # uninstall
  112. teamcity skill guide # print the guide that installed skills point to
  113. ```
  114. Installed skills are short stubs that tell the agent to run `teamcity skill guide`, so after a CLI upgrade agents read the instructions for the new version without reinstalling.
  115. After a green onboarding pipeline, the agent can offer to migrate remaining
  116. GitHub Actions jobs. Hook instructions load through `teamcity skill guide`
  117. after explicit consent; installation is optional.
  118. For **Claude Code**, you can install the `teamcity` plugin instead, which
  119. bundles these skills from
  120. [JetBrains/teamcity-skills](https://github.com/JetBrains/teamcity-skills):
  121. ```bash
  122. /plugin marketplace add JetBrains/teamcity-skills
  123. /plugin install teamcity@teamcity
  124. ```
  125. The plugin contains only the skills, so install the `teamcity` CLI itself as described above.
  126. See [AI agent integration](https://www.jetbrains.com/help/teamcity/teamcity-cli-ai-agent-integration.html) for details.
  127. ## Learn more
  128. - [Getting started](https://www.jetbrains.com/help/teamcity/teamcity-cli-get-started.html): install, authenticate, and run your first commands
  129. - [Configuration](https://www.jetbrains.com/help/teamcity/teamcity-cli-configuration.html): config file, environment variables, multi-server setup, shell completion
  130. - [Scripting and automation](https://www.jetbrains.com/help/teamcity/teamcity-cli-scripting.html): JSON output, plain text mode, CI/CD integration
  131. - [Aliases](https://www.jetbrains.com/help/teamcity/teamcity-cli-aliases.html): create custom command shortcuts
  132. ## Contributing
  133. TeamCity CLI is open source under the Apache-2.0 license. Bug reports and pull requests are welcome. [CONTRIBUTING.md](CONTRIBUTING.md) explains how to build and test the project.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.