Zettelkasten in Emacs: Org Mode Notes and Links

You can build a Zettelkasten in Emacs using plain Org mode files: write one claim per note, cite its source, and link it to related claims with a reason for each connection. You do not need an extra note package to begin. A small index and a repeatable review routine matter more than a complicated configuration.

Keep your thinking in Org files. When a conclusion affects active work, fenbs can hold the project decision and next step alongside references to those notes. Your personal note network can keep developing while the project has a clear record of what people actually agreed.

How do you create the first Org note collection?

Start with one folder and one real question. For example, a student preparing a research proposal might ask which observations would count against the proposal’s main explanation. These steps use ordinary files so you can understand the collection before choosing any additional software.

1. Create a folder named notes in a location you control. Inside it, create sources and ideas folders plus an index.org file. This is a suggested layout, not an Org mode requirement.
2. In Emacs, use C-x C-f to open a new .org file. Here, C means hold Ctrl; key sequences are pressed in order. Use M-x org-mode if the buffer is not already in Org mode; M-x is usually Alt+x.
3. Write a source note containing the document title, author, publication details, URL, and the page or section you used. Keep direct quotations clearly labeled.
4. Create an idea file with a stable filename and a title that states one claim. Explain that claim in a short paragraph, then link to the source note and one related idea.
5. Add the idea to index.org with a sentence explaining how it helps answer your question. Save with C-x C-s, follow the links, and check that you can return to the evidence.

A folder full of short files is not automatically a Zettelkasten. The useful part is the thinking between them: a claim, an explanation, a boundary, and a connection. See the broader second-brain collection for ways to keep notes useful beyond the first capture.

What should a working note look like?

Use readable filenames that you will not need to change every time the wording improves. A short identifier can stay stable while the title inside the file becomes more precise. The following fictional example shows the structure; replace its placeholder citation with a source you have actually read.

#+title: Useful explanations expose what would contradict them

A research explanation becomes easier to examine when I can name
an observation that would make me revise it. This is a planning
principle, not proof that the explanation is correct.

* Source
[[file:../sources/methods-reading.org][Methods reading, section 2]]

* Connections
This limits [[file:20261021-collecting-observations.org][Collecting more observations]]:
extra observations help only if I know what distinction they test.

* Open question
What observation would distinguish our two candidate explanations?

Keep the original wording of a quotation in the source note. The idea note should reveal what you understand, including what you still cannot establish. That separation makes it easier to reuse the same source for a different argument without treating your first interpretation as the author’s conclusion.

How do you insert and follow meaningful links?

Org supports web addresses and relative file links, as the official external-links manual↗ (opens in a new tab) explains. In an Org buffer, use C-c C-l to insert a link and its readable description. Put the cursor on the resulting link and use C-c C-o to open it. The link-handling manual↗ (opens in a new tab) documents these commands and M-x org-store-link, which stores a location for later insertion.

For the first collection, use relative file paths and keep the folder layout steady. A link from an idea file to ../sources/methods-reading.org means go up one folder, then into sources. After moving or renaming a file, open the notes that reference it and repair their paths.

Org also supports links to heading IDs. Consider that option when moving headings between files becomes common; it introduces an identifier and location-management convention you should understand first. You can have a useful note network before taking on that extra setup.

How do you capture ideas without creating a backlog?

Keep an inbox.org file for quick observations, then process those observations after reading. Org’s capture feature↗ (opens in a new tab) offers a way to store new material with less interruption if you later want a capture command. Begin manually so you can see whether the bottleneck is saving notes or making sense of them.

• Discard an observation if it no longer means anything once the source is closed.
• Add a source location if you might need to verify the claim later.
• Rewrite a useful observation as a stand-alone idea and explain its limits.
• Link it from the index or an existing note, giving the relationship a reason.

Do not turn every captured sentence into a permanent file. A useful note should change an explanation, support a question, or challenge something already in the collection. That is the distinction between saving material and building the reusable understanding described in what an AI second brain is. When an idea changes active work, fenbs keeps its source reference with the project context so the next assistant can see why it matters.

How can an assistant use selected notes responsibly?

Choose a few relevant notes and provide their text through an approved method in the AI app you use. A local file path is a locator for your computer; it does not give a remote assistant access. Include source locations and mark the difference between a verified claim and an open research question.

Ask for a specific output, such as an outline whose claims each identify a supporting note. Check those references before accepting the draft. When a person chooses the project direction, preserve that choice in fenbs project context and Decisions and rules so later sessions do not treat every exploratory idea as an instruction.

How to do this with fenbs

1. Create a free account and add the project that will use the research.
2. Save selected references in Links and listings. For local notes, include a readable title and location rather than assuming the assistant can open an Org link.
3. Write an AI context note containing the reviewed conclusion. Record the person’s choice in Decisions and rules, and add a task for any missing evidence.
4. Connect a supported AI app through Integrations. Ask it to read the context before starting and save progress with the next step before it stops.

fenbs is free for one person, with no credit card. It does not import or edit your Org collection. If you only need a private linked notebook, Emacs may already cover the whole job; fenbs is useful when conclusions need to survive a change of assistant or working session.

Test the handoff with one small writing task. Save which notes were checked, which interpretation the person accepted, and what remains uncertain. The next session should recover that distinction from the record, which is the practical purpose of portable AI memory.