Settings

Open Settings → BojuBot to configure:

Setting	Default	Description
Claude binary path	(auto-detect)	Full path to the claude executable. Leave blank to auto-detect from PATH and common install locations.
Context file path	_claude-context.md	Vault-relative path to the context file injected at session start.
Export folder	BojuBot Exports	Default folder for Export session to vault. Created automatically if it doesn't exist. Leave blank to save at vault root.
Session storage path	(empty — default location)	Where session JSON files are stored. See Session storage location below.
Skills folder	(empty — default: _BojuBot Skills/ at vault root)	Folder containing skill files. See Slash commands.
Vault tree depth	Off	Levels of folder/file names injected at session start. 0 = off (default), 1–10 = N levels, -1 = unlimited. Names only — no file contents. Claude discovers structure on demand via the vault query protocol when off.
Send on Enter	On	Press Enter to send. Shift+Enter always inserts a newline.
Resume last session on startup	On	Automatically resume the most recent session when the panel opens.
Autonomous memory	On	Claude updates the context file as it learns about your vault. Disable if you prefer manual control or if your vault is shared. Disabled in minimal mode.
Memory file size limit (tokens)	0 (no limit)	When the context file exceeds this token count, Claude is instructed to compact it before the session ends — summarizing redundant entries and dropping outdated observations. 0 disables the cap. Disabled in minimal mode.
Minimal mode	Off	Skip all context injection — no orientation, vault tree, context file, or active note. Reduces session start cost to zero. UI Bridge actions and vault queries will not work. Skills still work. Affected settings are greyed out when enabled.
Permission mode	Standard	Controls what vault operations Claude can perform: Chat only (web only, no file system), Standard (files + web), Read only (read + web, no writes), Full access (everything including Bash). See Permissions.
Command Allowlist	switcher:open, daily-notes, editor:open-search	Obsidian commands Claude can run via the UI Bridge. Found under UI Bridge & Commands. Allowlisted commands execute immediately.
Prompt for unlisted commands	On	When Claude tries a command not in the allowlist, show a confirmation modal. Allow + "Don't ask again" adds to allowlist. Deny + "Don't ask again" adds to denylist.
Denied commands	(hidden until used)	Shows count of permanently denied commands with a Clear denylist button. To re-enable a specific command, add it to the allowlist via the command browser.
Enable debug log	On	Write a debug log file. See Troubleshooting.
Log file path	.obsidian/plugins/bojubot/bojubot-debug.log	Vault-relative path for the log file. Defaults to the plugin folder so it stays out of your vault and git history.
Log verbosity	Normal	Normal logs session events and errors. Verbose adds raw stream data and token breakdowns.
@-mention file types	* (all vault files)	Comma-separated extensions for the @ autocomplete dropdown. * includes all vault files. To restrict, list extensions explicitly (e.g. md, pdf, txt). Add a trailing comma to also match files with no extension (e.g. md, txt,).
Inject split-pane files	On	When in split-pane view, include all visible file paths as active note context.

Custom models

BojuBot ships with a hardcoded list of Claude models (Haiku, Sonnet, Opus). When new models are released you can add them without waiting for a plugin update by creating a file at:

<vault>/.obsidian/plugins/bojubot/custom-models.json

The file is a JSON array of model objects. Any valid entries are appended to the built-in list in the /model picker:

[
  {
    "id": "claude-sonnet-4-7",
    "displayName": "Claude Sonnet 4.7",
    "description": "Latest Sonnet model"
  }
]

Field	Required	Description
id	Yes	Full model ID passed to --model at spawn time
displayName	Yes	Name shown in the picker
description	No	Short note shown below the name

The file is read each time the picker opens, so changes take effect immediately with no restart needed. If the file is missing or malformed, it is silently ignored and only the built-in models are shown.

Session storage location

By default, session files are stored in .obsidian/bojubot/sessions/ inside your vault. This folder is typically gitignored, so sessions don't appear in your git history.

You can change this in Settings → BojuBot → Session storage path:

Value	Behaviour
(empty)	Default — .obsidian/bojubot/sessions/. Gitignored.
_sessions (vault-relative)	Sessions stored at _sessions/ in your vault root. Tracked by git if not excluded.
/Users/you/sessions (absolute)	Sessions stored outside the vault entirely.

Sessions are not migrated

Changing this setting affects new sessions only. Existing sessions remain in their original location and will not appear in the session manager until you change the path back. If you want to move existing sessions, copy the .json files manually to the new path before restarting BojuBot.