Gateway on macOS

Gateway on macOS (external launchd)

AgenticFlow Enterprise.app no longer bundles Node/Bun or the Gateway runtime. The macOS app expects an external agenticflow-enterprise CLI install, does not spawn the Gateway as a child process, and manages a per‑user launchd service to keep the Gateway running (or attaches to an existing local Gateway if one is already running).

Install the CLI (required for local mode)

You need Node 22+ on the Mac, then install agenticflow-enterprise globally:

npm install -g agenticflow-enterprise@<version>

The macOS app’s Install CLI button runs the same flow via npm/pnpm (bun not recommended for Gateway runtime).

Launchd (Gateway as LaunchAgent)

Label:

bot.molt.gateway (or bot.molt.<profile>; legacy com.agenticflow-enterprise.* may remain)

Plist location (per‑user):

~/Library/LaunchAgents/bot.molt.gateway.plist (or ~/Library/LaunchAgents/bot.molt.<profile>.plist)

Manager:

The macOS app owns LaunchAgent install/update in Local mode.
The CLI can also install it: agenticflow-enterprise gateway install.

Behavior:

“AgenticFlow Enterprise Active” enables/disables the LaunchAgent.
App quit does not stop the gateway (launchd keeps it alive).
If a Gateway is already running on the configured port, the app attaches to it instead of starting a new one.

Logging:

launchd stdout/err: /tmp/agenticflow-enterprise/agenticflow-enterprise-gateway.log

Version compatibility

The macOS app checks the gateway version against its own version. If they’re incompatible, update the global CLI to match the app version.

Smoke check

agenticflow-enterprise --version

AGENTICFLOW_ENTERPRISE_SKIP_CHANNELS=1 \
AGENTICFLOW_ENTERPRISE_SKIP_CANVAS_HOST=1 \
agenticflow-enterprise gateway --port 18999 --bind loopback

Then:

agenticflow-enterprise gateway call health --url ws://127.0.0.1:18999 --timeout 3000