start here

start using Node.js with your agents

sign up, open a project, and add Node.js to its setup script in settings → server.

Start 7-day trial with Node.js
integrationstechnologyupdated
schematic diagram of the work aldena agents do through Node.js
Node.js

node.js ai agent: agents that install, build, and run your js app

add node.js to a project's setup script and its agents get node, npm and npx through the bash tool, so they install dependencies, run scripts, and start the app.

runs on
conversation sandbox
installed by
setup script
category
runtime

node.js in a project means a real install in each conversation's sandbox rather than a capability an agent claims to have. once the setup script has run, node, npm and npx are on the sandbox's path and every agent in the project reaches them through the bash tool.

what agents do with it

the useful pattern is the loop, not the single command. an agent clones the repository onto the conversation's sandbox, runs npm ci when a lockfile is present or npm install when it is not, runs the package script the app actually uses, reads the failure, edits the file, and runs it again. because the process runs in the conversation's sandbox, the agent sees real stack traces and real exit codes instead of reasoning about what the code probably does.

the matching skill

node.js ships with a skill of the same name. skills load only for the agents you assign them to, so the build agent that works your monorepo carries the guidance on npm ci and package scripts, and the requirements agent in the same project does not.

example tasks

  • 01

    install the dependencies and get the test suite passing.

    the agent installs from the lockfile, runs the suite, reads the failures, and fixes them in the conversation's sandbox before reporting what changed.

    bashreadedit
  • 02

    start the app and tell me what the health endpoint returns.

    it starts the server in the conversation's sandbox, waits for the port, calls the endpoint from the same box, and reports the real response body.

    bashgrep

what to know before installing

the project needs a sandbox, because a project without one has nowhere to run node. settings → server shows the setup script's last run, so a failed install surfaces its error instead of leaving the project in an unknown state. a new conversation gets its own sandbox, and the setup script runs on it again.

how to install Node.js

Node.js goes in the project's setup script, not once per team and not on your laptop.

  1. give the project a sandbox

    Node.js runs in each conversation's sandbox, on your team's own sandbox provider account. an owner or admin connects a provider once on the team's providers page, then picks it and a default size for the project, at creation or later in settings → server. a project with no sandbox has nowhere to run it.

  2. add it to the setup script

    settings → server holds the project's setup script, a bash script that runs once on each new sandbox, in /project, with sudo. add Node.js's install commands there and save.

  3. the next sandbox runs it

    the script runs when a conversation's sandbox is created or reused, on the conversation's first turn. settings shows the last run with its exit code and output, and a failed run leaves the sandbox usable rather than blocking the project.

  4. agents use it through bash

    from then on every agent in the project reaches Node.js with the bash tool, on the same filesystem as the checkout they are working in. the conversation's sandbox keeps it between turns, sleeping when idle and waking with the next one.

where Node.js actually lives

each conversation in a project gets its own sandbox on your team's sandbox provider account, and the project's setup script in settings → server decides what is on it. two projects never share a filesystem, so a version pinned for one client cannot collide with another's.

the sandbox provider bills its machine time to your team's account while it runs, and aldena adds nothing. the sizes are on isolated projects, and what agents may run in the sandbox is governed by the project's tool permissions.

faq

what does installing node.js on a project actually give the agents?

node, npm and npx on the path of each conversation's sandbox, reachable through the bash tool. agents install dependencies, run package scripts, and start the app on the same machine that holds the checkout, so a build failure is something they can see rather than guess at.

is node.js installed once for my whole team?

no. each project has its own setup script, which installs what it needs in each conversation's own sandbox. one project can run node while another has only python, and neither install touches the other, because two projects never share a filesystem.

which version of node gets installed?

whichever the setup script installs. pulling the current lts line from nodesource and printing node --version at the end means the last run's output in settings → server records exactly what landed.

do other technologies depend on node.js?

yes. pnpm, turborepo, playwright, agent browser and pm2 all install through npm, so node.js has to come before them in the setup script.

ready when you are

spin up your first project.

one project per client, product, or piece of work, staffed with intake, requirements, build and code review agents.