Meet your bots — onboarding card
Round 2, from your notes. The start page uses the team network, the bot cards come from the real picker with vendor bots, and there's a calendar step and a guided first job.
Lead: The start page now runs the Bots network canvas that shipped on www (#63), using the real Gizzi Presents rigs. The bots you pick on later pages join a small version of that network, so the start page leads into the rest. The "Set up your main bot" dialog still opens whenever no main bot is connected.
Prototype — click through it
Your notes → what changed
| Your note | Change |
|---|---|
| Set up your main bot always shows while no main bot is connected | Kept as it works today. The plan no longer removes the auto-open. The card's main bot page is that same picker |
| Use the main bot picker's nice preview cards | Giant stage on the look's colour field, blur-bloom swap (620 ms), bob, tone tag and a sample line, all from bot-look.css |
| Vendor bots must be shown | A "Bots you already use" row: Claude, ChatGPT, Grok and Meta AI, with the real connect step (subscription or API key). Import and New bot sit next to them |
| Start page more interesting, use the hero video | The www Bots network plays (Claude → Dots → Grok → Muse hand-off, speech bubbles, then the crowd joins). The headline builds word by word |
| Question and options at the top weren't good | "What should your team handle first?" Each option is an outcome card: the bot that does it and a sample of what it hands back. Every pick adds that bot to your network |
| Bot selection needs animated cards and more choices | 11 looks plus Import and New bot. Tiles spring in, lift on hover, and fire the picker's block-square ripple |
| No daily check-in; something important for a routine; calendar we're integrating; skippable | "Connect your calendar" (Google Calendar or Outlook, both already in the connector directory). Routines: morning brief, meeting prep, follow-ups, focus time. Your day fills in live on the left. Skip for now |
| First job needs guidance | Three suggested jobs from your picks and your calendar. Tap the underlined words to change them. The left side shows the exact steps and what the job needs. "Or write your own" |
| The last page and the suggested team were good | Kept. "Add all" added, and added bots join the network on the left |
Where it runs
- Setup: six pages (Start, Work, Main bot, Calendar, First job, Team) replace what's inside the Main bot step. The step order stays the same.
- Bot Mode first visit: a main bot is already connected, so it skips Work and Main bot. The headline names your main bot. Switch to it with the toggle at the top of the prototype.
- Phone and PWA: the same component. The visual sits on top and the panel below. Use the Phone toggle to see it.
What gets built
| Piece | Real source |
|---|---|
| Network on the start page | Move BotTeamNetwork + cast2d/stage2d into a shared package that both www and allternit-ai import. Never two copies |
| Main bot page | The existing useBotSetup, BotLookStage, BotLookTiles and vendor connect (QuickConnect), plus a tone and sample line per look in bot-looks.ts |
| Tone | Saved into the main bot's instructions, so it really talks that way |
| Work picks | Mapped to BUILTIN_BOT_TEMPLATES ids. "Add" creates the real bot, reporting to the main bot |
| Calendar | Google Calendar and Outlook connectors. Routines become the main bot's scheduled tasks. Read-only: it never accepts or moves events without asking |
| First job | Starts real thread #1. Missing connectors (Gmail, GitHub and others) get connected in one step before it runs |
| Seen flag | Stored on the account, so the card shows once across Desktop, web and phone. "Replay intro" in Bot settings |
| Docs | Bots guides + nav in surfaces/docs, same PR |
Not checked yet
- Whether the Google Calendar and Outlook connectors can already run scheduled reads for a bot, or only for chat. I check this first in the build. If they can't, the routines wait until the integration you mentioned lands, and the page says so.
- Template ids for money, meetings, code and plan. The prototype uses placeholders. The build uses the real ids from the catalog.
- The prototype loads its art from ai.allternit.com, and I haven't clicked through it in a real browser.