Your life in a single file
SEO Note

Version history

SEO Note exists in two lines. The current one is SEO Note 2.1 (Windows 10/11 64-bit, Linux x64 and Android). The classic one is SEO Note 1.3.34 (Win32, including 32-bit systems and Windows 7/8), finished and still downloadable. This page is the record of what was released and how updates work.

Current release

VersionReleasedFiles
SEO Note 2.1.229 October 2026 Windows installer 127 404 042 B · Linux AppImage 146 121 320 B · .deb 112 837 524 B · Android APK 10 893 833 B (signed)

SHA-256 for every file, including the classic build, is on the download page.

What 2.1.2 is: the current build of the Electron line, and the first Android build of the same interface. What came over from 2.0.0 unchanged: tree notes in one local file, Markdown with wikilinks, tags and per-note version history, password protection of the file and of single notes (Argon2id + AES-256-GCM), a web clipper with a clipboard watcher, AI features that talk to a model you connect (a local one or any OpenAI-compatible server), an MCP server for AI agents, optional sync through your git repository or WebDAV/S3, import of .seo, Evernote, Google Keep, TreePad and KeyNote files, interfaces in English, Russian, Turkish and German, portable mode. On the desktop 2.1.2 adds a demo vault (fifteen documents in English and Russian: ten notes and five diary days, so a fresh start has something real to show), a bank of diary questions that picks one for the day, keeps the streak and can be edited in its own manager, a gallery of nine ready note structures, export of a whole folder to Markdown with live links, the clipper's browser extension packed into the installer, and the vault library opening on its own after the splash until you tell it not to. It also drops the last network call 2.0.0 inherited: 2.0.0 asked GitHub at startup whether a newer release exists, 2.1 asks nothing at all. The packages are roughly a third smaller (Windows installer 127 404 042 bytes against 177 930 586 in 2.0.0). The phone build is not the desktop build: it carries the renderer, the note tree, the editor and search, while notes are stored as a folder of Markdown files in the app's sandbox; per-note history, passwords and encryption, sync, the web clipper and AI features answer there with an explicit refusal, and carrying a desktop .seonote file onto the phone is not finished. What 2.1.2 changed about the file: two tables are added by schema migration before your own note data is touched — the diary question bank (version 24) and the semantic index the search uses (version 25); the first start of a 2.1 build adds them to your file, nothing existing is rewritten, and we have not tested what an older build does with a file that a migration has touched.

What 2.1.2 adds over 2.1.1: an AI agent that works inside the program over your own notes — you ask it in a chat window, it reads notes through the same read-only tools an external agent uses, and anything it wants to write goes to the diary inbox queue for you to approve or reject first; SEO Note itself can now also act as an MCP host, so a third-party MCP server started over stdio shows up in a management screen and its tools answer from inside the app; the diary question bank became readable and writable for an agent through two MCP tools, and the diary got an AI hint of the day; the streak counter moved into the status bar. Three interface edges were sanded down: file dialogs reopen in the folder you last chose, Markdown preview takes the editor's place instead of opening a dialog, and one filter now serves both tool windows. On the phone the build finally writes to its own folder — a note you edit there is saved, and importing an .html file makes a Markdown note out of it instead of refusing — and a refusal now names the carrier it happened on instead of staying silent. The Android package keeps its release key, so the newer APK replaces the one installed on the phone.

How 2.0.0 was built

InternalDate (2026)What landed
0.13.028 Septemberreleased publicly as 2.0.0
0.12.022 SeptemberAI chat dock that answers about the whole vault
0.11.021 Septembertray menu rework, always-on-top
0.10.020 SeptemberSocratic review of your own notes, morning briefing
0.9.020 SeptemberMCP server — notes as agent memory
0.8.019 Septemberthe AI feature set: eleven commands over a selection or a note
0.7.019 SeptemberGoogle Keep and Apple Notes import, several vaults at once, Today tab, git backend
0.6.019 Septemberthe vault graph
0.5.017 Septemberdialog pass
0.4.017 Septemberweb clipper, WebDAV and S3 sync
0.3.017 SeptemberMarkdown, wikilinks, tags, history, Kanban, file association
0.2.015 Septemberincremental save and backups
0.1.0-beta.114 Septemberthe initial port

Read that table honestly. Those were internal builds, unsigned and unpublished; they are listed because "two weeks of work went into this" is the real answer to "is 2.0 a rushed release". The public line starts at 2.0.0 and will keep the same numbers from here.

What 2.1.2 still gets wrong

This page is where someone checks whether to use a version, so the defects belong here rather than in a changelog nobody opens. Both lists below were read out of the files this server hands out: the control block unpacked from the .deb, and Get-AuthenticodeSignature on the .exe. Two of the four rough edges the 2.0.0 packages carried are fixed in 2.1.2; two are not.

  • No code signature. The Windows installer reports NotSigned — measured with Get-AuthenticodeSignature on the file this server hands out, on 5 November 2026 for the 2.1.2 build current that day. SmartScreen asks you to confirm, and Smart App Control on some Windows 11 builds refuses to start it at all. Everything on this page assumes you get past that. This is now a decision rather than an oversight: buying a code-signing certificate costs money every year and buys nothing a private build cannot do without it, so we keep the installer unsigned and publish SHA-256 for every file instead. The Android APK is the exception: it is signed with our release key, so a newer APK replaces the old one instead of clashing with it.
  • Package metadata points Homepage at github.com/seonote/seonote-electron, an account that is not ours and is not registered. Ignore the field; downloads and releases live on this site. Treat it as a leftover of the build configuration rather than an address to visit.

Fixed in the 2.1.2 packages, measured the same way: the .deb now declares libasound2 | libasound2t64 in Depends, so a stripped desktop image no longer installs the program and exits at once; and its Description is no longer empty, so apt show seonote-electron prints a summary — see installing SEO Note on Linux. The 2.0.0 files were built before both fixes.

The classic line

VersionStatusFile
1.3.34final; still downloadable, nothing further addedSEONoteInstall.exe, 2 630 931 B (installs 8.7 MB)

We do not publish a version-by-version history for 1.x: there is no record of it we trust enough to put on a product page. Its data file is .seo, and SEO Note 2.1 imports it.

Update policy. No build replaces itself, and we are not going to add silent auto-update: the program works without network access, and an updater is a hole in that. To be straight about the 2.0.0 file that was offered before this one: it still carried an inherited update check that asked GitHub whether a newer release existed, once at startup and once a day. Nothing is published as our update feed, so the check found no version, downloaded no file and installed nothing, and offline behaviour was unchanged; the code is gone from the source 2.1.2 is built from, so the file offered now does not send it. New versions appear here on this site, with checksums. The Windows and Linux installers are not code-signed yet, so the first run of a fresh download shows a SmartScreen warning — that is a packaging gap, not a sign the file is tampered with, and the SHA-256 table is there for you to check. The Android APK is signed with our release key.

Compatibility. A .seonote file does not open in 1.3.34 — the older program does not know the format. Migration is one-way by design: keep the .seo file, keep the classic build installed if you need it, and read what the importer carries over before you rely on a moved file. The .seonote file is a SQLite database with nothing system-specific in it, which is why the same file is what the Windows and Linux builds both open; we have not published a cross-machine test of one file carried between the two. Android is the exception on purpose: that build keeps its notes as a folder of Markdown files in the app's sandbox, so it is not a viewer for a desktop .seonote file yet.

Download · Русская версия этой страницы · 2.0 vs 1.3.34 · Support

Mini FAQ

Is SEO Note 2.0 the first Electron release? It is the first one published on this site. The same line had thirteen internal builds before it, from 0.1.0-beta.1 on 14 September 2026 to 0.13.0, which is what 2.0.0 is called inside the source tree.

Why jump to 2.0 instead of continuing 1.x? The classic Win32 program reached 1.3.34 and stayed there. The rewrite is a different program with a different data file, so it starts its own numbering at 2.0 rather than pretending to be 1.3.35.

How do I get a new version? Download it here. We publish no update feed, and no build installs a new version without you — that is not going to change: a new release appears on the download page, and updating means fetching the installer again. The earlier 2.0.0 file still sent a startup update query left over in it, which found no feed and downloaded nothing; the 2.1.2 file offered now does not send it, and the paragraph on update policy below spells that out. Checksums are published next to the files so you can tell a fresh download from a damaged one.

Are releases signed? The Windows and Linux installers are not, and that is the rough edge we intend to fix; until then Windows SmartScreen warns on the first run of a build from this site, and the download page lists the SHA-256 of every file so you can verify what you got before running it. The Android APK is signed with our release key, so a newer APK replaces the old one instead of clashing with it.

What is new in 2.1 over 2.0.0? An Android build of the same interface; on the desktop, a demo vault of fifteen notes so a fresh start has something to show (ten notes and five diary days), a bank of diary questions that hands you one a day and keeps the streak, a gallery of nine ready note structures, export of a whole folder to Markdown with live links, the clipper browser extension packed into the installer, and no update check at all (2.0.0 still asked GitHub at startup, 2.1 asks nothing). The packages are roughly a third smaller. The .seonote data format is unchanged: a 2.0 file opens in 2.1, and 2.1 reads and writes the same file 2.0 did; the 2.1.2 build adds two tables to the file on first start — the question bank, schema version 24, and the semantic index the search uses, schema version 25. The Android app is not a third way to open that file — it is the same renderer over a folder of notes on the device, without passwords, sync or AI yet.

Are there release notes for the classic 1.3.34? No. 1.3.34 is the last build of a line maintained since before this site existed, and we do not have a version-by-version history for it we would be willing to publish. What we do state is that nothing more is being added to it.