Lens opens a plain Markdown vault as notes and a graph. Wikilinks connect the notes; a force layout gives those connections a spatial surface. Files and history remain in the vault, so the application is a way to work with the material rather than its only home.
Notes before a platform
A note can carry frontmatter without surrendering it to a proprietary format. Saving records a Git commit. Search, folders, links and graph navigation are different views over the same files. Synchronization uses the vault's configured Git path.
A human garden and agent memory
The shell's Garden tab is a client of Lens. The application also has a controlled path for viewing agent memory, with amendment and credential boundaries distinct from ordinary edits to human notes. That distinction prevents a convenient editor from silently becoming an unrestricted memory writer.
Lens uses the system webview for its interface. Its bridge owns the conversation with the embedded page; the vault remains the data owner.
What remains open
- First-run, sync and amendment acceptance remain specific to the installed session.
- A graph view does not establish a shared household task or calendar system.