Onboarding
Onboarding v1 should be short. The user should meet their bestie quickly. Full configuration can come later through follow-up commands.
Required v1 steps:
- Create character basics.
- Connect an LLM provider.
- Run a terminal test chat.
Telegram and memory setup can be follow-up commands.
Command
Section titled “Command”bestie onboardbestie onboard --skip-provider-testIn local development:
bestie onboardbestie onboard --skip-provider-testUse --skip-provider-test for offline setup, smoke tests, slow providers, or unavailable providers. It still creates config, env, character, prompt, and log files.
Welcome -> choose character name -> choose what agent calls user -> choose vibe preset -> choose tone sliders -> choose memory write policy -> choose LLM provider -> enter API key -> write config -> test LLM unless --skip-provider-test is set -> start terminal chatCharacter questions
Section titled “Character questions”- What should your bestie be called?
- What should it call you?
- Choose vibe preset:
- Funny Savage Bestie
- Soft Emotional Bestie
- Productivity Coach Bestie
- Chaotic Gen Z Friend
- Calm Brutally Honest Mentor
- Custom
- Roast level 1-10.
- Warmth level 1-10.
- Bluntness level 1-10.
- Language: Vietnamese, English, or mixed.
- Memory write policy:
ask,allow, ordeny. Default:ask. - Emoji level: none, light, or expressive.
- Topics it should never joke about.
LLM questions
Section titled “LLM questions”Supported setup directions:
- QuotaCheap
- OpenAI
- OpenRouter
- Custom OpenAI-compatible
Required values:
- base URL
- model
- API key
Secrets go into .bestie/.env, not .bestie/config.json.
Validation
Section titled “Validation”Onboarding should validate:
- API key presence.
- Config path writability.
- Logs path writability.
- Provider test result, when it runs.
- Provider test failure is explained but does not delete or block local files.
memory.writePolicyis written to config.
Follow-up commands
Section titled “Follow-up commands”bestie telegram setupbestie memory statusbestie doctorPrinciple
Section titled “Principle”Do not ask users to configure everything before they feel the product. Fast first magic beats complete first setup. Vibe first, bureaucracy later. Đỡ tự bắn vào chân.