Back to Signal Feed
CodeTracked since May 18, 2026

Read research vault path from OBSIDIAN_VAULT_PATH

The PR fixes a path configuration bug where the research toolkit hardcoded VAULT_PATH to one developer’s local Obsidian vault, causing other users’ notes and generated obsidian:// links in /youtube, /research, /research-deep, and /notebooklm to be written to a non-existent location. It switches resolution to OBSIDIAN_VAULT_PATH via the shared get_required helper and updates .env/setup flow so the value is written in setup.sh for standalone CLI runs.

OBSIDIAN_VAULT_PATHVAULT_PATHget_requiredscripts/research/lib/config.py

What Happened

  • The PR fixes a path configuration bug where the research toolkit hardcoded VAULT_PATH to one developer’s local Obsidian vault, causing other users’ notes and generated obsidian:// links in /youtube, /research, /research-deep, and /notebooklm to be written to a non-existent location. It switches resolution to OBSIDIAN_VAULT_PATH via the shared get_required helper and updates .env/setup flow so the value is written in setup.sh for standalone CLI runs.
  • The PR fixes a path configuration bug where the research toolkit hardcoded VAULT_PATH to one developer’s local Obsidian vault, causing other users’ notes and generated obsidian:// links in /youtube, /research, /research-deep, and /notebooklm to be written to a non-existent location. It switches resolution to OBSIDIAN_VAULT_PATH via the shared get_required helper and updates .env/setup flow so the value is written in setup.sh for standalone CLI runs.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Changed research note storage to use the repository-standard OBSIDIAN_VAULT_PATH with get_required validation, so vault writes now fail fast with the standard message instead of silently targeting a wrong personal path; added setup.sh env propagation into research .env for standalone CLI sessions.

Why Track This

Why It Matters

Users running the research toolkit on any machine besides the contributor’s now save notes to their configured Obsidian vault correctly, so their research notes and generated obsidian:// deep-links are much less likely to break or disappear. This is achieved by deprecating the hardcoded vault path in favor of OBSIDIAN_VAULT_PATH plus get_required validation; next, monitor onboarding workflows where this variable is missing or not loaded in CI/automation because this change intentionally changes silent misrouting into explicit configuration failure.

Impact

Users running the research toolkit on any machine besides the contributor’s now save notes to their configured Obsidian vault correctly, so their research notes and generated obsidian:// deep-links are much less likely to break or disappear. This is achieved by deprecating the hardcoded vault path in favor of OBSIDIAN_VAULT_PATH plus get_required validation; next, monitor onboarding workflows where this variable is missing or not loaded in CI/automation because this change intentionally changes silent misrouting into explicit configuration failure.

What To Watch Next

  • Watch whether OBSIDIAN_VAULT_PATH becomes a repeated pattern.
  • Track follow-up changes around AI Integration in IDEs.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: missing_obsidian_vault_path_env, standalone_cli_environment_not_setting_env.
Open Topic TimelineOpen Technical EventOpen Original Sourcemissing_obsidian_vault_path_env / standalone_cli_environment_not_setting_env / automation_jobs_relying_on_previous_hardcoded_path

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

eugeniughelbur/obsidian-second-brain PR #17: Read research vault path from OBSIDIAN_VAULT_PATH

Previously hardcoded VAULT_PATH caused non-author environments to save research outputs into a missing vault; now OBSIDIAN_VAULT_PATH is required and read consistently through existing project convention.