Frequently Asked Questions

I see "spawn claude ENOENT" or "Claude CLI not found". How do I fix it?

The plugin can't auto-detect your Claude CLI installation. This is common with Node version managers (nvm, fnm, volta). Fix: leave the CLI path setting empty so Claudian can auto-detect. If that fails, run which claude (macOS/Linux) or where.exe claude (Windows) and paste the path into Settings → Advanced → Claude CLI path.

The npm CLI and Node.js aren't in the same directory — what do I do?

Run dirname $(which claude) and dirname $(which node) to check if they match. If not, install the native binary instead, or add the Node.js path to Settings → Environment: PATH=/path/to/node/bin.

What features does Codex support?

Codex supports: send, streaming, cancel, history reload, fork, plan mode, image attachments, inline edit, and $ skills. Not yet supported: rewind, runtime-discovered provider commands, in-app MCP management, and Claude plugin integration.

Which Claude CLI path should I use on Windows?

For native installs use claude.exe; for npm installs, run npm root -g to find the global root and use cli-wrapper.cjs from there. Avoid .cmd and .ps1 wrappers, and the legacy cli.js.

Does Claudian collect any of my data?

No telemetry whatsoever. What gets sent to the API: your input, attached files, images, and tool-call outputs — to the API provider you configure (Anthropic or OpenAI by default). Local storage: vault/.claudian/ (settings) and vault/.claude/ (Claude provider files).

Which platforms are supported?

Claudian is desktop-only (macOS, Linux, Windows), requiring Obsidian v1.4.5+. Mobile (iOS/Android) is not supported.