Set up Verity Meetings and Verity Chat from the wizard
Two new flags fork, seed and locally boot the web agents that run as always-on services, for builders putting booking pages and a grounded chat widget on their own domain.
The wizard set up scheduled agents, but the web agents, Verity Meetings (booking pages on your own domain) and Verity Chat (a website chat widget that answers only from your facts), run as always-on services and had no setup path of their own.
What's new
Run npx -y @getnoan/wizard@latest --meetings --chat. For each one you pick, the wizard:
- forks the repo to your GitHub account;
- runs its seed scripts, so its starting instructions land in your workspace in a stack of their own;
- boots it locally with no keys to prove it works;
- writes a gitignored
.envin the clone with the block slugs, plus a session secret and your model key for the chat.
Deploying needs accounts only you can create (a host, a Supabase project, and Google Calendar credentials for Meetings), so the report hands your coding assistant the rest of each repo's INSTALL.md and a one-click Render deploy link.
Good to know: your personal NOAN key is never written into either service's .env. These services face the internet, so each should get a NOAN key made for it alone, and the report says so. Under --yes both are skipped unless you pass the flag; --no-meetings and --no-chat skip them explicitly.
Why it matters
A booking page and a chat widget that both answer from your verified facts are now a few minutes of setup away from the same wizard you already use for the agent pack.