Sturdier Panes, Safer Saves & a New Search Engine

Most of this release is invisible - but this time it's about something more immediate than infrastructure. We went looking for every place where Conception could lose your work, and closed them.

Nothing here adds a button. What it adds is confidence: that the pane you opened stays open, that the sentence you typed a second before closing the tab is still there when you come back, and that a note you moved into a folder stays in that folder.

Panes That Stay Put

The sliding columns are the core of how Conception works, so we rebuilt the model underneath them. Panes now have their own stable identity rather than being tied to whatever URL they happen to be showing, which fixes a family of bugs at the root instead of one at a time.

• Asking your first question no longer breaks the pane. Typing a question on a fresh chat and hitting enter could leave you staring at a 404 page while the answer generated invisibly behind it. That's fixed - the answer streams in where you asked it.
• Exiting full screen keeps your pane. Expanding a pane and collapsing it again used to drop you back with the pane gone. It now carries its expanded state through.
• Two tabs no longer fight. Panes are now tracked per browser tab, so opening a second tab doesn't overwrite the layout in your first. Your last layout still seeds a brand-new tab, then the two go their own way.
• Each pane scrolls on its own. Long documents scroll inside their own column instead of moving the whole row, and a sideways scroll still works even when your cursor is over a pane.

Saves That Actually Land

Conception saves in the background as you write. Two gaps in that mechanism could quietly cost you work, and both are now closed.

Closing a tab now saves instead of discarding. Both note edits and structure changes - moving a note into a folder, reordering your sidebar - were held briefly before being sent to the server. Close the tab inside that window and the change was gone. Hiding a tab or closing it now flushes whatever is pending, on its way out.

Your links stop disappearing. Opening a note on a second device could trigger the app to send an empty copy of that note's internal links back to the server, wiping the connections between your pages and leaving stray entries in its version history. The cycle is closed, and notes now load with their real links and text from the start.

Failures are visible now. When a structure change can't reach the server, Conception retries, and then tells you - with a banner and a retry button - instead of showing a spinner that finishes as if everything saved. If your files can't be loaded at all, you get an error and a way to try again rather than an empty sidebar.

New accounts land where they should. A routing bug meant every new user was sent to the chat page instead of the Getting Started note written for them. Fixed.

Version History, Corrected

Version history had a set of quiet inaccuracies, all of which we've fixed:

• Simply opening the history dialog used to create a version, stamped with the name of whoever opened it and bumping the note's version number. Looking at history no longer changes it.
• Restore is disabled while a save is in flight, so a restore can't be immediately overwritten by an autosave that was already on its way.
• Plan-based access is now judged by a version's age, and per version - previously the first entry on every page of history appeared unrestricted, whichever page you were on.
• When a restore isn't permitted on your plan, the message now says so instead of failing silently.

Databases That Stay in Their Lane

Editing a row is now strictly scoped to the database it belongs to. Previously a malformed or misrouted request could write over the contents of another note you own, and deleting a view could - through a miscounted safety check - remove the only view of a different database. Both paths are closed, and an operation that doesn't match anything now returns a clear error rather than reporting success it never performed.

Database rows also behave properly in search: opening a row from the command palette now takes you to the row, rather than to a broken chat page, and it shows the right icon while you're choosing. Optimistic row edits reconcile with the server correctly, and bulk operations have a sane upper limit.

A New Search Engine Underneath

Search in Conception has, until now, worked by downloading a copy of your whole workspace into your browser and searching it there. That was fine at a few dozen notes. It isn't at a few thousand.

We've replaced the engine. Search now runs in the database, over a single index that covers note titles, tags, page properties, note bodies and chat messages together - with fuzzy matching, so a near-miss or a typo still finds the page. It's built, tested, and live behind the scenes; the command palette switches over to it in the next release, and you should feel the difference most if you have a large workspace.

In the meantime, the palette itself got safer and steadier. Search results are now rendered as text under all circumstances, closing a flaw where a page containing markup - including content pasted in from the web by an AI - could execute it in the palette of anyone who searched for that page. Typing characters like ( no longer throws an error mid-search, and the search mode is now judged fresh on every keystroke rather than lagging a character behind.

One New Model

Kimi K3 from Moonshot AI joins the lineup, following the K2.6 addition in our last update. As always, it went through the evaluation suite before reaching the model picker.