charlesxiaomi382 downloadsA minimal AI writing and knowledge agent for your vault. Calls the Anthropic API directly, so it works on mobile as well as desktop.
A minimal AI writing and knowledge agent for your Obsidian vault. It calls the Anthropic Messages API directly from the client, so it works on Obsidian mobile (Android/iOS) as well as on desktop — no Node.js, no local CLI, no companion server.
read_note — read a note's contentwrite_note — replace a note's full contentpatch_note — apply a targeted edit to part of a notecreate_note — create a new notesearch_vault — full-text search across the vaultlist_files — list files and folders/v1/messages streaming API, so you can point it at a proxy or a compatible third-party gateway.This plugin requires an account with a third-party AI provider:
https://api.anthropic.com) using an API key you supply. See Anthropic's privacy policy and terms.Your API key is stored in plaintext in .obsidian/plugins/claudian-mobile/data.json inside your vault. If your vault is synced or shared, the key travels with it — use a key you are comfortable having on every device that syncs the vault.
sk-ant-...). You can create one at console.anthropic.com.Not yet available — this plugin is pending review.
main.js, manifest.json, and styles.css from the latest release.<your vault>/.obsidian/plugins/claudian-mobile/.Install BRAT and add the beta plugin Charlesxiaomi/claudian-mobile.
npm install
npm run dev # watch build
npm run build # production build
npm test # jest unit tests
npm run typecheck
npm run lint
Set OBSIDIAN_VAULT=/path/to/vault to have the build copy main.js, manifest.json, and styles.css straight into that vault's plugin folder.
Releases are built by GitHub Actions; the trigger is a version tag.
npm version patch # or minor / major
git push --follow-tags
npm version bumps package.json, then a version hook syncs manifest.json
and adds the new entry to versions.json, so all three land in the version
commit that npm tags. Tags are bare version numbers (0.2.0, no v prefix) —
that is what Obsidian's installer and BRAT expect.
Pushing the tag runs .github/workflows/release.yml:
it typechecks, lints, tests, builds, verifies the tag matches manifest.json,
and publishes a release with main.js, manifest.json, and styles.css
attached. Those build outputs are deliberately not committed to the repo — a
release is the only place they are published, so cloning the repo alone is not
enough to run the plugin.