UI direction

The UI is a product direction after the CLI and Telegram foundations are stable. It should feel like a character studio and companion control center, not a boring admin dashboard with an avatar sticker slapped on top.

Goal

Create a local web console and later product UI for configuring, managing, diagnosing, and embodying Bestie.

The UI should help answer:

1. Who is my bestie?
2. Is it healthy and connected?
3. How do I tune it without breaking it?

Recommended phases

1. CLI first: bestie onboard, bestie doctor, bestie status.
2. Local web console: bestie ui opens localhost.
3. Character Studio: visual personality, avatar, and tone setup.
4. Memory Center: inspect, edit, delete, export memories, including Zep status.
5. Provider and Channel Hub: connect LLMs, Zep, Telegram, Discord, and web chat.
6. Doctor UI: visual health checks and safe repair buttons.
7. Avatar, voice, and body layer.

First UI MVP

When UI work starts, build:

• Home/status screen.
• Character editor.
• Provider setup.
• Telegram setup.
• Doctor screen.
• Logs screen.
• Chat test panel.

Design direction

• playful but useful
• bold and characterful
• avatar-forward
• warm, expressive, personal
• no gray admin-table slop
• no generic purple AI startup look

Architecture

The UI should reuse runtime services used by the CLI.

runtime services -> CLI
runtime services -> local web API
runtime services -> future hosted UI

Do not duplicate core logic in the frontend.