A twin is a queryable assistant backed by its own knowledge base. Ask it something and it retrieves from what it’s been given, drafts an answer, and tells you how confident it is — escalating to a human when it isn’t sure.

​
Types

​
Creating one

Your first twin is created when you sign in. After that:
Or use the + button in the macOS app sidebar.
twin create adds a twin to your existing workspace — it never spins up a new one. Team twins need a teamId the CLI doesn’t collect; create those in the app.

​
Switching between them

The active twin is the target for ask, ingest, and the connectors. bestmate ask has no per-question target flag — switch first.

​
Isolation

Twin scoping is enforced in two independent places: application code and Firestore security rules. A twin can only reach chunks belonging to its workspace and targeted at it, and visibility gates access on top of that (private → team → tenant → public).

​
Structure inside a twin

Under each twin sit context stores — named compartments like “Botwick CLI” or “Q3 Rebrand”. Questions route to the relevant stores rather than scanning the whole corpus.

Context stores

Creating stores and auto-routing content into them.

Team members

Inviting people to a team twin and fencing them to it.

​
Archiving

Soft-deletes the twin so it stops appearing in listings. You must own it, and the underlying data is preserved — this is reversible.