Tools
The development tools a host gets, how to switch categories off, and how versions are chosen.
The base is Ubuntu 26.04. Coding agents come from plugins, which can install their own tools too.
Inventory
| Area | Included |
|---|---|
| JavaScript | Node 24 by default, Node 22 available; npm, Bun/bunx, Deno, pnpm |
| Python | Ubuntu Python, pip, venv, pipx, uv, artifact libraries and Playwright |
| Native | GCC and G++, Clang, CMake and Ninja, pkg-config, Go, Rust with Cargo and rustup |
| JVM | OpenJDK 21, Maven, Gradle, Kotlin, Scala, sbt |
| Other languages | Ruby with Bundler, PHP with Composer, Erlang and Elixir, .NET 10 SDK, R |
| Containers | Docker and Compose on full hosts, with the agent in the docker group |
| Browsers, media, desktop | Chrome, Firefox and Playwright Chromium; FFmpeg; xdotool and wmctrl; XFCE with office and artifact tools |
| General CLI | Git with LFS and gh; ripgrep and jq; curl, SSH and tmux; archive, search and debugging tools |
The resolved runtime inventory of a host is /var/lib/rookery/toolchains.json.
Tool categories
Each category is a switch on the Features tab. All are on by default.
| Category | Ansible setting | Container build |
|---|---|---|
| JavaScript runtimes | rookery_tools_web | INSTALL_WEB_TOOLS |
| Native development | rookery_tools_native | INSTALL_NATIVE_TOOLS |
| JVM development | rookery_tools_jvm | INSTALL_JVM_TOOLS |
| .NET development | rookery_tools_dotnet | INSTALL_DOTNET_TOOLS |
| Scripting languages | rookery_tools_scripting | INSTALL_SCRIPTING_TOOLS |
| Scientific computing | rookery_tools_scientific | INSTALL_SCIENTIFIC_TOOLS |
| Google Chrome | rookery_tools_chrome | INSTALL_CHROME_TOOLS |
rookery_install_dev_tools (INSTALL_DEV_TOOLS for the container) sets the default of all of them at once. A category set on its own takes precedence. Playwright (rookery_install_playwright) and software graphics have their own switches.
Node and npm, Python, GCC, CMake and Ninja stay as base dependencies. The package lists, runtimes and expected smoke-test commands of each category are defined together in rookery_tool_categories. Switching a category off skips its packages and runtimes on a fresh install. Packages already installed stay when a profile is applied again. Anything beyond the categories, such as the Unity CLI, is a plugin.
Runtimes with mise
mise selects between runtime versions. Nvm is not installed. mise is checksum-pinned and its configuration belongs to the agent at ~/.config/mise/config.toml. Its shims are on the PATH of shells, the desktop and the T3 service, and project-local mise configurations override the global selection after mise's usual trust step.
mise ls
mise exec node@22 -- node --version
box exec node --version
box exec gh --versionVersions
| Tool | Version | Source |
|---|---|---|
| Playwright | 1.65.0 | With its matching Chromium |
| ansible-core | 2.21.6 | On your machine. Supports Ubuntu's Python 3.14 on hosts |
A plugin chooses the versions of what it installs, and its guide says which settings change them. Update brings them to their latest versions, and those settings are the least versions, so applying again does not go back.
Node 22 and .NET 10 use release selectors, so a clean install may get newer patches. Pin full versions in rookery_node_versions and rookery_mise_tools for closer reproduction. Ubuntu packages, npm's transitive dependencies and Python version ranges also move. The role describes how to set a host up and does not freeze its packages. Defaults for all of this are in defaults/main.yml.
Prompts an agent would not see
Some programs stop at a dialog on the desktop the first time they run, and an agent working over SSH never notices. The role removes the common ones:
| Program | What the role does |
|---|---|
| Keyring | Gives the agent a default keyring without a password, so programs using the Secret Service store credentials without asking. Those secrets are unencrypted in ~/.local/share/keyrings. An existing keyring is left as it is |
| Chrome | Skips the terms-of-service dialog, the default-browser question and the welcome page, and turns usage statistics off |
Signing in to an agent, to Unity or to a browser profile still needs a person.
References
Last updated on