Share a page by link
A document in LogiShell is a markdown file in your project, edited by the same editor as the code next to it. That is deliberate: your writing lives in git, with its history, and not in a second product.
It also means the text is on your machine. Sending someone a path is useless, and sending a copy in a message makes a second version of the truth an hour later. Publishing solves that: the page gets an address you can paste into a chat.
Make a link
Open the page, in Logbook or as a tab. In the line under the title there is Share. It offers two links:
- Create view link: anyone with the link reads the page.
- Create comment link: anyone with the link reads it and leaves a comment under it, after typing their name.
The link looks like app.logishell.com/p/<token> and is copied for you. It
opens without signing in and without a LogiShell account, in any browser. It
shows the page together with its sub pages: a list on the left, in the order
you gave them in the tree, and links between them stay inside the shared set.
A page can have several links at once, for example a view link for a channel and a comment link for one reviewer. Each one is revoked on its own.
What exactly is on that link
It depends on where the page lives.
- A page on a desk without a project is already kept in your LogiShell account, so the link shows it live: what you saved is what they see.
- A page in a project is a file on your machine, and your machine goes into a bag, falls asleep and loses wifi. So the link shows a copy of the page and its sub pages, taken when you made the link. The panel says the date, and Update the copy sends your edits.
Canvases, terminals and other live blocks inside the page are shown to the reader as a short note: they need LogiShell to be seen live.
Comments
Comments left on a comment link appear in the Share panel of the page, with the name the person typed and the page they commented on. A view link has no comment form and does not accept one.
Who can read it
Anyone with the link. The address is the only lock, so it is long and random, and the page asks search engines not to index it. Treat it the way you treat any link with contents: fine for a document you would show a colleague, wrong for a secret.
Revoke turns a link off at once. A revoked link answers exactly like a link
that never existed. Links made before November 2026 (/d/<id>) keep working
until you press Stop sharing on them.
Where this is not the right tool
If you want a page with an address you keep, on a shelf people can browse, that is the public docs site, and its pages are markdown in a repository built by a deploy. Publishing by link is for one document and one conversation.