start using Java with your agents
sign up, open a room, and install Java from its technologies tab.
java ai agent: a jdk on the room server so agents can build and test
install eclipse temurin on a room's server and its agents compile with javac, run with java, and drive the project's own maven or gradle wrapper.
- runs on
- room server
- installed
- per room
- category
- runtime
java on a room means a real jdk on a real machine. once it reports installed, java and javac are on the room server's path and every agent in the room reaches them through the bash tool.
what agents do with it
for most projects the agent does not call javac directly. it runs the project's own build through ./mvnw or ./gradlew, which is what keeps a run reproducible. the compiler and the test suite then do the reviewing: a wrong generic, a missing override, a broken dependency scope all surface as real errors with line numbers, on the same machine that holds the checkout.
the matching skill
java ships with a skill of the same name. it carries three things: compile with javac and run with java, prefer the wrapper when one is present, and check the active version before assuming compatibility. skills load only for the agents you assign them to.
example tasks
- 01
the build fails on the ci image but not on my machine. work out why.
the agent runs the wrapper on the room's clean server, reads the real failure, and reports the dependency or jdk difference rather than a theory about it.
bashreadgrep - 02
add the endpoint and run the test suite.
it writes the code, builds through the project's wrapper on the room machine, fixes what the compiler names, and reports the suite result.
writebashedit
what to know before installing
the room needs a paid server tier, and a jvm build is a good reason to pick 8 gb over 4. the install brings the temurin lts jdk and exits early if java is already present. kafka depends on this technology, so install java before it if a room needs both.
how to install Java
Java is installed per room from the technologies tab, not once per team and not on your laptop.
- give the room a server
technologies are installed on real hardware, so the room needs a 4 GB or 8 GB tier. a room created without a server has nowhere to put them, and the install is refused rather than queued.
- open the technologies tab
room settings lists every installable technology with its status. pick Java and the install is queued for that room's server alone.
- watch the install run
the room streams the status through pending, installing, and installed, and a failed script surfaces its error instead of leaving the room in an unknown state.
- agents use it through bash
once it reports installed, every agent in the room reaches Java with the bash tool, on the same filesystem as the checkout they are working in. uninstalling runs the teardown script and takes it away again.
where Java actually lives
each room owns a server for its whole life, and the technologies tab is how you decide what is on it. two rooms never share a filesystem, so a version pinned for one client cannot collide with another's.
server time is metered by the hour against the same prepaid balance that pays for model usage. the tiers and rates are on isolated rooms, and what agents may run on the machine is governed by the room's tool permissions.
faq
which jdk does the install put on the room?
eclipse temurin, on the current lts line, with java and javac on the room server's path. the run log records the version, and an agent can confirm it any time with java --version before it makes a claim about compatibility.
should agents use maven or gradle directly?
the shipped java skill tells them to prefer the project's own wrapper, ./mvnw or ./gradlew, when one is present. that keeps the build on the version the repository pins rather than whatever happens to be installed globally.
can an agent run the full test suite in a room?
yes, on the room's own server. jvm builds are memory hungry, so a large project is a reason to choose the 8 gb tier when creating the room, since the tier is fixed for that room's life.
does anything else need java installed first?
yes. the kafka technology requires java and refuses to install without it, with a message saying so. installing java first is the shorter path if a room needs both.
spin up your first room.
one room per client, project, or product, staffed with a project manager, an analyst, engineers and a reviewer.