Agentero
에이전트를 연결해 로컬 Vault에 연구 컨텍스트를 보관·Zotero에서 무결점 이동·읽고 이해·재활용
Notes는 오픈소스 데스크톱 에디터로, 파일만 지정하면 바로 텍스트와 마크다운을 작성할 수 있습니다
Notes is an open-source desktop editor for plain text and markdown. No vault, no index, no project to set up — point it at a file and start typing.
생산성TypeScript · JavaScriptGitHub @etiennedelange온라인운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
A desktop editor for .txt and .md files that opens instantly. No vault, no index, no project to set up.
저장소 README에서 가져옴
README 전체를 불러오는 중입니다.
README 전문 보기 ↗A desktop editor for .txt and .md files that opens instantly.
It never owns your files. There's no vault, no index database and no project to set up. Point it at a file or a folder and start typing. It sits between Notepad++ (fast, but no real Markdown) and Obsidian or VS Code (capable, but built around a workspace).
Download for Windows · Website · macOS and Linux builds are on the backlog.
.txt and .md files in place on disk. Saves are atomic, and it
warns you if a file changed on disk while it was open.Ctrl+P fuzzy quick-open across the open folder, other files in the
sidebar and recent files.| Nord | Noctis Lux | Noctis Hibernus | Quick-open |
|---|---|---|---|
Requires Node.js, pnpm (via
corepack enable), Rust and the
Tauri prerequisites for your
platform. The dev container in .devcontainer/ installs all of these.
| Command | Purpose |
|---|---|
pnpm install | Install dependencies |
pnpm tauri dev | Run the app with hot reload |
pnpm test | Front-end unit tests (Vitest, via Vite+) |
pnpm check | Format, lint and typecheck the front end (vp check) |
pnpm test:scripts | Tests for the release scripts |
cd src-tauri && cargo test --workspace | Rust tests, including notes-core |
pnpm tauri build | Build installers for the current platform (needs the updater key, or --config src-tauri/tauri.no-updater.conf.json) |
pnpm release [x.y.z] | Release (the next patch if no version): version PR, merge, tag, and the Windows build (see docs/RELEASING.md) |
pnpm mock:web | Run the front end in any browser against a mock backend, no Tauri needed |
pnpm screenshots | Regenerate the screenshots in docs/screenshots/ and the site |
The marketing site lives in site/ and has its own README.
The screenshots come from scripts/screenshots/. The script runs the front
end in headless Chromium and swaps the Rust backend for a mock that serves a
sample notes folder, so it works anywhere, not just on Windows. Run
pnpm exec playwright install chromium once before the first run.
pnpm mock:web serves the same front end and mock on the dev server
(http://localhost:1420, with hot reload) for working on the UI in a normal
browser. Saves go to memory and are lost on reload; native dialogs act as if
cancelled. pnpm mock:web --update also offers an update to the next patch
version, with the [Unreleased] CHANGELOG entries as its notes, for working
on the update button and dialog.
It's a Tauri 2 app. The window is a system webview
running a CodeMirror 6 editor (src/). It talks to
a small Rust backend over Tauri IPC.
The Rust side is split in two. src-tauri/core/ (notes-core) holds
everything that doesn't care how the UI is drawn: file access, atomic saves,
the folder walk and session persistence. src-tauri/src/ is the thin Tauri
shell around it. Keeping the core free of Tauri means a different front end
could replace the webview later without touching the file logic. Why the
webview stayed, for now, is in docs/HISTORY.md.
File access is consent-based. The backend only reads or writes paths you've
explicitly opened, or that sit under a folder you've opened. It refuses to
write anything but .txt and .md files. A strict CSP locks down the webview. Folder walks are capped
at 8,000 entries and 12 levels deep, and single files at 50 MB, so pointing it
at your home directory can't stall the app.
tauri build only builds for the platform it runs on. Shipped Windows
installers come from CI: pnpm release <x.y.z> merges a version PR and tags
it, and the tag runs .github/workflows/release.yml, which builds the
installer and publishes the GitHub release. Installed copies update
themselves from there. The steps, the updater and its signing key are in
docs/RELEASING.md; what changed in each version is
in CHANGELOG.md, and past releases with their
installers are on the
releases page.
PRODUCT.md: who it's for, and what it deliberately leaves
outdocs/HISTORY.md: dated log of decisions and the
reasons behind themdocs/ENHANCEMENTS.md: deferred ideasdocs/RELEASING.md: branches, releases and the
in-app updaterMIT © Etienne de Lange