App management

Overview

All recording commands — explore, explore-guided, run-instruction — start by reading the currently active app to know which URL to work with and what the app does. Use /bu:apps to register applications and set which one is active.

Apps are persisted locally in .brow-use/apps.json. You register an app once and switch between them as needed — you do not need to re-register every session.

Command

/bu:apps

Manage all saved apps in one conversational command. Supports list, create, delete, and set current. Run this and describe what you want to do — Claude will ask for any missing details and update .brow-use/apps.json directly. Setting the current app only updates the active app record; it does not open a browser.

File shape

{
  "currentAppId": "<id or null>",
  "apps": [
    {
      "id": "uuid-...",
      "name": "Avni — Field App",
      "description": "Mobile-first form-driven data collection app...",
      "url": "https://staging.avniproject.org",
      "createdAt": "2025-04-22T10:14:00.000Z"
    }
  ]
}

The description is more than metadata — it's used as exploration bias in /bu:explore and as grounding context in /bu:run-instruction. A specific description ("registers visits for community health workers") leads to better-focused runs than a generic one ("a web app").

Typical setup sequence

For a new application:

/bu:apps                    register the app and set it as current
/bu:explore                 walk it autonomously

In subsequent sessions, run /bu:apps again to set the current app — it is already registered.