start using Ruby with your agents
sign up, open a room, and install Ruby from its technologies tab.
ruby ai agent: agents that run the script and the bundle for real
install ruby on a room's server and its agents run scripts, install gems, drive bundler with bundle exec, and iterate on the error the interpreter produced.
- runs on
- room server
- installed
- per room
- category
- runtime
ruby on a room is an interpreter on real hardware. once it reports installed, ruby and gem are on the room server's path and every agent in the room reaches them through the bash tool.
what agents do with it
the interpreter is the fastest reviewer an agent has. it runs a script with ruby script.rb and reads the actual backtrace, installs the project's gems with bundle install when a gemfile is present, and runs tasks through bundle exec so the versions match the lockfile. for a web app it starts the server on the room's machine and calls the route from the same box, which turns a suspected bug into an observed one.
the matching skill
ruby ships with a skill of the same name. it carries running a script, installing gems, preferring bundler when a gemfile exists, and using bundle exec for tasks. skills are versioned documents that load only for the agents you assign them to, so the engineer on the ruby service carries it and nobody else does.
example tasks
- 01
the background job fails on some records. find the pattern.
the agent runs the job against sample data on the room server, reads the backtraces, and reports the specific attribute that is missing rather than a category of cause.
bashreadgrep - 02
bump the gem and check nothing broke.
it updates the gemfile, installs the bundle on the room machine, runs the suite through bundle exec, and shows what changed in the lockfile.
editbash
what to know before installing
the room needs a paid server tier. the install brings the ruby runtime and gem, and exits early if ruby is already present. bundler, rails, and anything else the project needs come from the project's own gemfile on the room's machine.
how to install Ruby
Ruby 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 Ruby 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 Ruby 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 Ruby 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
what does installing ruby on a room give the agents?
the ruby runtime and the gem package manager on that room's server. agents run scripts with ruby script.rb, install gems, and run project tasks through bundle exec when the repository has a gemfile.
will agents install gems globally or into the bundle?
the shipped ruby skill tells them to prefer bundle install when a gemfile is present and to run tasks through bundle exec, so the versions come from the lockfile rather than from whatever the machine happens to have.
can an agent run a rails test suite?
yes, on the room's own server. if the app needs a database, install postgresql or mysql in the same room and the suite runs against a real instance rather than a stub, all on one machine.
does the ruby install persist between sessions?
yes. the room's server is provisioned with the room and stays with it, so an installed bundle is still there next time. uninstalling from the technologies tab removes the runtime and the gem manager.
spin up your first room.
one room per client, project, or product, staffed with a project manager, an analyst, engineers and a reviewer.