Planned Features

EtherPK is in alpha and changes often. Every other page in these docs describes what is built and working as of September 2026. Below is what is not, so that nothing has to be taken on trust.

On the roadmap

• Queries and saved views: blocks that list documents and tasks matching a query, in place.
• Kanban boards and habits over tasks.
• Dragging blocks with the mouse to reorder or move them. The keyboard moves them today (Outliner Blocks).
• Remembering folds between visits.
• D2 and Excalidraw diagrams, beside the Mermaid and KaTeX blocks that exist (Code Maths And Diagrams).
• Search by meaning in the browser, as a third group in Search. It exists today for an agent through the Headless Client (The Headless Client).
• Working with no network at all. An installed app still needs a connection to load; a synced graph then works through a dropped connection.
• Removing a player from a shared graph by its owner, with the key rotated so a removed player sees nothing new. Today a player can leave and an owner can transfer or delete (Sharing A Graph).
• Importing into an existing graph, merging by name. Today an import always creates a new graph (Importing From Logseq Obsidian Or EtherPK).
• Carrying protected documents through an import by asking for the source graph's passphrase. Today they arrive as ciphertext the new graph cannot open.
• Redirects for renamed pages on a published site, and links between publications.
• Formatting buttons on the phone's command bar.
• Changing your name or deleting your account from the Account page (Your EtherPK Account).

Extensions

EtherPK has no extensions yet. The design is written down early because it makes commitments about privacy and the safety of your notes, and those hold whatever ships.

Extensions are meant to add features to the app: new kinds of panel, support for new diagram or content types, extra commands and integrations, built by EtherPK and in time by others. The features EtherPK ships would be built on the same seams.

Extensions belong to you, not to a graph. You would install an extension into your own copy of the app, and it would follow your account across your devices. An extension is never stored inside a graph, so sharing a graph never shares extensions, opening a graph someone shared can never install or run code on your device, and an export stays plain markdown.

Trust is social, not a sandbox. An installed extension would run with full access to the app, so it could see content you have unlocked on screen, protected documents included. Extensions would be reviewed before distribution, nothing would install without your consent, and anything unreviewed would be marked as untrusted. Treat installing one as trusting its author with what you can see.

Publishing stays safe whatever you install. A published site never reveals a private or protected document, and the app enforces that after any extension has done its work. An extension can help render what you have chosen to make public; it can never widen what gets published.