Messaging Intelligence Engine

Run Nomister on your Mac

These commands restart an existing, configured installation. Use two Terminal windows: one for the Facebook Agent and one for the projection worker. Keep both running and your Mac awake while using the local services.

The Agent receives Facebook messages and handles replies. The projection worker makes received events available in the Nomister inbox. If your worker is already running on a server, you do not need to start a local worker.

Commands below assume your checkout is in $HOME/_NOMISTER/nomister. Adjust that path if yours is elsewhere.

Start the Agent · Start the projection worker · Add a Facebook account

Start the Agent

Use your usual Agent Terminal, with the same paired data directory and Gateway settings. In a new Terminal, restore your existing local environment first, including NOMISTER_DATA_DIR if you use a custom directory, NOMISTER_GATEWAY_HTTPS_URL, and your history/reply options. Environment variables from another Terminal are not automatically shared.

For a normal restart:

cd "$HOME/_NOMISTER/nomister" &&
corepack pnpm agent:local:run --facebook-playwright-receive

After an Agent or dependency update, or if the compiled artifact is missing, rebuild before starting:

cd "$HOME/_NOMISTER/nomister" &&
corepack pnpm agent:local:prepare &&
corepack pnpm agent:local:run --facebook-playwright-receive

To allow adding Facebook accounts from Settings, run this in the same Terminal before starting the Agent:

export NOMISTER_FACEBOOK_PLAYWRIGHT_ACCOUNT_SETUP_ENABLED=true

Keep your existing NOMISTER_FACEBOOK_PLAYWRIGHT_SEND_ENABLED, NOMISTER_FACEBOOK_PLAYWRIGHT_LOAD_HISTORY, and browser-capacity settings when restarting. The account-setup flag alone does not enable sending.

Once the Agent is connected, go to Settings, select your Mac, and click Refresh accounts. “Paired” means registered, not necessarily online. The Facebook accounts section includes the remaining login and enable steps.

For a first-time installation, configure and pair the Agent first. Do not initialize a new data directory or pair again just to restart an existing installation.

Start the projection worker

In a separate Terminal, a normal restart only needs:

cd "$HOME/_NOMISTER/nomister" &&
corepack pnpm projection-worker:local:run

Run already validates the configuration. You do not need to run projection-worker:local:validate separately every time.

After a worker or dependency update, or if the compiled artifact is missing:

cd "$HOME/_NOMISTER/nomister" &&
corepack pnpm projection-worker:local:prepare &&
corepack pnpm projection-worker:local:run

To check configuration without starting the worker:

corepack pnpm projection-worker:local:validate

The launcher reads your existing configuration from $HOME/.nomister/projection-worker.env. If you use another file, pass --config /absolute/path/to/your/file to run or validate. You do not need to source the database environment in this Terminal.

An idle outcome means there is currently no eligible work to process. UI-only updates do not require rebuilding or restarting the worker.

Stop or restart safely

Press Ctrl+C in the service’s Terminal and wait for it to exit before starting it again. Restart only the service you need; leave the other one running. A normal restart does not require a database reset, migration, or deleting locks.