docs/docs/en/ai/install-nocobase-app.md
Install NocoBase CLI globally first:
npm install -g @nocobase/cli
nb --version
If you often work with multiple terminals or want to operate in parallel with AI Agents, we also recommend running nb session setup once. This lets each session keep its own current env, so they are less likely to affect one another.
We recommend installing through the UI wizard:
nb init --ui
Getting started - set the --env identifier and choose Install a new appApp environment - set the app basics, storage location, and runtime portApp source and version - choose how to get the app and which source and version to useConfigure the database - choose the built-in database or a custom databaseCreate an admin account - set up the first admin accountConnection & authentication - enter the app access URL and choose an authentication methodIf you prefer terminal interaction, you can also run:
nb init
If you need to initialize in scripts or CI, use non-interactive mode:
nb init --yes --env app1
:::tip Install on a remote server
If you run nb init --ui on a server, we recommend changing the default host to that server's IP first. That way, you can open the wizard from your local browser.
nb config set default-ui-host <server-ip>
nb config set default-api-host <server-ip>
:::
After installation, it is usually worth confirming these three things first:
Common commands:
nb env list
nb env info
nb app logs
For a local default installation, you can usually open http://localhost:13000 in your browser directly. After signing in, start a new AI Agent session or restart the current one, and the AI can begin working with this NocoBase app.
CLI configuration is stored in ~/.nocobase/ by default, so AI Agents can usually access it from any working directory.
If this app will be exposed to real users later, we do not recommend using IP + port for the long term. The next step is usually to put it behind a reverse proxy and enable HTTPS.
nb init command reference — Initialize a new app, take over an existing local app, or connect a remote appnb env info command reference — View the connection details and runtime configuration of the current envnb commands