Bestie Docs

Bestie / local companion runtime

Make the runtime trustworthy before you make it powerful.

Bestie is a self-hosted AI companion with editable character files, local SQLite memory, configurable providers, and a localhost console. This documentation starts with a working local runtime, then lets you add only the capabilities you intend to operate.

Install Bestie ->Diagnose a problem ->Find a command ->

First-run board

One local runtime. Four things to establish.

1. 01
   Install

   Node.js 24+ and npm provide the local CLI.

   npm install -g bestie-agent
2. 02
   Configure

   Onboarding creates local files and sets up a provider.

   bestie onboard
3. 03
   Verify

   Doctor checks paths, config, secret presence, and provider access.

   bestie doctor
4. 04
   Talk

   Start in terminal chat or open the local web console.

   bestie chat

Secret boundary

Values belong in ~/.bestie/.env; config contains environment-variable names, not secret values.

Add capabilities deliberately

CoreTerminal + local console

Use the runtime locally before connecting a service.

Required firstChannelTelegram

Owner-only polling with attachments, voice workflows, commands, and approvals.

After Doctor passesChannelZalo

Owner-only local polling through the current text-only adapter.

After Doctor passesOperateBackground runtime

Use a daemon or managed user service, not both for one target.

When you need continuityExtendSkills, tools, and MCP

Introduce new capability under an explicit permission policy.

Review permissions firstControlLocal memory

Inspect, edit, export, pause, approve, or delete it.

Owner controlled

Operate with boundaries

Inspectable: character configuration, runtime files, local memory, diagnostics, and logs stay available to the owner.

Permission-gated: public, external, destructive, payment, and unknown actions need explicit confirmation.

Honest: Bestie is software, not conscious or human, not a therapist replacement, and not a romantic companion.

ConfigurationProviders, paths, memory, channels, tools, MCP, and voice.TroubleshootingDoctor-led checks for setup, providers, channels, and memory.Security and privacySecrets, untrusted content, approvals, and public claims.