Roadmap and priorities

Bestie’s roadmap is intentionally sequenced to avoid building risky power before the local character, memory, diagnostics, and permission foundation can support it.

Dangerous mistakes to avoid

Do not build Zep before local SQLite.
Do not build broad MCP or ACP before Doctor and permissions.
Do not let playful rude tone become abusive.
Do not market the agent as conscious, therapy, romance, or perfect memory.
Do not make onboarding v1 too long.

Available in local development

Implemented for local development:

terminal chat
character prompt
minimal onboarding/config wizard
OpenAI-compatible LLM calls
basic logs
local SQLite memory
memory policy and manual controls
status
Doctor checks and safe local fixes
Telegram long polling
owner-only Telegram access
Telegram slash commands
permission-gated local read tools
classified read-only MCP calls
opt-in real Telegram smoke
one-command installer smoke

The next work should stay scoped and improve first-run reliability before expanding the product surface.

Good next work:

Fuller onboarding polish when it improves first-run completion.
Doctor diagnostics polish when it protects install or real use.
Telegram reliability fixes discovered by daily local use.
Installer/onboarding handoff for non-technical users.

Planned later

Optional Zep memory.
Backup, update, migration, restore.
Local web console.
Doctor UI.
Broader tools after permissions have real terminal and Telegram mileage.

Possible future directions

Broader MCP support.
ACP/multi-agent support.
Plugin system.
Persona templates and marketplace.
Avatar, voice, and body layer.
Hosted/SaaS mode.

Hard rules

Zep after SQLite.
MCP/ACP after Doctor and permissions.
UI after CLI basics.
Installer after onboarding works.
No public marketing claims about consciousness, therapy, romance, or perfect memory.