Continuity for Windows v0.4.10

Continuity now runs on a clean Windows install with nothing else installed.

Earlier builds silently depended on the Microsoft Visual C++ Redistributable. Most machines already have it, so the app worked on developers' PCs but failed to start on a fresh Windows image with a "DLL not found" error (0xC0000135). This is what winget's automated install check hit on the 0.4.8 submission. The runtime is now built into the executable, so the only DLLs it loads ship with Windows.

No editor behaviour changes in this release.

The embeddable SDK is unaffected; its latest release is sdk-v0.2.40.

Install

winget install Continuity.Continuity (listing pending review), or download below.

• MSI - normal install with Start Menu entry, uninstall, upgrades, and file associations.
• Portable zip - continuity.exe plus data\; keeps all settings and data in the extracted folder.
• Standalone zip - just continuity.exe; uses normal Windows AppData locations.

Verify a download against SHA256SUMS.txt. These builds are unsigned, so SmartScreen will warn on first run.

Continuity for Windows v0.4.9

Indent guides now show the first level of indentation.

Previously a line indented once drew no guide at all. A guide marked where an enclosing parent's content started, and the body's own left edge was not counted as one - so a long run of singly-indented content looked exactly like unindented content once you had scrolled past its parent. The left edge is that content's parent, and it now gets a rule like every other level. A genuinely top-level line still draws nothing, so the guides stay a statement about structure rather than a document margin.

Indent guides also no longer break across a wrapped line. A soft-wrapped paragraph drew its guides only on its first visual row, so every long line punched a gap in the rules running down the page. Wrapped rows now carry the same guides as the row they continue.

Indent guides are off by default; turn them on from the command palette with view.toggle_indent_guides.

The embeddable SDK gets the same first-level fix in sdk-v0.2.37.

Install

winget install Continuity.Continuity, or download below.

• MSI - normal install with Start Menu entry, uninstall, upgrades, and file associations.
• Portable zip - continuity.exe plus data\; keeps all settings and data in the extracted folder.
• Standalone zip - just continuity.exe; uses normal Windows AppData locations.

Verify a download against SHA256SUMS.txt. These builds are unsigned, so SmartScreen will warn on first run.

Continuity SDK sdk-v0.2.40

Full Changelog: sdk-v0.2.39...sdk-v0.2.40

Continuity SDK sdk-v0.2.39

Full Changelog: sdk-v0.2.38...sdk-v0.2.39

Continuity SDK sdk-v0.2.37

indent-guides="on" now draws the first indent level. No public API change.

A guide marks where an enclosing parent's content starts, and the body's own left edge was not counted as one, so a line indented exactly once drew no rule at all. A page of singly-indented content therefore became indistinguishable from unindented content as soon as its parent scrolled off the top. The left edge is that content's top-level parent and now draws at offset 0 like every other level; a genuinely top-level line still draws nothing, so the guides stay a statement about structure rather than a document margin.

The offset-0 rule sits flush at the text origin rather than biased a few pixels left of it. A background is clipped to its painting area, so a negative gradient stop paints nothing, and the only way to move the rule left is padding or a border on the line - both shift the content edge and with it the tab-stop grid origin. Hosts wanting more room to the left of the guides should pad their own container.

indentGuides keeps its "on" | "off" shape and its "off" default, so a host that never enabled guides is unaffected.

The native desktop painter changed identically in v0.4.9, and additionally stopped breaking its guides across soft-wrapped rows. The browser projection never had that gap, because it paints a line's guides into that line's own background.

Registry publication status

This release is not on any registry. The hosted workflow's stage job succeeded and its bundle is attested, but all three publish jobs failed on trusted-publisher configuration that does not yet exist on the registry side:

• npm - E404 on PUT /@continuity-editor%2feditor; OIDC yielded no credential
• crates.io - No Trusted Publishing config found for repository jatoran/continuity
• PyPI - invalid-publisher: valid token, but no corresponding publisher

npm install @continuity-editor/editor@next still resolves 0.2.36. To use 0.2.37, install the tarball attached below:

gh release download sdk-v0.2.37 --repo jatoran/continuity --dir sdk-v0.2.37
npm install ./sdk-v0.2.37/continuity-editor-0.2.37.tgz

Verify the bundle against its manifest first with cargo xtask sdk-release-verify sdk-v0.2.37.

These assets were downloaded from workflow run 33269363528, independently verified against release-manifest.json, and checked with gh attestation verify. This release was created by hand because the workflow's github-release job is gated on all three registry jobs.

Hosted npm tarball SHA-256: ee5179539c1a0e2bf31007585a926da982d50b38e26fb3152a0f86e56973701a

---

Looking for the Windows desktop app instead? See Continuity for Windows v0.4.9.

Continuity for Windows v0.4.8

Continuity for Windows — the native Win32 markdown notes editor. Looking for the embeddable editor instead? See the sdk-v* prereleases.

This release rolls up everything since v0.4.2, which is versions 0.4.3 through 0.4.8. Most of it is vault reliability.

Vaults

• Autosave no longer wedges mid-session. A save that was briefly refused — a manual Ctrl+S racing the automatic save, or an external program (cloud sync, antivirus, backup) touching the file — could permanently stop autosave for that note with no visible prompt: the unsaved indicator stayed on and the file quietly stopped updating. Autosave now only pauses when the file genuinely still differs on disk (with the reload / keep mine / show diff banner) and resumes on its own once a transient conflict clears.
• Autosave no longer dies once a second window is open. Save confirmations were delivered on a channel shared by every window, so a second window could consume another window's save acknowledgement, leaving the first believing a save was still in progress and silently skipping all further autosaves for that note. Save results now go only to the window that requested them, and a watchdog clears any acknowledgement that is ever lost.
• The file on disk keeps up with what you typed. Closing a tab, closing the window, switching tabs or panes, or clicking away now exports every changed note under the vault, not just the ones already waiting on the debounce timer.
• Vaults remember their open tabs. Closing a vault and reopening it — via the launcher, a desktop shortcut, or --vault — restores the same open files, the focused tab, and each tab's scroll position. State lives portably beside the vault in .continuity/workspace.toml, so it travels with the folder.
• Closing a tab in an autosave vault no longer shows an "unsaved changes" prompt. Autosave owns the file, so closing just writes and closes. The prompt still appears for untitled buffers and for notes whose autosave is paused by an unresolved conflict.

Sidebar and tabs

• Middle-clicking a file in the sidebar opens it in a new tab, matching Ctrl+click.
• The sidebar highlights the file you are currently viewing. The highlight follows the focused tab and clears when the tab is not a file inside the open folder.
• Opening multiple selected documents from Explorer now creates one new window with every selected document in its own tab.
• Dropping a document onto an open window adds it as a tab in the pane under the drop point instead of opening another window.

Editing

• Markdown block toggles are scoped to the lines they rewrite. Marking one line no longer pulls the next one into the new block as lazy continuation text, and stripping a marker no longer drops the newly-plain line into the block above it. Where a rewrite would otherwise absorb an untouched neighbour, the toggle inserts a blank-line separator in the same edit and the same undo group.

Downloads

Asset	Use
continuity-0.4.8-setup.msi	Recommended. Installs under Program Files, supports in-place upgrades, Start Menu shortcut, file associations.
continuity-0.4.8-portable.zip	No install. Extract and run continuity.exe; all app data stays in that folder.
continuity-0.4.8-standalone.zip	Just continuity.exe; settings, themes, and notes use normal Windows AppData.
SHA256SUMS.txt	Hashes for the above.

Builds are unsigned, so Windows SmartScreen may warn until release signing is in place.

Full Changelog: v0.4.2...v0.4.8

Continuity SDK sdk-v0.2.34

Continuity SDK — the embeddable editor. This is not the Windows desktop application; for that, see the v* releases.

The SDK is a preview channel and ships as a prerelease. It versions independently of the desktop app.

What changed

0.2.34 fixes host-driven reveal navigation without changing the public API. revealRange(range, { align }) now waits for the Markdown projection, measures the actual rendered caret or range, and scrolls whichever element owns the viewport. nearest keeps a fitting target fully visible with rendered-row clearance; center centers it as closely as scroll bounds permit. The same projected navigation primitive backs setSelections(..., { reveal: true }).

Normal editing also follows the post-render projected caret, preventing typing from moving outside either the desktop textarea viewport or the coarse-pointer touch-shield viewport. Desktop textarea scrolling and coarse-pointer touch-shield scrolling now agree, including late matches within heavily wrapped source lines.

These operations change selection and viewport only — not text, revision, or undo history.

Artifacts

Registry publication is not active yet, so these assets are the distribution channel. npm install @continuity-editor/editor, cargo add continuity-engine, and pip install continuity-editor do not resolve.

gh release download sdk-v0.2.34 --repo jatoran/continuity --dir continuity-sdk
npm install ./continuity-sdk/continuity-editor-0.2.34.tgz

Asset	Use
continuity-editor-0.2.34.tgz	npm package: Web Component, WASM engine, TS facade, React/Svelte/Vue adapters
continuity-engine-0.2.34.crate	Rust engine
continuity-buffer-0.2.34.crate, continuity-text-0.2.34.crate	Rust engine dependencies
continuity-engine-c-0.2.34-windows-x86_64.zip	C ABI: DLL plus continuity_engine.h
continuity_editor-0.2.34-*.whl	Python wheel (abi3)
continuity-sdk-0.2.34.cdx.json	CycloneDX SBOM
release-manifest.json, SHA256SUMS.txt	Artifact inventory and hashes

All assets carry GitHub build provenance attestation. Verify a download with cargo xtask sdk-release-verify <dir>.

The authoritative npm tarball SHA-256 is 09b4aba1654df262551ef7ad7576dbf08d9ec3dd01483020d5cc673c18f23808.

Integration

Surfaces, APIs, supported targets, and version history: EMBEDDING.md.

Full Changelog: sdk-v0.2.33...sdk-v0.2.34

Continuity for Windows v0.4.2

External-change handling: reopening or reloading a file changed on disk now shows current content (silently if you have no unsaved edits, with a prompt if you do). Saving no longer silently overwrites a file changed on disk behind your back — you get a Reload / Keep mine / Show diff banner with clickable buttons and a real line-by-line diff. Reopening an already-open file focuses its existing tab instead of opening a duplicate window. Every theme now has its own distinct text-selection color and a subtler current-line highlight (all 17 themes).

Continuity for Windows v0.4.1

0.4.1

• Fixed the viewport jumping and warping while you type in large documents.
  The 0.4.0 fix for this was incomplete — on long files (especially with a
  big table above where you're typing) the view could still lurch around or
  snap your current line to the top of the screen. Typing on a line that's
  already on screen now keeps the view steady.

Continuity for Windows v0.4.0

0.4.0

• Fixed a frequent crash when pressing Ctrl+Z (undo), especially after
  pasting and typing — the editor no longer dies on undo, and a UI panic no
  longer takes down the whole app.
• Markdown lists are smarter: pressing Enter on a checkbox line continues a
  checkbox, ordered lists auto-renumber when you insert or reorder items, and
  Ctrl+R on a numbered list converts it to bullets.
• Ctrl+B (and italic/strikethrough/code) now removes the formatting when
  the caret is already inside it, instead of inserting empty markers.
• New Ctrl+Shift+R: toggle bullets on the selected lines and indent the
  continuation lines. (Reload keymap moved to Ctrl+K Ctrl+M.)
• New Ctrl+K Ctrl+S: strip leading and trailing whitespace.
• Shift+Backspace and Shift+Delete now delete instead of doing nothing.
• Tabs: titles now use the available width and shrink only when crowded, with
  <> scroll arrows (and Shift+mouse-wheel) when they overflow; the close
  button hides when tabs get small so you can't hit it by accident;
  double-clicking empty ribbon space opens a new tab; Ctrl+W on an unsaved
  untitled tab now warns (and notes the content stays recoverable); and each
  tab remembers its cursor and scroll position when you switch away and back.
• Clicking a rendered checkbox toggles it without moving the caret; Ctrl +
  double-click adds another word to a multi-selection.
• The current cursor line now has its own highlight, and the line you hover
  shows its number in the gutter.
• Fold markers in the gutter only appear on hover or where something is
  collapsed; indent guides, minimap click/drag, and outline-heading clicks now
  line up correctly; typing in large documents no longer makes the view jump;
  active vs inactive tabs are easier to tell apart in every theme.
• Paste: rich text / HTML copied from a browser is converted to Markdown, and
  pasted Markdown tables render correctly.
• Find & Replace: regex can now match across line breaks (use \n).
• The status bar no longer wraps; notifications dismiss on their own, sit below
  the tab bar, and no longer clip their text.
• Command palette: removed the "cycle theme" command; typing "theme" now
  surfaces "pick theme" first.
• Save dialog: defaults to Markdown and appends .md automatically, and
  pre-fills the file name from the tab's title (selected, so you can just type
  to replace it).