Obsidian and note folders

Updates and repair

The desktop app checks for releases from its update control. Installing a newer version migrates unchanged managed skills and protocols with backups. Personal notes and customized files are preserved.

Configuration includes Repair. Repair restores a connection from the bundled definitions, backing up previous contents and preserving unrelated global instructions. Ambiguous or malformed rule blocks remain untouched for review.

A useful starting point

New and empty folders receive the protocol plus linked Home, About me, Projects, Decisions and Lessons notes. Existing folders receive missing starter notes without replacing existing content. Older installations migrate managed files on launch; customized notes are preserved.

The memory skill is named claudian-memory. Startup rules ask the host to load it quietly. Claude Code exposes /claudian-memory; Codex supports explicit skill selection with $claudian-memory. Host permissions and invocation settings still apply.

Protocol 2.1 defines admission criteria, targeted updates, invalidation, deletion and NO_OP, with source, validity and uncertainty. It is a behavioural contract, not an enforced memory database. Semantic merging of purchased brain packs with an existing vault is a future feature, not part of this release.

Review existing context

The optional desktop review opens an editable message. Press Enter to launch a supported interactive AI session; Shift + Enter inserts a line. Direct launch currently requires a native Codex CLI or Claude Code executable. Other installed skill connections do not yet support this launcher.

The AI can review only memories and connected sources available to its session, subject to its permissions. It asks focused questions when context is missing. This does not transfer histories between providers or start continuous background scanning. The session uses your existing provider account and its usage limits.

If Obsidian is missing, Download Obsidian opens the official download website. Return to Claudian after installing it to open your notes.

Your folder is the memory

A vault is a folder of notes. Claudian’s desktop preview uses filesystem access to read and prepare that folder; it does not sign in to an Obsidian account or require an Obsidian plugin.

When you connect existing notes, setup preserves their content. If no recognized protocol is present, it adds a separate Claudian Memory Protocol.md. It does not reorganize or bulk-import your existing collection.

Choose the folder deliberately

The discovery step reads registered Obsidian vault paths and checks a few common locations. The first discovered folder is only a suggestion. Choose another path in setup if needed.

One installation currently stores one selected vault. Switching the active vault in Obsidian does not switch Claudian. After setup, there is no supported vault-switching interface yet.

The memory panel provides direct access to the note folder and an Obsidian link. For a new vault, close Obsidian once and use Open in Obsidian. Claudian backs up the local vault registry, adds the selected folder and opens its home note. If Obsidian is running, registration waits until you close it. Existing vault registrations are reused.

Let related notes stay connected

A note holds a coherent concept. Links connect it to projects, decisions and related knowledge. A map of content provides a small entry point into a topic instead of forcing every conversation to load the entire collection.

A useful link explains a relationship. Adding links everywhere or creating a new file for every sentence makes memory harder to maintain.

# Project decision

Use a local Markdown folder for durable context.

Related: [[Memory protocol]] · [[Project overview]]