start using PHP with your agents
sign up, open a project, and add PHP to its setup script in settings → server.
php on a project is a real runtime on a real machine. once the setup script has run, php is in the sandbox's path and every agent in the project reaches it through the bash tool.
what agents do with it
the loop is run, read, edit, run. an agent executes a script with php script.php and reads the actual notice, warning, or fatal error with its file and line. php -m answers which extensions are loaded, which turns a vague failure into a specific missing module. php -S 127.0.0.1:8000 starts a development server in the conversation's sandbox so a route can be exercised rather than read.
the matching skill
php ships with a skill of the same name. it covers checking the version and the module list, running scripts, starting the built-in server, and the fact that composer is a separate install. skills load only for the agents you assign them to, so the engineer working the php service carries it and the rest of the project does not.
example tasks
- 01
this endpoint returns a 500. find the cause.
the agent starts the built-in server in the conversation's sandbox, calls the route, reads the fatal error with its line number, and fixes the file it points at.
bashreadedit - 02
will this script run on our php version?
it checks the runtime version and the loaded modules in the conversation's sandbox, runs the script, and reports the specific syntax or extension that would fail.
bashgrep
what to know before installing
the project needs a sandbox. composer, framework tooling, and any extension the app needs beyond the defaults go in the setup script alongside php itself.
how to install PHP
PHP goes in the project's setup script, not once per team and not on your laptop.
- give the project a sandbox
PHP 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.
- 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 PHP's install commands there and save.
- 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.
- agents use it through bash
from then on every agent in the project reaches PHP 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 PHP 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 php on a project give the agents?
the php runtime and cli in each conversation's sandbox. agents run scripts with php script.php, list the loaded modules with php -m, and start a development server with php -S when they need to exercise a route rather than read it.
does installing php include composer?
no. installing php gives the runtime and cli. if a project uses composer, add it to the setup script too, before anything runs composer install. the shipped php skill says the same thing so agents do not assume it is there.
how does an agent know which extensions are available?
php -m lists the loaded modules in the conversation's sandbox, so an agent checks rather than assumes. a missing extension is then a specific thing to install rather than a mysterious failure halfway through a run.
can agents work on a legacy php codebase?
yes, and this is where a real runtime helps most. an agent can run the actual file, see the notice or the fatal error with its line number, and work from that instead of reasoning about behaviour spread across includes.
spin up your first project.
one project per client, product, or piece of work, staffed with intake, requirements, build and code review agents.
