Onboarding Overview
Pllan has two onboarding paths. Both configure auth, the Gateway, and optional channels — they just differ in how you interact with the setup.Which path should I use?
| CLI onboarding | macOS app onboarding | |
|---|---|---|
| Platforms | macOS, Linux, Windows (native or WSL2) | macOS only |
| Interface | Terminal wizard | Guided UI in the app |
| Best for | Servers, headless, full control | Desktop Mac, visual setup |
| Automation | --non-interactive for scripts | Manual only |
| Command | pllan onboard | Launch the app |
What onboarding configures
Regardless of which path you choose, onboarding sets up:- Model provider and auth — API key, OAuth, or setup token for your chosen provider
- Workspace — directory for agent files, bootstrap templates, and memory
- Gateway — port, bind address, auth mode
- Channels (optional) — WhatsApp, Telegram, Discord, and more
- Daemon (optional) — background service so the Gateway starts automatically
CLI onboarding
Run in any terminal:--install-daemon to also install the background service in one step.
Full reference: Onboarding (CLI)
CLI command docs: pllan onboard
macOS app onboarding
Open the Pllan app. The first-run wizard walks you through the same steps with a visual interface. Full reference: Onboarding (macOS App)Custom or unlisted providers
If your provider is not listed in onboarding, choose Custom Provider and enter:- API compatibility mode (OpenAI-compatible, Anthropic-compatible, or auto-detect)
- Base URL and API key
- Model ID and optional alias