My files — how it works
My files shows the content of your own home the way a file explorer does. It is one of the two
apps that replaced everything that used to sit below the Apps grid of the home (owner, 2026-11-21:
"at bottom, just bring contents of user home as explorer type view (i.e. navigatable by namespace)",
"or let's also put this in an app, then we only have apps on start page. plus chat window."). The
other is Spaces. The home itself is now the Apps grid and the message box
(core Doc/Architecture/AppsHome).
The page
| Part | What it shows |
|---|---|
| Breadcrumb | My files › Projects › Q4 — every step but the last is a link back up. |
| Folders | The namespaces one level down that hold content of their own. Opening one shows that folder here, in the app. |
| In this folder | Everything at this level, as the platform catalog (MeshSearch): a hit opens the node, the search box narrows the level, + creates something right here. |
The folder being read is the page parameter ?path=, relative to your home:
/Explorer/Browse?path=Projects%2FQ4 is {you}/Projects/Q4.
Rules
- Your home only.
?path=is relative to your own home. A value that tries to leave it (..,., a backslash) or names an internal_satellite (_Settings,_Access, …) is not a folder: the page says so and links back to the home. Access is still decided by the mesh — every read runs as you — the confinement keeps the app saying what it is. ?path=cannot reshape a query. A segment with whitespace or a control character (a newline would add a union leg to the read), a quote, a|or a parenthesis is refused like...- Presentation mode (#1803). A folder marked for the presentation screen is not drawn in the folder list, and a marked folder opened directly shows not a folder while the screen is up; the contents catalog screens its own hits where it paints them.
- A folder is a child with a child. The folder list reads the level's direct children once
(main content, internal
_entries excluded, at most 200), then probes each of the first 100 for a visible child of its own with the platform's own probe (DefaultNodeNavigation.ChildProbeQuery, the one the side index uses). A wider level is still complete below: the contents catalog pages store-side. - The folder list never holds up the page. It is its own area: the breadcrumb and the contents paint at once, the folders join when their probes answer. A probe that faults is logged and reads as "no folder"; the child is still listed in the contents.
- Platform controls only — title, markdown links, stack and MeshSearch — so Blazor, the web client and the native app render the same page. Links are markdown links, the one link every client renders inside a page.
What it does not do
- It does not list other people's spaces or what was shared with you — that is Spaces.
- It does not move, rename or delete: a hit opens the node, where its own menu does that.
Tests
Explorer/FileExplorer → Tests runs every case on the mesh: the path confinement (home, ..,
satellites), the breadcrumb, folder selection and order, markdown escaping of names, the anchored
queries, both languages, and the rendered page.