OpenKnowledge Beta now names ok-beta and ~/.ok-beta in its remaining setup, diagnostics, sign-in, embeddings and connection messages, and the bundled skills note the Beta command alongside Stable's.
OpenKnowledge Beta now names ok-beta, not ok, in its server-not-running and stuck-server hints, PATH setup copy, CLI help and the built-in terminal's Claude approval, and names ~/.ok-beta/secrets.yml for its search key.
Opening or closing the agents panel, and typing a long question in the Ask AI box, are now faster on large documents.
The desktop app and dev server run from source now use their own dev channel, with separate home folder, credentials, MCP entry and link scheme, so they no longer share or take over an installed app's state and projects.
The @ and / menus now open when typing with a Japanese input method: after an ideographic space, on full-width ＠ and ／, and once the input method commits the character.
Projects in one git repository whose folder names differ only in non-Latin letters, spaces or punctuation now keep separate version histories, and such skill files keep separate discarded-edit backups. A history two projects already shared stays with the project that created it; the other starts fresh.
The Linux packages are now named after the app they install: openknowledge for Stable on deb and rpm, and openknowledge-beta for Beta. Existing installs update in place and keep their terminal commands.
Links and heading anchors in Japanese, Hindi, Thai and other scripts whose marks change a letter keep those marks, so [[ガラス]] no longer opens a page named カラス. Links the editor saved earlier without the marks, such as #カラス for ## ガラス, need the marks restored.
Suggested links now find page mentions in Chinese, Japanese, Thai and other text written without spaces, and report the right position when the text contains characters such as İ.
Converting a page to a template no longer overwrites an existing template with the same generated name; it picks the next free name such as imported-template-2. Importing under an explicit name that is already taken is refused.
Template names, doc paths in agent chat, typed or pasted links with non-Latin domains, and agent names in thread titles now work in any script, and shortened titles and previews no longer cut an emoji or character in half.
Tags can now use any script, including Japanese, Chinese, Korean, Cyrillic and accented Latin, in front matter and inline #tags. Existing non-ASCII tags that were hidden now appear in the tag list. Letters written directly after an inline tag name, such as #wip日本語, now extend that tag.