reflect-open keeps notes as Markdown files, and its Rust workspace is ten crates wide
Open-source Reflect rewrite: A local-first AI agent-friendly Markdown note-taking app
At a glance
- What is it?
- team-reflect/reflect-open is a Mac and iPhone note app built around a plain folder of Markdown, shipped as a Tauri shell with a Rust CLI and a native browser capture host. The feature list is the least informative part of it. The release channel split, the two build systems that disagree about the tree, and the three numbered install steps are.
- Who is it for?
- Reflect fits a reader who wants notes that stay inspectable files on a Mac and accepts a beta Mac app, an iOS build that arrives through TestFlight, and a browser capture path whose native host is absent from the install list.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 13, 2026, and from our analysis. They are not legal advice.
Star history
- team-reflect/reflect-open1,621 ★ · +150
| Repository | 2026-09-11 | 2026-11-13 |
|---|---|---|
| team-reflect/reflect-open | 1.5k | 1.6k |
150 Stars in the last 63 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The layout block names nine directories and the Rust workspace has ten members
The layout block presents reflect-open as a pnpm and Turborepo monorepo and names nine directories: apps/desktop, apps/cli, apps/extension, apps/native-host, packages/core, packages/db, crates/index-schema, design-system, and docs. The Cargo workspace beside it has ten members. Four of those ten map onto the layout block: apps/cli, apps/desktop/src-tauri, apps/native-host, and crates/index-schema. Six do not appear in it. crates/graph-paths is a workspace member and a path dependency of the others, and plugins/ holds five crates: tauri-plugin-app-store, tauri-plugin-keyboard, tauri-plugin-mobile-haptics, tauri-plugin-recording, and tauri-plugin-web-auth. The repository root also carries fixtures/, plugins/, CLAUDE.md, AGENTS.md, .claude/, and .codex/, none of which the block mentions. The two views of the same tree therefore disagree about scope, and the Cargo workspace covers strictly more ground than the directory map that introduces it.
Stable and beta builds are served from two different release tags
The install section gives four download links. Stable builds resolve through `releases/latest/download`, and beta builds resolve through `releases/download/updater-beta`, so the two channels never read the same release feed. The asset names differ as well: stable uses Reflect_aarch64.dmg and Reflect_x86_64.dmg, while beta uses Reflect.Beta_aarch64.dmg and Reflect.Beta_x86_64.dmg, switching from underscores to dots between the channels. Each build is signed, notarized, and auto-updated from GitHub Releases. The published releases show how the channels relate to each other: v0.14.0-beta.3 on 2026-09-29 at 09:58:12Z, then v0.14.0 the same morning at 10:25:43Z, then v0.15.0-beta.1 on 2026-10-02 at 16:52:54Z. The newest artifact is a beta of a version whose final has not shipped, and it was published about nineteen minutes after the last push at 16:33:25Z. Only two CPU architectures are offered, both in DMG form, and no other format appears in the install section.
Markdown files on disk, a bundled SQLite build underneath
The graph layout is four folders on disk:
my-graph/
├── daily/2026-06-12.md # Daily notes, named by date
├── notes/some-title.md # Other notes, named from their titles
├── assets/ # Images and attachments
└── audio-memos/ # Audio recordings and transcriptsMarkdown files are named the source of truth, and search, backlinks, tags, and related notes sit on top of them. Underneath sits a bundled database. The Rust workspace pins rusqlite 0.40.2 with the bundled feature, rusqlite_migration 2.6.0, sqlite-vec 0.1.9, sha2 0.11.0, and tempfile 3.27.0. A comment above the member list explains why: one lockfile pins one SQLite everywhere, so the desktop writer and the CLI reader can never skew. The keyboard command for local search is ⌘K, covering notes, backlinks, and tags, and optional semantic search can be enabled locally, which is the part sqlite-vec serves. What is not written down is where the index file lives, what rebuilds it, and what happens if it is deleted. The Markdown side raises no such question, which leaves the database as the one part of the data model a reader has to infer rather than read.
Browser capture needs a native host, and the install list stops at the extension
Capture from Chrome is the third of three install items, after the Mac app and the TestFlight iOS beta. The extension id is ccabifmooehighoonjeiololjfofkhkd, and its stated surface is the current page, selected text, screenshots, and optional page text. Behind it sits a Rust crate the install list never mentions. apps/native-host is a Cargo workspace member and is named in the layout block as the browser capture helper. A browser extension cannot save screenshots and selected text from a web page on its own, so the helper is the bridge, and none of the three numbered install steps covers it. The development section widens the gap by describing `pnpm dev` as Vite only on http://localhost:1420, which is the frontend running without the native side. A reader who follows the install section exactly ends up holding a browser extension and no written way to attach the host it depends on.
pnpm lint is three tools, and the development block names one
The development section gives the root commands:
pnpm dev # Vite only, http://localhost:1420
pnpm typecheck # TypeScript
pnpm lint # oxlint
pnpm test # vitest; use --run path/to/test for one file
pnpm check # typecheck + lint
# Rust tests that compile the desktop crate need sidecars staged first
pnpm --filter @reflect/desktop sidecar
cargo test --workspaceThe comment beside `pnpm lint` says `oxlint`. The root package.json expands that single script into three: `oxfmt --check`, then `oxlint --max-warnings 0 apps packages`, then `eslint --cache --max-warnings 0`. The formatter is a separate gate that the comment never mentions, and oxlint is scoped to `apps packages` while eslint runs with no path at all, so the two linters cover different sets of files and one of them covers everything. `pnpm check` is `pnpm typecheck && pnpm lint`, which leaves vitest and `cargo test --workspace` outside the gate a reviewer would run first. The root `test` script is bare `vitest`, and the comment on it already concedes the watch mode problem by pointing at `--run path/to/test` for a single file. Two more details sit in the same file: `version` is `0.1.0` on a package marked `private` while the published builds are 0.15.0-beta.1, and `postinstall` runs `simple-git-hooks`, so a plain `pnpm install` writes git hooks into the clone.
A plugin API declared out of scope next to five plugin crates
The Status section says Windows, Android, and a plugin API are out of scope for now. The Cargo workspace lists five crates under plugins/: tauri-plugin-app-store, tauri-plugin-keyboard, tauri-plugin-mobile-haptics, tauri-plugin-recording, and tauri-plugin-web-auth, and the comment on the member list calls them first-party mobile plugins. The word plugin carries two meanings in this repository, and a reader who takes the Status sentence literally will expect plugins/ to be nearly empty. Two of the five attach to features the feature list does describe: recording is the audio memo path, and app-store is the auto-update channel that pulls builds from GitHub Releases. mobile-haptics only matters on the iOS companion. web-auth has no counterpart anywhere in the install, feature, or development sections. The same Status sentence also puts Windows out of scope while the root scripts keep `release:windows` wired to `pnpm --filter @reflect/desktop release:windows`, right beside `tauri:build:dev` and `tauri:build:beta`.
private: true is a line inside the file, and the AI keys are the user's
Ask your notes is bound to ⌘J and runs through OpenAI, Anthropic, Google, or OpenRouter keys the user provides, and answers cite the source notes they came from. The per-note opt-out is a field in the Markdown itself, `private: true`, which excludes a note's content from AI and other external services. Because it lives inside the file, the opt-out travels with the note into whatever sync is attached: the same graph can sit in an iCloud-synced folder such as `iCloud Drive/ReflectGraph`, or in a repository the user controls over any SSH git remote. The privacy statement is scoped to external calls and names a configured provider, a connected git remote, and a platform sync service as the three triggers. Two other features cross that boundary in a way a note-level flag cannot cover. Audio memos are transcribed through a configured transcription provider, and browser capture moves page text and screenshots into the app. The README points at docs/privacy.md for the full model and names no second opt-out.
Four agent instruction files, three CLI verbs, and no documented flags
The repository root carries four places where instructions for automated agents live: .claude/, .codex/, AGENTS.md, and CLAUDE.md. The feature list describes the CLI as being for scripts and agents and names three commands, `reflect today`, `reflect search`, and `reflect show`, then points at docs/cli.md for the rest. Those three verbs line up with the data layout. `reflect today` corresponds to the `daily/` folder whose files are named by date, `reflect search` corresponds to the local index the desktop app writes, and `reflect show` is the reader side of a graph that any Markdown editor can already open. The Cargo comment names apps/cli as the reflect CLI and casts it as the reader, paired against the desktop writer. What the install, feature, and development sections never give is a flag, an output format, or an exit code for any of the three verbs. apps/cli is a Rust crate, even though the layout block files it inside the pnpm monorepo tree.
Editorial conclusion
Reflect fits a reader who wants notes that stay inspectable files on a Mac and accepts a beta Mac app, an iOS build that arrives through TestFlight, and a browser capture path whose native host is absent from the install list. Before committing, check that the notes you already keep can be pointed at a graph, that the AI provider keys you supply are ones you are willing to have note text sent to, and that the beta release channel is the one you actually want, because the two channels move independently of each other.
Frequently asked questions
Does reflect-open require a Reflect account?
No. The app does not require a Reflect account. Notes live in a folder you choose, and optional services such as AI providers, transcription, iCloud, GitHub, or another git remote are connected directly by the user.
Which platforms does reflect-open ship builds for?
Mac builds are published as DMG files for Apple silicon (Reflect_aarch64.dmg) and Intel (Reflect_x86_64.dmg) on both the stable and beta channels, and the iOS build is distributed through TestFlight. Windows and Android are named out of scope.
Where does Reflect send note content when the AI features are on?
Ask your notes, bound to ⌘J, queries your notes through OpenAI, Anthropic, Google, or OpenRouter keys that you supply, and answers cite their source notes. A note marked private: true is excluded from AI and other external services.
What commands does the reflect CLI provide?
The feature list names three: reflect today, reflect search, and reflect show, described as available for scripts and agents. docs/cli.md is the reference for the full set, and no flags or output formats appear in the README.
What license does reflect-open use?
MIT. The README links the license from its final section and a LICENSE file sits at the repository root.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/team-reflect-reflect-open)Star history chart for your README
[](https://hysenlabs.com/projects/team-reflect-reflect-open)Was this useful?