Documentation / Installation

Connect the local app

Open Bee Team in your browser and connect it to the Bee Team service running on this computer.

Why a local connection is needed

The website provides the interface and connects to the local API. The Bee Team binary runs the API and MCP on your computer; by default, task data is stored locally in SQLite. Opening the website does not install or start that service. The connection screen means the interface could not verify it; the service may be stopped, browser access may be blocked, or another port may be in use.

Use the browser on the same computer as the service. The address 127.0.0.1 refers to the device opening the page: a phone cannot reach your computer's service through that address.

The official binary serves the panel on the same port as the API by default. If your assistant’s browser blocks the connection from the website, open the local panel directly. If you changed APP_PORT, replace 59865 in the address. If you set BEE_FRONTEND_MODE=disabled, remove that setting and restart the service. Open local panel

Connect step by step

Start the installed Bee Team service
If it is already running, keep that process and continue to the next step. Otherwise, open a terminal in the folder containing the installed binary and run the command for your system. If Bee Team is not installed, follow the installation guide first.
Read the installation guide
PowerShell
```
$env:APP_PORT = '59865'
.\beeteam.exe
```
Terminal · macOS / Linux
```
APP_PORT=59865 ./beeteam
```
Keep the terminal open while using Bee Team, unless your installation already runs it as a background service. These commands use the default port without resetting your database.
Check that the local API responds
In a second terminal, run these read-only health and service identity checks:
PowerShell
```
Invoke-RestMethod http://127.0.0.1:59865/health
Invoke-RestMethod http://127.0.0.1:59865/api/v1/info
```
Terminal · macOS / Linux
```
curl -fsS http://127.0.0.1:59865/health
curl -fsS http://127.0.0.1:59865/api/v1/info
```
Both requests should return JSON; info includes apiVersion. This confirms the service responds on that port. Browser permission is still required, and the interface and service versions must match.
Allow the browser to access the local service
Open https://getbee.team/app/ and allow the request to connect to your local device or network if your browser shows one. This lets the website reach the Bee Team service on your computer. The permission name and availability depend on your browser version.
Check the connection again
Return to the app and select “Check connection again”. When the service responds and its version matches the interface, the app opens automatically. If it asks for an update, follow that separate version instruction.
Open local panel

Three common connection problems

1. The local app is not running

Symptom: health and info cannot connect, or the terminal that started Bee Team has been closed.

Start the installed binary using step 1, keep it running, and repeat the terminal and browser checks. If startup reports an error, read it before starting another process. A connection failure does not require reinstalling or deleting your data.

2. The browser has blocked local access

Symptom: the terminal checks succeed, but the website cannot verify the service, or you previously denied its access request.

With getbee.team open, select the site controls beside the address bar and open the site's permissions/settings.
Find local network access or apps on this device. Allow it for getbee.team, or reset the denied permission so the browser can ask again.
Reload the app, accept the prompt if it appears, and select “Check connection again”.

Chrome and Edge may use different labels, and managed browsers may lock this permission. If the control is unavailable or managed, consult browser help or your administrator. Do not disable browser security or your firewall.

Chrome site permission help · Edge local network permission help

3. The service is using a different port

Symptom: the startup log shows a port other than 59865, or health responds on another port while the default address fails.

The hosted app connects to http://127.0.0.1:59865/api/v1. Check the startup address and APP_PORT. To use the hosted app, stop your existing Bee Team process safely and start that same installation with APP_PORT=59865 as shown above. Do not start a second copy against the same data. If another program occupies the port, resolve that conflict before retrying.

The hosted app has no runtime port selector. Another API address requires your own frontend build configured with VITE_API_BASE_URL. Changing APP_PORT alone does not change the endpoint used by the public website.

Environment reference