Assistants
An assistant is a Backboard entity that acts as a namespace for memories. Each assistant has its own isolated memory store. When you run tribal init, TribalMind creates an assistant for your project.
How assistants are identified
Section titled “How assistants are identified”TribalMind identifies projects using the git remote URL. When you run tribal init:
- It reads the git remote URL (e.g.,
github.com/yourorg/yourrepo) - It creates (or finds) a Backboard assistant with that identifier
- The assistant ID is stored in
.tribal/config.yaml
This means the same repo cloned on different machines will automatically share the same assistant and memories.
Per-project vs global
Section titled “Per-project vs global”Per-project (default)
Section titled “Per-project (default)”tribal initCreates a .tribal/config.yaml in your project root with the assistant ID for that specific repo. Memories are scoped to this project only.
Global
Section titled “Global”tribal init --globalCreates a config at ~/.config/tribalmind/tribal.yaml. Any repo that doesn’t have its own .tribal/config.yaml will use this global assistant.
Cross-repo search
Section titled “Cross-repo search”Even with per-project assistants, you can search across all assistants in your Backboard account:
tribal recall --all "auth token handling"This is useful when you know knowledge exists somewhere but aren’t sure which project it’s in.
Managing assistants
Section titled “Managing assistants”List all assistants in your account:
tribal config assistantsClear all memories for a specific assistant:
tribal config clear-memory --assistant asst_abc123Configuration precedence
Section titled “Configuration precedence”TribalMind resolves the assistant ID using this chain:
- Environment variable:
TRIBAL_PROJECT_ASSISTANT_ID - Per-project config:
.tribal/config.yaml→project_assistant_id - Global config:
~/.config/tribalmind/tribal.yaml→project_assistant_id
See Configuration for the full config precedence chain.