Changelog

A fix release for scanned textbooks: a chapter number the scanner could not read no longer costs you every chapter after it, and a figure printed next to a paragraph no longer cuts that paragraph in two. Copying from a page or a chat answer now gives you Markdown.

Ingesting scanned PDFs

• A missed chapter number no longer swallows the rest of the book. When the scan loses the number in front of a chapter title (a lone 8 a tab away from De Wind is too little ink for the text detector), Wikai now reads it from the 8.1 heading below, and the chapter list recovers at the next numbered chapter even when two in a row were lost. A 24-chapter meteorology course used to come out as 7 chapters, with 8 to 24 folded into chapter 7. See Ingesting sources.
• A figure beside a paragraph stays beside it. A chart printed next to a block of text was dropped into the middle of that text, between its first and second line, and the text next to it was sometimes taken for the chart’s caption and set in italics. The figure now follows the paragraph it sits next to, and only a title above or below a figure is its caption.

Copying and pasting

• Copying from a page or a chat answer puts Markdown on the clipboard. Select text in a rendered page or in the chat sidebar and copy: what you paste elsewhere is Markdown — headings, lists, bold, links back to wiki pages — rather than flattened text. Rich destinations still get the formatted version.
• Pasting into a comment keeps its formatting. An answer copied from the chat and pasted into a comment card used to lose its bold, lists and headings; it arrives as Markdown now. See Comments and highlights.

Fixes

• The selection bar (Comment, Highlight, Copy link) stays over the words you selected near the edges of the page instead of sliding away.
• The search bar is back to its intended height, so its separators line up with the chat header’s.

Select a few words in a chapter and leave a note on them. The note lives in the panel beside the text, the words stay highlighted, and the chapter itself is never touched — comments are kept on a companion page of their own, which the agents can read and write like anything else in the wiki.

Comments and highlights

• Comment on a passage. Select words in a book chapter or any other ingested page and press Comment in the bar that appears. A card opens in the right-hand panel; it saves as you type, like the editor. Comments carry one of five marker colours, can be replied to, edited and deleted in place, and a long one can be promoted to a page of its own. See Comments and highlights.
• Highlights without a note. Highlight marks the words in a colour and nothing more. Click the stroke to change its colour, remove it, or turn it into a comment. A comment’s words wear a thin dashed underline; a plain highlight does not, so the two are told apart at a glance.
• The panel shows Connections or Comments. The info panel beside a page gained a switch; a page that has comments opens on them. Hovering a comment lights its words in the text and the other way round; clicking either opens the card and brings the words into view. A long column scrolls with the page instead of hiding its tail. N comments in the title bar hides the marks for that page when you want to read clean.
• Links to a paragraph, or to exactly these words. Hover a paragraph in a chapter and a small handle in the margin copies a link to it (⌘⇧C does the same for the paragraph you are in). Copy link on a selection copies a link that lands on those very words. Following a link to a comment opens the page with the comment in view; the companion page never shows itself.
• ⌘K inside a comment opens the same page picker the editor has, to link a page from a note.
• Agents see comments too. Four MCP tools — list_comments_for, add_comment, edit_comment, delete_comment — give an agent the reader’s annotations on a page and let it add, change or remove its own, under the same edit policy as any page. See MCP.

Pages and editing

• A wider page. The text column grew a little and keeps one width whether the side panel is open or closed; with it closed the text centres.
• Agent edits are cheaper. An agent’s page edit now refreshes only that page in the index instead of rescanning the wiki — which every edit used to pay for.
• A heading reference in a daily plan stops at its checklist instead of running to the end of the section.
• The search bar no longer shifts up a few pixels when its results open.

A fix for 0.7.0’s headline: the Comment bar only offered itself on chapters that came in from an EPUB. Chapters of a PDF — scanned or born-digital — are book chapters too, and now get it.

Fixes

• Comment, Highlight and Copy link appear on every book chapter, including the chapters of an ingested PDF. 0.7.0 keyed the bar on a flag only the EPUB importer writes, so a scanned textbook could not be commented on at all. See Comments and highlights.

A scanned textbook now comes out of the ingest looking like a book: chapters, headings at the right depth, lists, and only the figures as images. Around it, a smaller and steadier MCP surface for the agents, and a Wikai that explains itself when the machine runs out of memory.

Scanned and born-digital PDFs

• Figures are cropped out; the full-page scan is gone. A scanned page that is mostly text used to arrive as one big image followed by the recognised text. It now arrives as text with the figures and charts cut out and placed where they belong, like a born-digital page. A scan that is mostly picture keeps the full-page image, as before. Scanned tables are kept as crops rather than guessed at.
• Chapters without an outline. A PDF of twenty pages or more that has no bookmarks but numbered headings is split into chapters on those headings, so it reads the same way as a book with a proper table of contents.
• Structure that matches the print. Numbered headings land at the right depth, bold labels stay bold text instead of becoming headings, bullets and numbered items become lists, and the page summary is drawn from the first real prose rather than from the table of contents. See Ingesting sources.
• Word and other pandoc imports no longer carry raw HTML the editor could only show as source; those fragments are rewritten as Markdown.

Agents and MCP

• 28 tools instead of 45. The tool surface for agents was folded: one list_pages with filters, one get_page, one links, one search, and the write tools take an operation argument. The same work in fewer, clearer calls, and a much smaller tool description for the model to read.
• A tool set that fits the model. Settings → Agents lets you pick which tools each agent backend sees: everything, a core set of about eight for small local models, or reads only. Wikai picks a sensible default per backend and probes a local Ollama model for its context size. See Settings.
• A stable MCP endpoint. The port is chosen once on first launch and kept; the token stays the same until you press Generate new in Settings. An external client such as Claude Code or Codex is configured once. If the kept port is taken at launch, Wikai picks another, keeps that one, and tells you. See MCP.
• The sidebar says when Claude Code starts without Wikai’s tools, once, at the top of the turn, instead of the model finding out a call later.

Memory

• Wikai’s own footprint is bounded. The embedding model now embeds in small batches and unloads after ten idle minutes. A release build that could grow past 19 GB over two weeks now sits around 50 MB idle and under 600 MB under load.
• Settings → Diagnostics shows memory: Wikai’s own number, the system’s available memory and pressure level, and how much of Wikai the OS has compressed out. The log gets one line each time the footprint doubles.
• A slow ingest on a starved machine says so. When the system reports low memory while a document is being read, the ingest panel shows since which page, and clears the note when memory recovers. The slowness is the machine’s; Wikai now says so instead of looking hung.

Pages and editing

• Deleting a page or a source moves it to the OS trash, where it can be recovered, rather than removing it outright.
• A page containing a raw HTML fragment no longer blanks the editor.
• A multi-line task can be checked and unchecked again.
• The chat sidebar’s autosave no longer rescans the wiki on every save, which stopped the daily note’s embeds from blinking while an answer streamed.

A day of testing on Windows turned up a window that should never have been there, and a closer look at the chat sidebar turned up a control nobody needed. Both are gone, along with a few smaller things.

Windows

• No more terminal window per question. Every message to a CLI agent (Claude Code, Codex) opened a console window that stayed until the answer arrived. The same flash could appear at startup, when re-detecting an agent in Settings, and when importing a Word document. Helpers now run without a window.

Chat

• The Ground in selector is gone. It asked you to choose between the current page and the whole wiki — a choice the agent can make from your message. The whole wiki is now always the context, and with each message the agent is told which page you have open: “summarise this page” works without naming it, and a question about something else is no longer pulled towards the page on screen. See The chat sidebar.

Pages

• A backlink appears once. A page that cited several passages of the same chapter was listed once per citation under Inbound links. It is now listed once, however often it links. Agents asking for a page’s backlinks got the same duplicates, and no longer do.

Creating a wiki

• Title first; the slug follows. The dialog asks for a title and derives the folder name from it. Edit the slug and it stays yours; clear it and it follows the title again. A title is still optional. A long title gives a slug cut at a word boundary rather than an error about something you never typed.
• The wiki switcher shows a wiki’s full name as a tooltip, so two long names that start alike can be told apart.

Four days of using 0.5.0 on real daily notes, and the things that got in the way are fixed. Nothing new to learn; the rail, the link picker and the block anchors now do what they already looked like they did.

Daily notes

• The now-marker is a tick you can click. Every time on the rail could open the composer except the one most often wanted, the current minute. It now opens the composer at that exact minute.
• Fold and summarise are drawn as icons, sized to the kind chip beside the title, instead of small text glyphs that two enlargements had not made noticeable.
• A folded short entry shows its title only. The two-line preview used to appear on every folded entry, and on a body of one or two paragraphs it was as tall as the body it stood in for, so folding changed nothing you could see. The preview now appears only on entries long enough to need one.
• The “N h after the last” label sits where the gap is, just ahead of the stretch, rather than above a timed entry nested in the range before it.
• An entry starting on a meeting’s end minute is the next thing, not something inside the meeting.

Linking and editing

• A page you just created is offered by [[ and the search bar at once. Notes created, renamed or retitled from inside Wikai were invisible to the link picker and the main search bar until something else changed on disk, or until a restart; semantic search found them, which was the clue. Fixed.
• No stray ^id on the page. Emptying a paragraph in the editor left a block id standing alone, and the next save stamped a second one next to it; the first then showed as text. An id-only line is now recognised for what it is.

Books

• DRM-protected EPUBs are stored, not imported, and say so. Dropping a book locked with Adobe ADEPT, Apple FairPlay or Readium LCP now keeps the file under raw/ with an amber note naming the scheme. Wikai does not remove DRM; DRM-free and watermarked EPUBs import as before.

Under the hood

• The TLS library is updated for an advisory published this week (RUSTSEC-2026-0285). The bug could not be used to tamper with a connection, and no Wikai traffic was exposed, but the release gate is mechanical.

Drop an EPUB on a wiki and it becomes a book: an index page and one page per chapter, with the pictures. Until now that took a script on the command line. The same release closes a security review of the app’s own dependencies and its local endpoints, and fixes two document imports that failed for no good reason.

Books

• EPUB import is built in. Drop an .epub on a wiki — the same way you drop a PDF — and Wikai writes a book index and a chapter page for every section in the book’s own table of contents, so a volume that packs several books into one file becomes one page per book, and a section that straddles the publisher’s file breaks becomes one page. The title, authors, language, date, subjects and identifiers come from the book’s metadata.
• Illustrations at full size. Project Gutenberg books show a small copy of each picture that links to the big one. Wikai shows the big one and drops the link, which never had anywhere to go inside a wiki.
• Every paragraph keeps its anchor, so links into a chapter — from the book’s own contents page or from your notes — resolve after the import, exactly as they did for books imported with the old script.
• Files Wikai cannot read are stored, not “ingested”. A dropped file with no importer (a .pptx, say) used to show a green “done” row and create nothing. It now lands under raw/, the wiki log says stored, and the row is amber and says which file type is missing an importer.

Documents

• Word documents no longer “time out”. Any .docx, .odt, .rtf or LaTeX file whose converted text ran past a few pages was killed after 30 seconds with a misleading timeout; the conversion itself took under a second. Fixed, and the images in those documents now appear on the page instead of as broken links.
• PowerPoint is honestly unsupported for now. Wikai claimed .pptx and then failed on every one. It no longer claims it; a native reader is planned.

Security

The first release after a full security review of the app. What changed for you:

• The local MCP endpoint now requires a token. Wikai’s own chat agents get it automatically. If you pointed another MCP client at Wikai, copy the new client configuration from Settings → MCP server once; the old URL-only configuration will be refused.
• Web pages fetched into a wiki must be on the public internet. Addresses on your own machine or local network, and redirects to them, are refused.
• Dependencies refreshed. Every reported vulnerability in the app’s libraries — Rust and JavaScript — is resolved, the PDF engine is current, and the build now verifies the checksum of everything it downloads.

Daily notes and editing

• A daily note’s title reads like a date: Wednesday 9 September 2026 rather than the raw file stem, and the Daily notes group on a wiki’s overview stays in date order. Editing a daily note puts the cursor in the body, not the title.
• The Edit and Done buttons show their shortcut (⌘E / ⌘S on macOS, Ctrl+E / Ctrl+S elsewhere).

A bug-fix release. The first thing a new install shows is now an empty wiki list rather than a settings form, the installers show the actual license, and the daily note gets the corrections that came from living with 0.4.0 for two days.

First launch

Until now a fresh install opened on the full Settings form and asked you to pick a folder before anything existed — and then, if no agent was found, opened Settings again. Both are gone.

• Wikai picks the folder. On first launch it creates Documents/Wikai (or the app’s data folder if you have no Documents), saves that as your wikis folder, and shows the home screen with a single Create a new wiki card. You can move the folder later in Settings → Wikis folder; a move takes effect immediately.
• The chat sidebar opens on the first launch. If Wikai found Claude Code or Codex, you can start talking. If it found nothing, the sidebar says so and links to the agent settings — you are not taken there.
• The setup form still exists for one case: when the default folder cannot be created. It now says that, instead of describing folder layouts.

Installers

• The installer shows the End User License Agreement — the same text as wikai.app/eula — on the macOS disk image, the Windows setup and the .msi. It used to show a three-line copyright notice.

The daily note

• Plan a day from the calendar. Today and any future day are clickable, whether or not a note exists; clicking an empty one creates it and opens the timeline, so writing Thursday’s intent no longer requires starring a checklist onto Thursday first. The forward arrow reaches a year ahead. Past days without a note stay as they were.
• A timed entry from Quick Capture. Press Tab in the capture box to pick a kind — meeting, call, and the rest of the rail’s vocabulary — and Enter writes a timed section at the current minute, with the same → Today toast. Plain captures are unchanged; ↑/↓ still pick the wiki.
• Click an entry’s time to edit it. The composer reopens on that entry with its start, end, kind and title filled in. Enter saves and leaves you reading; Shift+Enter saves and opens the editor on the entry. Changing only the title leaves the rest of the entry byte-for-byte alone.
• Back-to-back meetings. The stretch right under a 09:30–11:00 meeting now opens at 11:00, not 11:05, so the next one can start the minute the last one ended.
• Links in an entry title render on the rail instead of showing as bracketed source.

Follow-ups

• Starring a daily note’s captures puts the whole list on today’s plan. A daily note’s captures are a list nothing introduces, and the mirror used to pick up only the first item.
• A starred checklist is now addressed by its page title, so the reference survives edits to the first item.

Wikai has always been bring-your-own-agent. This release makes that literal: six agents to choose from, the model picked beside the chat, and a daily note that understands time.

Six agents

Until now the chat sidebar spoke to Claude Code or, failing that, the Anthropic API. It now speaks to six, and every one of them reaches the same wiki tools with the same guarantees — a page a protected policy says to review is queued for your approval whichever agent proposed the edit.

• Codex — if you have a ChatGPT subscription, Wikai runs the Codex CLI you already have, the way it runs Claude Code. No key to manage; sign in once with codex login.
• OpenRouter — one key, hundreds of models. Wikai lists the ones that can call tools and leaves the rest out.
• llama.cpp and vLLM — a model you run yourself, on this machine or one you own. Point Wikai at the server and the wiki answers with the network off. Settings says, in one sentence, where your pages are going, because that depends on the address you typed — and it warns you when a server on the open internet has no key.
• Claude Code and the Anthropic API, as before.

Each agent has its own tab under Settings → Agents, with its brand mark, what it needs from you, and a status line. The three least-exercised carry a small beta tag. A Grok tab is there too, marked coming soon, so you can see where it will go.

See the chat sidebar and privacy & data for what leaves your machine with each.

The model, beside the chat

• Pick the model where you chat. A dropdown next to the agent picker lists what that agent offers — Codex reports its catalog, OpenRouter and the local servers are asked for theirs, Claude Code takes an alias like sonnet or opus. Leave it on Default and the agent picks, which is the one choice guaranteed to be inside your plan. Wikai remembers your model per agent.
• Reasoning effort for Codex, from the ladder each model actually supports — a wrong value would cost you a failed turn, so you can only pick a right one.
• “Last used” as your default agent. New chats open on whichever agent you used last, across all your wikis.
• A reopened chat goes back to the agent it ran on, which it did not do before — a Codex chat reopened with the picker on Claude Code sent its next turn to the wrong agent.

Research is something you start

An agent that decides, on its own, to open a research project rewrites a chat’s purpose and puts a file in your wiki. It can now only propose one: you get a banner, and nothing is created until you accept. Asked a plain question, an agent answers it.

The daily note understands time

• Today is a timeline. Captures sit at the minute you made them on a vertical rail; hand-written prose sits between. Click an hour and it opens in place with a composer in the gap, so a note at 14:20 lands at 14:20.
• Intent and Reflection — a section at the top of the day for what you mean to do, and one at the bottom for what happened.
• A capture can become a section: promote a one-liner into a heading with a body when it turns out to be a meeting, not a remark.
• Long entries fold, and a quiet stretch of the day folds into a wave rather than a wall of empty hours.
• Summarise an entry. Ask the agent for a summary of a long entry; it is offered beside the entry, grounded in your wiki, and written only if you take it.
• Capture while the day is open in the editor — the capture lands where it belongs without fighting your unsaved text.

Follow-ups on today’s plan

• Star a checklist onto today. A star in any checklist’s header puts that list under today’s Intent — as a reference, not a copy. Tick a box there and the source page is updated; the follow-up stays the follow-up.
• Plan a week by starring the days you mean to work on something, from a small calendar in the same button.
• Done items are struck through, not hidden, from one definition of done, so the plan and the source agree.
• Take a checklist off the plan from the day itself.

Elsewhere

• The connections panel sets its floor from your wiki, so it stops showing the least-related pages as if they were related.
• Block embeds render as references in the editor, with a chip that shows the label rather than the block id.
• Codex conversations continue past the first turn. The first build could not resume a Codex thread; fixed before release, and the fix keeps the sandbox on for resumed turns.
• Creating a research document no longer cuts off the agent mid-sentence, and pressing Stop no longer reports an error.
• The Anthropic API backend can now use concept search.

Fixes: a failed Codex turn reports the actual reason instead of “exited with status 1”; the chat header’s dropdowns keep their width when you switch agents; and the settings page no longer allows Automatic daily-note enrichment on any metered agent, while allowing it on a local model, which is free.

A wiki is only as good as what it can read and what it can find. This release widens both: Wikai now ingests documents it used to give up on — scans, multi-column layouts, tables, mathematics, footnotes — and search now points at the passage that answers you, not just the page it lives on.

Documents Wikai could not read before

• Scanned PDFs are recognised, page by page. A PDF with no text layer used to ingest as a placeholder. It now goes through OCR, so a photographed book or a scanned report becomes searchable text like any other source. OCR runs only on the pages that need it, so a born-digital report with scanned appendices pays for the appendices alone — and you get a time estimate before it starts. See ingesting sources.
• Every page records whether it was OCR’d, and with which engine, in its metadata — so you can tell a faithful extraction from a best-effort one.
• Multi-column pages read in the right order instead of being stitched across the column break. Reading order for scanned pages is reconstructed from the page layout rather than guessed from coordinates.
• Tables become Markdown tables. Where a grid genuinely cannot be reconstructed, the table is captured as an image instead of collapsing into a column of loose numbers.
• Mathematics survives. Display equations become LaTeX, inline maths stays inline, and formulas are recognised on scanned pages too — so an equation is something you can read and search rather than a run of broken glyphs.
• Footnotes become real footnotes — proper references in the text with their definitions preserved, instead of being spliced into the middle of the paragraph that referenced them.
• Figures drawn as vectors are captured, links inside a PDF are carried into the Markdown, headings are told apart from emphasised body text, and numbers survive extraction intact.
• Ingesting two documents at once no longer hangs.

Search that finds the passage

• A page is findable by any part of it. Long pages used to be represented by their opening alone, so an answer buried on page 40 of a chapter was effectively invisible. Pages are now indexed in sections, and a search hit carries the passage that actually matched.
• Quotation marks mean phrase search — and only then. Ordinary queries now reach the keyword index properly instead of being sent as one long phrase that matched nothing.
• Snippets are long enough to answer with. The previous cap cut answers in half, so the agent fetched whole pages to recover text it had already been shown.
• The connections panel stays out of your way: relatedness has a higher floor, an edit re-embeds only what changed, and the indexing work has moved off the path you type on.

Keyboard

• A shortcut registry and a cheat sheet — press ⌘/ to see every binding, labelled for your platform.
• The bindings that were missing: ⌘K search, ⌘L chat, ⌘E editor, ⌘N new note, ⌘S save and leave edit mode, ⌘, settings, and tab switching. Shortcuts now work while you are typing, which ⌘, in particular did not.
• Arrow keys walk the search results, Enter says what it will do, and Esc steps back out before clearing. Search returns 50 results, shows ten, and scrolls the rest.

Daily notes

• A calendar for browsing daily notes, so a long-running log stays navigable by date.
• One kind of to-do. A quick capture marked as a to-do is now a real checkbox in the note, so it shows up on the Follow-ups page alongside every other - [ ] you have written — instead of being a label that went nowhere. Add one with ⌘⏎, or by starting the capture with [].
• Quick Capture picks its wiki from the composer, closes when the capture lands, and no longer pauses on the way.

Elsewhere

• Editing no longer corrupts maths or footnotes. The visual editor round-trips $…$ and GFM footnotes intact; opening edit mode without changing anything no longer rewrites the page.
• A new note takes its filename from its title.
• person is a first-class page type, and you can change a page’s type from the metadata block.
• The MCP port can be pinned, so an external client’s configuration survives a restart. See MCP.
• The window reopens at the size you closed it.

Fixes: an empty page no longer leaves a wiki permanently “indexing”; the embedding cache survives a rescan; saving a page costs one page of indexing rather than the whole wiki; the block-id sweep no longer skips chapters; a follow-up group of one no longer hides behind its heading; “Open page” builds a URL that matches a route; and every scrollable pane uses the app’s thin scrollbar.

A note on the models. Recognising scanned pages and their formulas takes sizeable models, so rather than putting them in the installer Wikai fetches them once, the first time you ingest something that needs them. Wikai stays about the size it was, and you only pay for the download if you actually ingest a scan. Nothing is sent anywhere — recognition runs on your own machine, offline, like the search index always has.

A wiki you keep for years is a wiki you keep rearranging. This release makes rearranging safe — and makes linking something you do while typing, rather than something you go and look up.

• Move, rename and retype pages. Drag a page to a new folder, give it a better filename, or change what kind of page it is — every link pointing at it is rewritten in the same operation, including block references and image embeds. Available in the app and to agents over MCP.
• A page’s type no longer follows its folder. A concept can live under pages/notes/ and stay a concept. New pages inherit the type of where you made them, and the breadcrumb tells you what a page is instead of just saying “page”.
• Assets move with their page. Images a page owns follow it, instead of becoming orphans in the folder it left.
• [[ opens the page picker at the caret. Type two brackets, keep typing, pick a page — the link lands where you were, and the caret stays put. An exact title ranks first. If the page doesn’t exist yet, ⌘K can create it and link it in one step.
• A selection action bar. Select text and the things you can do with it come to you — including turning it into a link, from search results and the breadcrumb as well.

Agents got a sharper set of tools, too:

• replace_in_page for targeted edits to content that has no block id, update_frontmatter so page metadata can be maintained without rewriting the body, and write_wiki_file — the counterpart read_wiki_file had been missing.
• No filesystem tools. The rule that agents reach the wiki only through Wikai’s own tools is now enforced rather than merely stated.

Elsewhere:

• Daily notes group by year and month, so a long-running log stays navigable.
• Settings is organised under tabs, with a new About pane listing the open-source software Wikai is built from.
• The launch update-check is opt-out rather than opt-in.
• “Tidy now” cleans up a note’s layout, and no longer looks like a slower Edit button.
• + New Research asks what you want to research instead of picking a topic for you.

Supporter

Wikai is free, and stays that way. Supporter is for backing the project and for commercial use — a named-user licence covering every machine you own, with no device cap. See what it costs.

• Activate however suits you. Ask for an email link and click it, or paste your licence key. Either way the app verifies once and then works offline: the entitlement is signed, cached, and re-checked quietly in the background, so a flight or a bad hotel network is a non-event.
• A Supporter badge in the footer, and the licence state in Settings → Supporter, including which machines you’re signed in on and a way to sign out of one.
• Manage or cancel any time, from the app or from wikai.app/manage. Billing runs through Paddle, our merchant of record — Wikai never sees your card. Cancelling stops future charges and you keep Supporter until the end of the period you paid for.

Nothing behind the free tier moved: your wikis are Markdown on your own disk, readable and editable with or without a licence, now and if you ever stop.

Fixes: block ids survive entity-escaped spaces, display-math fences and id-only blocks instead of being stamped or printed into the text; the inline renderer no longer shows ^id in daily notes; long external links are capped with a middle ellipsis so near-identical URLs stay distinguishable; emphasis inside a link inherits the link colour; sticky layers pin to the title bar’s real height; dev builds no longer share a cache or log directory with an installed copy; and an agent prompt starting with - is no longer mistaken for a command-line flag.

You can now point at a single block — a paragraph, a heading, a list item — instead of a whole page, and the reference survives editing.

• Block references. Every block gets a durable, invisible id. Link to it with page.md#^a4a45a and Wikai scrolls to that block and flashes it. Reword, reorder, split or merge the block later and the link still resolves. How it works.
• Block embeds. Use image syntax — ![](page.md#^a4a45a) — and the block’s content renders inline where you put it, attributed back to the page it came from.
• Book chapters are Markdown. Ingested EPUB chapters are no longer verbatim HTML, so every paragraph in a book is now a citable target like any other block. Existing chapters were migrated in place; old intra-chapter links keep working.
• Block-level agent edits. The MCP endpoint gained tools to read, update, insert and delete a single block, so an agent can revise one paragraph without rewriting the page — and without breaking anything that cites it.
• A missing block id lint with a one-click fix, for blocks nothing can cite yet.

The editor got a working-over, too:

• The toolbar and the Done row stay pinned while you scroll.
• The title is a single editable heading — no more duplicate title card.
• Paste as Markdown: pasted **bold**, links and tables become real formatting instead of literal characters.
• A page info panel — metadata and connections — available in both read and edit mode, on one toggle.

Fixes: checkboxes stick reliably (on pages, daily notes, and in Follow-ups) instead of flickering back; short runs of loose checkboxes group under their section instead of scattering into separate follow-ups; editing a page no longer pins it as a tab; links and pasted tables are legible in dark mode, and the editor follows the app’s light/dark setting rather than the system one.

Windows installers are now signed with Azure Trusted Signing. SmartScreen may still prompt until the new certificate builds reputation — you can check the signature yourself under Properties → Digital Signatures. See verifying your download.

Known limitation: LaTeX math can still be mangled by repeated edit cycles on a page. It’s on the list.

Wikai is available for macOS (Apple Silicon), Windows, and Linux. Download it.

What’s in the first release:

• Ingest EPUB, PDF, DOCX, web links, and Markdown.
• Agent-maintained pages with cross-references, kept current as you add sources.
• Quick capture & daily notes — jot things down; the agent files them.
• Hybrid concept search and lint across your wiki.
• Chat sidebar grounded in your pages (bring your own Claude Code or Anthropic key).
• MCP endpoint for external agents.
• Local-first — everything is Markdown on your disk.

Installers are signed; updates are signature-checked and arrive automatically. On Windows, SmartScreen may warn until code-signing is fully in place — choose More info → Run anyway.