AI for Obsidian notes while keeping your Markdown files

You can use AI with Obsidian notes through a community plugin, an external assistant that reads files, or a separate notebook. Choose by the job you want done and the changes you are willing to allow. Before connecting a whole vault, test three sample notes and check the answer against the actual files.

Keeping Markdown locally gives you control over the files. It does not, by itself, mean that an AI model runs locally or that note content stays on your computer.

Choose the job before the tool

For assistance inside Obsidian, investigate a community plugin. The official directory has an AI category, but plugins have different providers, permissions, and editing behavior. Read the selected plugin's documentation rather than assuming every “Obsidian AI” tool works alike. Obsidian community directory

For extracting information from a web page, Obsidian's own Web Clipper has an optional Interpreter. It can summarize, translate, or extract content into a clipping template, using a chosen provider or a supported local model. This is a page-capture workflow, distinct from answering over your existing vault. Interpreter documentation

For custom operations over files, a coding assistant can be appropriate. Claude Code, for example, can read files, edit them, and run commands. Decide which of those abilities the task needs. A question about notes should not silently become permission to reorganize them. Claude Code overview

For a fixed notebook that helps you make something of what you learn, Graphite offers an Inbox for everything you write down, folders and projects of your own, the Graphite button and the Guide beside every note, and Actions — what's missing, an outline or a first draft arranged from your own sentences, a page you publish — plus explaining, connecting, and teaching back. Its Mac app works with a folder of Markdown; its browser notebook uses separate browser storage. The Graphite and Obsidian comparison explains where each fits, including plugins, platforms, and sync.

Make a three-note test vault

Create a small separate folder and open it as a test vault in Obsidian. Use invented material instead of your private archive. These three files are enough to test whether an assistant follows evidence.

Decisions.md

---
status: draft
---
Our fictional team tests a reversible change before a full rollout.
For the signup form test, success means fewer people need help.
We have not recorded the result yet.

Related: [[Reversible changes]] and [[Open questions]]

Reversible changes.md

A reversible change can be withdrawn if its result is poor.
Our signup form test can be rolled back to the previous form.

Open questions.md

- [ ] How many people needed help with the old signup form?
- [ ] Who will check the test results?

Keep a copy of these originals. Their exact filenames, the status property, and the uncompleted questions give you things to inspect after the session. Obsidian keeps notes as local files, so you can examine the folder with an ordinary text editor. Obsidian's file model

Ask one answerable question and one impossible one

Ask your selected assistant:

According to these notes, why can we test the signup form before a full rollout? Name the notes that support your answer. Do not edit any files.

The supported answer is modest: the change is reversible, and the previous form can be restored. It should identify the relevant notes. A claim that the experiment has already succeeded is unsupported.

Then ask:

How many people needed help after the test?

The notes do not contain a result. An answer acknowledging that absence passes this part of the exercise. An invented number fails, even if it sounds plausible or includes a citation.

Open each cited file yourself. A citation shows where an answer points; you still need to check whether the cited sentence supports the conclusion. Also notice whether the assistant distinguishes an open question from an established fact.

Inspect what changed

Compare the folder with your original copy. For this read-only task, no file needed to change. Check the note bodies, names, status: draft, and the two unticked questions.

If you next ask the assistant to save an answer, give it a separate destination and keep the source notes unchanged. Label the saved text as an AI answer, and include the source-note links. That lets you distinguish your original record from a generated interpretation later.

For a filing task, define the expected change before running it. Adding a relationship, moving a file, rewriting its body, and deleting it are different operations. Check which happened. If an undo feature exists, test its limits on this disposable sample before depending on it.

Understand what reaches the model

Answer these questions for the particular tool you choose:

• Does it send selected notes, search matches, or a larger index?
• Does it send content directly to a provider or through another service?
• Can it edit files, and can you review a proposed edit?
• Does it use an API key, a separate subscription, or a local model?
• Where are generated answers and conversations stored?

For example, Web Clipper's Interpreter documentation says requests go directly to the selected provider and describes local-model options. That statement applies to Interpreter; it says nothing about an unrelated plugin's data handling. Interpreter privacy and models

Try Graphite with the same evidence test

You can manually copy the sample text into Graphite's browser notebook to try its current Ask workflow. This creates a separate set of notes; the browser cannot open or synchronize your Obsidian folder.

Ask finds matching notes on your device and sends those notes with your question to the AI you choose in Settings → AI. It shows which notes were sent and cites supporting notes. When the supplied notes do not cover the answer, it can say so. The sample questions above are a way to examine that behavior, not a guarantee of identical model wording.

In the browser, the request passes through Graphite's server to that AI's provider; Graphite's server stores neither your key nor notes. In the Mac app, a request on a key of your own goes from the app's local server directly to your provider. Check the download page for the available Mac build and its current features before expecting browser features in that release.

Graphite does not run Obsidian plugins or provide its own sync. It does not read a dropped book or paper as learning material. If the sample makes you want less filing, continue with organizing notes around ideas. If you want to test your understanding of those notes, use the teach-back exercise.