Skip to content

Docs: set-default --vault flag doesn't exist, vault registration instructions outdated #110

@namastex888

Description

@namastex888

Problem

The README and various integrations reference notesmd-cli set-default --vault <path> but the --vault flag doesn't exist on set-default. The actual flags are:

$ notesmd-cli set-default --help
Flags:
  -h, --help               help for set-default
      --open-type string   default open type: 'obsidian' (default) or 'editor'

How vault resolution actually works

Reading the source (pkg/obsidian/vault_path.go), --vault on other commands matches against the path suffix in ~/.config/obsidian/obsidian.json, not the key name. This is non-obvious and undocumented.

For example, if the config has:

{
  "vaults": {
    "my-key": {
      "path": "/home/user/vaults/my-brain"
    }
  }
}

Then --vault my-brain works (path ends with /my-brain), but --vault my-key does NOT.

Multi-vault setup

In multi-agent environments where multiple vaults exist (each agent has its own brain), this path-suffix matching means vault directory names must be globally unique. The README doesn't mention this.

Suggestion

  1. Remove or correct set-default --vault references
  2. Document that --vault matches against path suffix, not config key
  3. Add a multi-vault setup example

Environment

  • notesmd-cli v0.3.3
  • Linux x86_64
  • Headless (no Obsidian GUI)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions