Configurable vault subfolder as Claudian working directory
Hi! I’d like to revisit the request from #796 and #794.
My Obsidian vault contains several projects, but I normally want Claudian scoped to one vault subfolder rather than the entire vault root. Ideally, a conversation could select a vault-relative working directory such as:
Projects/MyProject/That directory would then become the Claude SDK’s cwd, while default behavior would remain unchanged for users who prefer the vault root.
I noticed that PR #390 introduces similar working-directory plumbing for Skill Runs. Would you be open to generalizing that mechanism for regular Claudian conversations?
A minimal implementation could be:
- Default to the vault root, preserving existing behavior.
- Allow selecting a vault subfolder per conversation.
- Persist the selection with the conversation.
- Scope path validation and Claude’s
cwdto the selected folder. - Provide a command or folder picker to change or reset it.
This would let users keep one larger Obsidian vault while giving each Claudian conversation a focused project boundary. It would also avoid needing separate vaults, Nested Vaults, or local patches.
If this direction is acceptable, I’d be interested in helping test it or contributing an implementation.
Source: YishenTu/claudian