Fix the cloud environment setup script command in AGENTS.md (#4882)

* Use an absolute path for the cloud setup script command

The environment setup script doesn't run from the repo root, so the
documented `bash scripts/dev-setup.sh --db` fails with "No such file or
directory" and blocks the session from starting. Point it at the clone
path and add `|| true` so the SessionStart hook can retry a failed install.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_014sizskTaS3oGD7ZoWHQBv8

* Note the cloud clone path for renamed forks in AGENTS.md

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_014sizskTaS3oGD7ZoWHQBv8

---------

Co-authored-by: Claude Opus 5.5 <[email protected]>
This commit is contained in:
Sam Dornan
2026-09-28 11:15:08 -05:00
committed by GitHub
co-authored by Claude Opus 5.5
parent 3b2d677724
commit 75ac420125
+1 -1
View File
@@ -79,7 +79,7 @@ place for full-suite coverage; local runs stay scoped.
Each tool version is pinned in one file: Python in `.python-version`, uv as `ARG UV_VERSION` in `docker/Dockerfile`, and Node in `frontend/.nvmrc`. Don't install these by hand. Run `scripts/dev-setup.sh`, which installs the pinned toolchain, the backend and frontend dependencies, and the Trunk launcher, and skips anything already in place. Add `--db` to also install and start MariaDB with the pytest database (Debian/Ubuntu only). Rerun it whenever a version is wrong or a dependency is missing.
In Claude Code cloud sessions, `.claude/hooks/cloud-setup.sh` runs `scripts/dev-setup.sh --db` at session start. Setting the environment's setup script to `bash scripts/dev-setup.sh --db` gets the install cached in the environment snapshot, so the hook only has to restart MariaDB. Other agents should use the same command as their setup step.
In Claude Code cloud sessions, `.claude/hooks/cloud-setup.sh` runs `scripts/dev-setup.sh --db` at session start. Setting the environment's setup script to `bash /home/user/romm/scripts/dev-setup.sh --db || true` gets the install cached in the environment snapshot, so the hook only has to restart MariaDB. The setup script doesn't run from the repo root and `CLAUDE_PROJECT_DIR` isn't set yet, so the path must be absolute. The cloud clone lives at `/home/user/<repo-name>`; adjust the path for a renamed fork. `|| true` keeps a failed install from blocking the session (the hook retries it). Other agents should run `scripts/dev-setup.sh --db` from the repo root as their setup step.
---