A MANUAL workflow for working on your vault with AI

Is this project open source? Yes/No
Is this project completely free? Yes/No - there are sources of free tokens out there.
Is this project made with AI beyond the author’s ability to comprehend how it works? Yes/No


While there are projects to connect up to your vault, this process is more manual. You might find this helpful.

Ingredients:

  • nono.sh workflow
  • an AI harness. I use ClaudeCode with Deepseek. You might use OpenCode and a strong local model such as Qwen. Share your experiences with that.
  • Wick from krypsis-io. But you could use Presidio or some other Pii filter.

Workflow:

  1. Use WICK to redact your vault, copying it to a new location.

  2. Protect your system using NONO sandbox, but allow it read access to your redacted vault.

  3. Use that read only access to PLAN and create scripts that use the OBSIDIAN CLI to clear up your vault, make MoC for you etc.

Experiences:

I found that Wick missed a few filenames named after people. Then even the AI missed these names too. So I had to manually work with those. A better workflow might be something that can redact and unredact data in the same flow, especially with other tools,

but this manual approach helps us to stay in control of the process.