BanyanSo4k downloadsA lightweight Memos entry for Obsidian: quick capture, daily context, monthly collection, and local-first control.
English | 简体中文
A local-first Memos entry for Obsidian: quick capture, Daily Note context, monthly Markdown collection, card review, and mobile-friendly input.
Knomo is a memo-first capture plugin for Obsidian. It helps you write down fragmented thoughts quickly while keeping the content inside your own Vault, in regular Markdown files that remain readable and editable outside the plugin.
Knomo is built around a simple idea:
Knomo does not try to replace Obsidian's files, folders, tags, links, backlinks, or Daily Notes. It provides a lighter capture layer on top of Obsidian's Markdown workflow.




Obsidian is excellent for long-term knowledge management, but many thoughts do not arrive as polished notes. They arrive as fragments: a sentence from reading, a meeting idea, a task, a screenshot, a link, a small decision, a feeling, or a half-formed connection.
If every fragment requires opening the right file, finding the right heading, choosing the right folder, and deciding the final structure, many of them never get written down.
Knomo gives those fragments a low-friction entry point:
Knomo treats the memo as the first capture unit. You can record first, then later connect, tag, search, reference, develop, or move content into larger notes.
Knomo's core workflow has two Markdown layers:
Daily Notes answer: What happened today?
Monthly Memos answer: What did I write down this month?
Memo content is stored in your Obsidian Vault. Knomo does not require an account, does not rely on an external server, and does not actively upload your notes.
Knomo tries to support and preserve common Obsidian / Markdown syntax, including tags, internal links, Markdown links, URLs, images, lists, task lists, block references, quotes, headings, and code blocks.
Knomo does not turn your Daily Notes into a private database. It writes memo-shaped Markdown and keeps the original content readable.
Knomo treats Obsidian mobile as a core use case, not as a smaller desktop window. The composer, keyboard behavior, touch targets, sidebar, search, and card browsing are optimized for mobile capture.
Write and save memos directly inside Knomo without opening a Markdown file first.
Good for:
Knomo depends on Obsidian's core Daily Notes plugin.
New memos are written under a configured heading in the Daily Note of the day. The default heading is:
## Memos
Example:
## Memos
- 18:30:12 I came up with a new product idea #idea
- 21:10:03 This paragraph from a book is worth revisiting #reading
You can configure the heading, insertion position, and time format in Knomo settings.
In addition to Daily Notes, Knomo automatically maintains monthly Memos Markdown files.
Default example:
# Knomo/Memos-2026-06.md
## [[2026-06-21]]
- 09:20:10 A small product idea that should not be lost #idea
- 22:15:42 Review note: this needs to become a project brief later #review
## [[2026-06-20]]
- 16:42:03 Useful quote from reading #reading
Monthly files make it easier to browse a long memo stream without losing the daily source context.
Knomo displays memos as cards instead of forcing you to read the raw Markdown stream.
Cards are useful for:
Knomo supports multiple ways to narrow down your memo stream:
For large Vaults, Knomo can load recent content first and then hydrate the full memo set for filters and statistics that require all data.
Knomo recognizes tags and links written inside memos.
- 16:20:00 Improve the mobile composer spacing #knomo #interaction
- 19:05:00 This connects to [[Product Design]] and [[Mobile UX]]
- 20:10:00 Reference: https://obsidian.md
Knomo preserves the original Markdown instead of replacing it with a private format.
When a memo should respond to or build on another memo, Knomo can create a reference from the card action menu.
This is useful when you want to:
References use Obsidian-friendly links or block references so the connection remains meaningful outside Knomo.
Knomo supports lightweight image previews in memo cards.
Supported use cases include:
![[image.png]];;The goal is not to become an image manager. Knomo only provides compact previews so image-based memos remain easy to browse.
Knomo supports Markdown task lists inside memos.
Example:
- 09:30:00
- [ ] Send the project note
- [x] Check yesterday's meeting memo
Task status can be updated from the card view and synced back to the source Markdown content.
Knomo includes a record statistics view for understanding your memo habits and reviewing your writing rhythm.
It can show:
Statistics are designed for review and navigation, not for turning writing into a productivity scoreboard. You can use statistics to notice patterns and jump back into related memo cards.
Knomo includes lightweight review entry points such as random revisit and date-based review. They are designed to help old fragments meet the present again without requiring AI or external services.
A memo does not need to become useful immediately. Sometimes its value appears when you encounter it again in a different context.
Shuffle day brings back one complete day from at least seven days ago and displays that day's memos in chronological order. It favors varied dates and avoids immediately repeating recently shown days when possible.
Alongside the memo cards, Knomo summarizes the day's memo count, word count, tags, images, and links. Selection happens entirely from your local memo index, without AI or external services.
Add @YYYY-MM-DD to a memo to make it surface on a chosen date. You can type the marker directly or use the date picker in the composer, then review buoys in Today, Upcoming, and Past views.
The date marker remains part of the memo's Markdown content. Knomo only builds a local, removable, and rebuildable index for fast lookup; the index does not replace or rewrite the source memo in your Daily Note.
Knomo includes safer maintenance flows for day-to-day use:
Markdown remains the long-term trusted source. The plugin index is used to improve browsing, filtering, and synchronization.
Knomo has dedicated mobile interaction improvements:
Knomo's mobile goal is not just to open inside Obsidian mobile, but to make quick memo capture feel natural there.
Knomo uses Obsidian theme variables where possible and includes compatibility work for community themes such as Minimal.
If you use a different theme and see spacing, color, contrast, or mobile layout issues, feedback is welcome.
When Knomo is available in the Obsidian community plugin marketplace:
Knomo;main.jsmanifest.jsonstyles.css.obsidian/plugins/knomo/
Open Knomo from the command palette.Knomo requires Obsidian's core Daily Notes plugin.
Before using Knomo, make sure:
You can open Knomo by:
Open Knomo from the command palette;Write:
Today I started using Knomo to capture small thoughts #knomo
After saving, the memo appears in the card flow and is written to the corresponding Markdown files.
After writing for a while, try:
Knomo uses simple Markdown that stays readable outside the plugin.
- 18:30:12 This is a memo
- 18:30:12 First line
Second line
Third line
- 18:30:12 I read a useful point today #reading #product
- 18:30:12 This connects to [[Product Design]] and https://obsidian.md
- 18:30:12 Inspiration screenshot ![[image.png]]
- 09:30:00
- [ ] Follow up with the project owner
- [x] Check yesterday's memo
- 20:15:00
> A small note can become useful when it returns at the right time.
## [[2026-06-21]]
- 18:30:12 This is a memo
Knomo settings include:
Knomo's core principle is: your data belongs to you.
Knomo writes to Markdown files. To reduce risk:
Knomo's goal is not to hide Markdown. It is to make Markdown easier to capture, browse, and reuse.
Use Knomo as a quick input box inside Obsidian. Write first; organize later.
- 10:32:00 The important part is not the number of features, but the path users take to complete their goals. #reading #product
- 16:20:00 The mobile input box should feel like a calm panel above the keyboard. #knomo #interaction
- 09:30:00
- [ ] Draft the release note
- [ ] Review the mobile card layout
- 18:30:12 Layout reference for a compact card ![[card-layout-reference.png]] #design
Use tags, search, Random revisit, Record statistics, and references to bring old fragments back into current work.
Knomo is not:
Knomo is a local memo-first capture and review layer for Obsidian Markdown.
flomo is a standalone Memos product. Knomo is an Obsidian plugin.
Knomo is more suitable for users who want to keep fragmented notes in their own Vault while continuing to use Obsidian's tags, links, search, backlinks, Daily Notes, and Markdown workflow.
Thino is a mature Obsidian Memos plugin.
Knomo focuses more on:
If you need a mature and feature-rich Memos plugin, Thino may be a better fit. If you want a lightweight memo entry that stays close to Daily Notes and local Markdown, Knomo may fit your workflow.
No. Core memo content is written to Markdown files. The index improves the experience, but Markdown remains the long-term trusted source.
Yes. Knomo's main writing workflow is built around Obsidian's core Daily Notes plugin.
No. Knomo does not rely on external servers and does not actively upload your notes.
Yes. Mobile is one of Knomo's main optimization areas. Knomo includes a mobile composer, keyboard adaptation, mobile search, touch-friendly controls, safe-area handling, mobile sidebar behavior, and mobile-friendly card browsing.
The index may not have refreshed yet, or Markdown files may have been edited externally.
Try:
Yes. Knomo is designed to keep content readable in Markdown. If you edit files manually, refresh or rebuild the index if the card flow does not update as expected.
Choose verification by the change's scope and risk. Documentation-only work needs content, reference and diff checks. For a low-risk local change, run the relevant tests (multiple files may be passed together):
npm run test:file -- tests/<Name>.test.ts
npm test / npm run test:quiet run product behavior, data safety, sync acceptance and architecture/product contracts. npm run test:tooling runs the test runner, verification utilities and benchmark trace validator tests. npm run test:all runs both sets; CI, release checks and npm run verify use this full set. Tests remain in the same directory, new files default to the product set, and test:file can select files from either set. Synthetic trace tests do not replace real-device performance acceptance.
Persistence, migration, identity, data-safety and cross-service semantic changes require focused regression coverage followed by npm run test:quiet and npm run typecheck. Run npm run build when build artifacts need verification. Expand or repeat checks only for new changes, failures or unresolved risks; report unrun checks separately.
npm run verify is a comprehensive check, not a default handoff requirement: it includes type checking, all tests, the production build, i18n, diff whitespace, forbidden source patterns and trailing whitespace scans. Use it only when that full scope is required. Do not run lint unless requested. Coordinate test commands serially within one working tree because they share compiled output.
When device verification is in the current task, select the affected scenarios; the full device matrix belongs to the corresponding Stage/Beta/Release scope. The optional local mobile QA checklist is supporting guidance, not a test/build dependency.
Feedback is welcome, especially:
When reporting mobile issues, please include device model, OS version, Obsidian version, theme, and reproduction steps.
Starting with the Knomo 1.10.0 licensing change, Knomo's original material is licensed under GNU GPL version 3 only (GPL-3.0-only), with the Knomo Obsidian Host Additional Permission. Read LICENSING.md, the standard GPLv3 text, and the host additional permission together.
You may use, modify, and commercially distribute Knomo under these terms. Distribution of covered forks or extracted code, styles, components, and utilities must comply with applicable GPL obligations, including Corresponding Source and required notices. The host permission permits the necessary combination with independently obtained Obsidian; it does not waive GPL obligations for Knomo or authorize distribution of Obsidian. The software is provided without warranty to the extent permitted by law.
Historical MIT grants remain valid: you may continue to use material previously supplied under MIT on those terms. The historical MIT notice is preserved; it does not grant MIT permission for new contributions. Third-party material retains its own licenses and required notices. Your notes do not become GPL-covered merely by using Knomo.
The brand policy separates code licensing from official identity. Forks and commercial use are allowed under the software license; do not imply official endorsement. A project link or Buy me a coffee link is appreciated, not required. See CONTRIBUTING.md for the license of new contributions.
Development source is available in this repository. Each GPL binary distribution must provide a clearly identified way to obtain its complete Corresponding Source. The current licensing change does not yet implement release packaging or source delivery; see the remaining release requirements.