Add a root-level bun run dev command

README.md

@@ -125,10 +125,10 @@ Set these before you start it. **Settings → Setup** in the app says whether th
 Then start it:
 
 ```sh
-bash scripts/start.sh
+bun run dev
 ```
 
-and open <http://localhost:3010>. The script starts Postgres and each Bot's computer in Docker, applies the database migrations, and starts the API server, the routine worker, and the app. It checks that each one answers before it prints the next steps. `bash scripts/stop.sh` stops the app, the worker, the API server and the Docker services, and removes the Bot computers that belong to this install, the ones with its `COMPUTER_NAMESPACE`. It does not touch another install's. The database, each Bot's files and its browser profile are Docker volumes, so they stay. Add `--keep-computers` to leave the Bot computers running.
+and open <http://localhost:3010>. `bun run dev` calls `scripts/start.sh`, which starts Postgres and each Bot's computer in Docker, applies the database migrations, and starts the API server, the routine worker, and the app. It checks that each one answers before it prints the next steps. `bash scripts/stop.sh` stops the app, the worker, the API server and the Docker services, and removes the Bot computers that belong to this install, the ones with its `COMPUTER_NAMESPACE`. It does not touch another install's. The database, each Bot's files and its browser profile are Docker volumes, so they stay. Add `--keep-computers` to leave the Bot computers running.
 
 If port 5432 is already taken on your machine, set `POSTGRES_PORT` in `.env` to a free port and change the port in `DATABASE_URL` to match.
 

package.json

@@ -6,6 +6,7 @@
   "description": "The open-source proactive agent, built on OpenBot. The platform lives in openbot/.",
   "scripts": {
     "postinstall": "bun install --cwd openbot",
+    "dev": "bun run start",
     "start": "bash scripts/start.sh",
     "stop": "bash scripts/stop.sh"
   }