AI Linzi
approvedby Alina霖子
把 AI霖子接入 Obsidian 数字大脑,支持侧边栏对话、Vault 搜索、内容创作、文章配图、公众号排版与发布. - This plugin has not been manually reviewed by Obsidian staff.
AI Linzi
AI Linzi connects Alina's business coaching service to a local knowledge Vault. It provides sidebar chat, local search, note-aware content workflows, AI illustrations, long-document processing, and WeChat formatting and publishing.
Features
- Chat with AI Linzi in a sidebar and optionally include the active note.
- Search Markdown, TXT, text-based PDF, and DOCX files locally.
- Send only a bounded set of relevant excerpts to the service.
- Explicitly select complete documents for authorized long-document tasks.
- Create new notes and folders after an in-app confirmation.
- Generate or revise article illustrations and save successful images locally.
- Format WeChat articles and send them to a configured WeChat draft box.
- Review local content activity and authorized account data in the one-person-company cockpit.
Installation
Install AI Linzi from the Obsidian community plugin directory when the listing is available:
- Open Settings → Community plugins → Browse.
- Search for AI Linzi.
- Select Install, then Enable.
- Open the AI Linzi settings tab and paste a connection key created at chat.alinalinzi.com.
AI Linzi is currently desktop-only and requires Obsidian 1.11.4 or later.
Privacy and network access
Local search scans supported files in memory on the user's device. It does not create a cloud index or upload the whole Vault. For a normal chat request, the plugin sends only the active note, explicitly authorized documents, or a bounded set of locally matched excerpts.
The plugin reads or writes Vault files only for user-triggered actions such as including a note, saving a generated result, creating a confirmed note or folder, inserting an image, or publishing a WeChat draft. Connection keys and WeChat AppSecrets use Obsidian SecretStorage and are not written to plugin settings or logs.
Generated images and local conversation cards remain in the Vault or Obsidian-managed local plugin data. Cloud history contains text only and excludes local paths and image data.
Security and implementation notes
- The public repository is a thin client. Private prompts, model routing, billing, account data, and service-side orchestration remain on the AI Linzi service.
- Vault enumeration powers user-enabled local search. Only bounded matched excerpts are transmitted.
- Clipboard access occurs only after an explicit user copy action.
- PDF.js is bundled for local extraction of text-based PDFs. It supplies the dynamic-code finding reported by automated static analysis; no remote script or CDN is used.
- Streaming chat uses
fetchbecause Obsidian'srequestUrlAPI buffers the complete response and does not expose the response stream. - The official release contains only
main.js,manifest.json, andstyles.css. GitHub Actions generates build-provenance attestations for these assets.
Development
npm ci
npm run build
npm test
Every release tag must exactly match the version in manifest.json. The release workflow builds from source, verifies the version, creates provenance attestations, and publishes the three files supported by Obsidian's plugin installer.
License
For plugin developers
Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.