Browse, create and organize
Browsing in the app
/<namespace>/profile?tab=notes and /<namespace>/notes reuse the same
Memos catalog. Your own namespace and organizations you belong to show
resources and actions allowed by your permissions. Signed-out visitors and
signed-in visitors to other namespaces see public resources only, without
creation or modification controls. Profile uses an avatar rail; the application
uses resource navigation for the namespace in the URL.
Your own Memos catalog retains Shared with me and recent organization memos. Private Memo share links require sign-in under the server's per-person grant rules.
Signed-out public and unlisted Memo links open an article reader without the application sidebar. Its heading comes from the article content, with author and listening controls below it. The full-width, translucent navigation offers sign-in and the author’s Memo catalog; it hides while scrolling down and returns when scrolling up. Author and publishing-namespace links appear in the reader. The guest agent entry offers sign-in to start a conversation.
Signed-in Memo details retain resource navigation. Details opened inside a project retain their return-to-project action. See Profiles and workspaces.
Pin memos to the top
Signed in, any memo you can read offers Pin to top among its row actions in the Memos catalog, in grid and list views, and in the list beside an open memo. Pinned memos come first. Within the pinned group and within the rest, the order you chose is kept, and search, the filter chips and Show archived still decide which memos appear. Unpin from top returns a memo to its place. In the list beside an open memo, a pinned memo shows a tilted pin in place of its memo icon.
Pins belong to you and follow the memo, including memos shared with you. They are not shared with anyone else, do not change the memo, and are not the left panel's saved items. You can pin up to 100 memos. A pinned memo you can no longer read stops appearing.
GET /me/memo-pins?namespace=<slug>returnsids, the pinned memos you can read now, andnotes, the pinned memos that namespace's catalog lists, so a pin on a page not yet loaded still shows first. Archived memos are included only withincludeArchived=true.PUT /me/memo-pins/:noteIdpins a memo you can read (404otherwise,409at the limit).DELETE /me/memo-pins/:noteIdunpins it. Repeating either is harmless.
Returning to a project folder
Project folder lists refresh when you return to the browser page, return from another app, or reveal a previously hidden list panel. Only visible folder lists refresh; there is no periodic directory polling while the page is hidden or while it remains visible. A return event refreshes the pages already loaded in that directory, keeping the search, sort, selection and reading position. A list already at the top stays at the top so new Memos are visible. If the top visible item was removed, the next surviving visible item anchors the position; if none survive, the scroll offset is kept as far as the remaining content allows. Failed return refreshes retain the existing rows and wait for another return event instead of retrying in the background. Changes made elsewhere while you remain on the page appear on its next return refresh or when you navigate back into the folder.
Archive memos and folders
The web controls and initial archive endpoints are deployed. See the
archive API contract for HTTP, client and tool interfaces.
Memos and folders have a separate nullable archivedAt field. Archiving does not
delete content, revoke access, remove project filings, or remove bindr membership.
Tags remain independent labels.
The memo toolbar and memo rows in catalogs, projects and bindrs offer Archive and Unarchive. Folder rows offer the same controls. Show archived includes archived items in the current list. Memo body previews span the row width below the title; the bindr timestamp sits with the metadata.
PATCH /namespaces/:slug/notes/:noteIdaccepts{"archived":true}or{"archived":false}, subject to the Memo's rename permission.PATCH /nodes/:idaccepts the same body for folders, using the existing project write permission. Send archive changes separately from edits.- Memo catalogs, project resource/bindr listings, and node children/search
exclude archived items by default. Pass
includeArchived=trueto include them. Filtering occurs before page counts and pagination. - An archived folder hides its subtree in those project listings without changing every child's own archive flag. A memo filed elsewhere keeps its independent state.
- A successful content, metadata or attachment edit restores an archived Memo. Editing a file or folder, or adding a child, restores its archived folder path. Memo edits restore the paths of its valid live project filings. Independently archived siblings and deleted items remain untouched.
- Opening a Memo or synchronizing unchanged content does not restore it. Content restoration occurs when the changed body is durably saved; a failed save leaves archive state intact.
Project and bindr associations
In New memo, choose private or public below the name; a memo is private unless you choose public, and the projects it is filed into never change that choice. Anyone can read a public memo, including signed-out visitors. Projects are optional: a memo can be filed under none, one or several. Below the visibility choice, the dialog lists the projects where you can create content, each with a checkbox, its name and its slug; check as many as you need. The list header shows how many are selected and offers Clear selection. In the search field, the arrow keys move through the list, Enter checks or unchecks a project, and Escape clears the search. From the memos list nothing is preselected; from a project's + new memo, that project is preselected and can be unchecked, in which case the memo opens on its own page. If you cannot create content in any project, the dialog says so and creates the memo without one.
Search matches names and slugs across every project you can read, not only the loaded pages, and lists those you can write to. The list loads more projects as you scroll. Selected projects come first, then suggestions that combine recent projects with successful memo creations in this browser: frequency decays with a 14-day half-life and recent use adds a boost. Checking a project does not move it; after a search is cleared, selections return to the top. History is scoped to the signed-in user and workspace, bounded to 128 projects and pruned after 180 days; cancelled or failed drafts do not train it.
The memos list and grid show the projects each memo is filed in, as links to
those projects: two per list row and one per grid card, with a +N button that
expands the rest in place. Only projects you can read are listed, so a memo with
no line may still be filed in projects you cannot see. A project from another
namespace is prefixed with that namespace, and same-named projects show their
slug. GET /namespaces/:slug/notes and GET /me/notes/shared return these as
projects: [{ id, slug, name, namespaceSlug }] on each row.
Adding a project or bindr keeps the current memo, URL, search and panes open. The single project/Bindr list panel supplies the scope for + bindr, even when the open memo belongs to another project in the same namespace. Without a project list, the memo's selected existing project supplies that scope.
A bindr can reference the memo's existing node in another project without mounting, moving or copying the memo into its own project. Its name is qualified by its owning project in the picker. The original project, folder and bindrs stay visible on one header line; current-scope bindrs follow them. Before the first current-scope tag is added, only the usual add control appears. Afterward, bindrs outside that scope gain a trailing turn arrow. +N opens excess tags in a separate menu while the header remains one line.
The caller needs access to the source node and Memo, plus write permission on the destination project. A reference does not grant access to the Memo. Lists, search and counts filter unreadable references before pagination. Cross-namespace references and references to other projects' plain files/folders are unsupported.
Pending operations disable duplicate submissions; errors remain inline. Adding a bindr never implicitly adds a project association. Adding a project remains a separate explicit action. Removing a bindr removes only its tag; removing a project retains the last-project guard. Open project and Open bindr navigate.
Matching passages
Searching the Memos catalog shows up to two distinct matching passages beneath each result title, with matching words highlighted. Hover or focus a passage to open a line-based popover, or use Preview matches from the keyboard. The popover shows multiple matching paragraphs with their line breaks and all query highlights. Repeated excerpts appear once with an occurrence count; expand them to choose the exact section and occurrence. Selecting a passage opens the memo in the existing pane and selects the matching occurrence when its current source still agrees with the result. Identical wording at different source positions remains distinct. A changed source reports Match changed and asks you to choose a current occurrence instead of using stale offsets. Title-only matches open the memo normally.
The current catalog query and list scroll survive opening a passage. Source-only matches that cannot be mapped safely to rendered Markdown remain visible in the explicit source excerpt; the interface does not guess a rendered position.
Resource subviews
Project file and folder details use native draggable sibling view tabs. Files offer Preview and Details; folders offer their available Files, README, Visualize and Episodes views. Each tab identifies its resource and subview. In the project view, selecting another resource reuses the existing resource tab slots instead of accumulating README/Files pairs for visited folders. Open memo tabs remain in place. Drag a tab to an edge to compare views side by side, or into a panel's center to group it. Closing a subview leaves its siblings open; Views reopens closed views. Tab switches retain mounted view state. Existing source-browser URL-owned view controls keep their navigation behavior. ML-Dash run inspectors use the same native tabs for Params and Log, while detail pages keep their existing separate log panel.
Create and list
The implementation of Shared with me resolves each Memo's live owner and uses its current namespace slug in the returned route. Cached namespace fields on an accepted-share record are historical provenance, not authorization or routing facts. The read does not repair or mutate those records. Current namespace members receive the Memo through their normal catalog; other active recipients retain their accepted access while sharing remains enabled. A public Memo stays readable after its share link is disabled, without retaining share-based editing permission. Deleted Memos, deleted owner namespaces and revoked acceptances are omitted. This reader change does not enable ownership transfer.
dl memos create "Design Doc"
dl memos create "Design Doc" --file draft.md
dl memos create "Design Doc" --text "# Design Doc"
dl memos create "Design Doc" --public # default is private
dl memos list
dl memos list --limit 20
dl memos list --shared # what others sent you
dl memos list --jsonimport dreamlake as dl
note = dl.create_memo(
"<namespace>", "Design Doc", text="# Design Doc\n",
)
note.id, note.namespace, note.etag
dl.list_notes("<namespace>")
dl.list_notes("<namespace>", limit=20, offset=20)
dl.shared_with_me()Titles may repeat — the slug takes a suffix — so keep note.id rather than
the name you passed.
Duplicate a memo
The memo's Duplicate action creates an independent private memo from the current visible editor text, including local edits not yet synchronized. It copies the attachment snapshot captured when the request is admitted, preserving exact bytes, logical paths and content types. The source's body, RTC room, sharing and history stay unchanged; the copy has a new room and no inherited share link or saved-version history.
The optimized server contract is
POST /namespaces/:slug/notes/:noteId/duplicate with
{name, text, projects?, bindrIds?}. It requires current namespace membership,
independent source-read authority, and write access to every requested project
and bindr. The text is literal Unicode, with at most 4 MiB of UTF-8 bytes; it is
not trimmed or normalized. Requested bindrs must belong to requested projects.
A successful 201 returns {note, rtc: {rtcDocId}, contentSha256, sizeBytes, files}.
contentSha256 is lowercase SHA-256 hex over the acknowledged UTF-8 text;
sizeBytes is its UTF-8 byte count. Each file receipt is
{path, etag, sizeBytes, contentType}, where etag is lowercase SHA-256 hex of
the copied bytes. The browser verifies the text receipt instead of rereading the
entire body. The server initializes only the new native room, verifies its text,
and copies attachments with two bounded get/hash/put workers; it does not send
attachment bytes through the browser or reset an existing room.
Concurrent attachment mutation between admission and publication is rejected.
Later source edits do not change the captured copy. A failed operation after
creation returns duplicate_incomplete and createdNoteId; the partial memo
and original room binding are retained for inspection. A timeout without a
receipt is also uncertain: inspect the created memos before trying again.
Neither server nor browser automatically replays an uncertain creation or deletes
its possible result. This endpoint does not add a CLI command or SDK method.
Memo summaries
A compatible Memos server exposes summary metadata. Published CLI 0.94.0 has
neither notes summary nor notes create --summary; Python 0.32.1 has no
summary helpers. TypeScript notes.create accepts an optional summary.
Check client and server capabilities separately.
A memo may have a short, optional summary for catalogs and quick context. The
summary is metadata separate from the collaborative body. Body edits and
revision checks leave it unchanged. Summaries can contain up to 4,000
characters; older memos without one return null.
The owner of the namespace or the Memo's creator who is still a current member
of that namespace can set or clear a summary, the same as for a title or
visibility change. Other users with body-edit access cannot change it. For the REST API, POST /namespaces/:slug/notes accepts an
optional summary; PATCH /namespaces/:slug/notes/:noteId accepts a string to
set it or null to clear it. Omitting the field from PATCH preserves the
existing summary. GET /notes/:noteId and catalog list responses return the
summary separately from the body. A summary update does not create a body
revision or change its content hash.
Python SDK 0.32.1 does not expose summary in create_note or provide
Note.summary, read_metadata, or update_summary helpers. Use the
REST metadata endpoints above for summaries; do not pass those unsupported
arguments to the Python SDK.
GraphQL's authorized Query.note(namespaceSlug:, id:) returns the nullable
Note.summary field alongside id, name, and visible project/Bindr
associations. It is a metadata-only read; body content is not returned. Use the
REST metadata PATCH to update the summary.
Link to a memo in the browser
Use the memo's full id in browser links:
Read namespaceSlug and id from dl memos create --json or
dl memos list --json. Do not substitute the title or human-readable
slug in this URL: the browser detail route expects the ID, even though the
CLI accepts slugs and titles. Use the returned owner namespace rather than
assuming your personal namespace. The ID is sometimes called the memo hash;
it is the note query parameter, not a # URL fragment.
In the development preview, the path controls the list pane independently of the active note:
/<namespace>/noteslists memos./<namespace>/projectslists projects;/projects/<project>opens a project./<namespace>/bindrslists Bindrs;/bindrs/<bindrId>opens a Bindr.
Append ?note=<full-note-id> to any of these paths to open a memo. Switching
list context keeps that memo open. The memo header's contextual list button
hides or restores the list pane. Older memo and project links redirect to these
routes. List search includes ordering; default status/category chips are omitted
from the compact panes. Project and Bindr member ordering is applied before
pagination so it covers the entire result set.
Inside another DreamLake Memo, use :memo[id] with the full resource ID. Existing Markdown
links and legacy :note directives remain readable. Copy URL still returns a URL. A browser link does not change visibility or grant access to a
private memo.
Project items expose a More actions (…) button on desktop hover or keyboard
focus. Click it, right-click an item, or use the existing touch long-press menu
and choose Copy URL. Panel titles have no copy action.
There is no separate folder-path copy action. Menu actions do not open the item.
The copied URL includes the namespace, project slug and folder path, so you can paste it into an AI request to identify the folder whose Memos you want read. It opens the selected item without carrying unrelated open Memos or panel layouts. Copying a URL does not grant access to the folder or its Memos.
Profile introduction
A namespace's public memo whose slug equals the namespace slug is shown at the top of its profile Overview, for personal and organization namespaces. To add one, create a memo titled with the namespace slug and make it public; to remove it, make it private or delete it. Memos are private by default and are never published automatically.
A memo's slug is derived from its title when the memo is created and does not change when the title changes, so retitling the introduction keeps it in place. If another memo already holds the slug, a new memo receives a numbered suffix and does not match; make the existing memo public instead. Renaming the namespace changes which slug matches.
The Overview shows the memo's body in a card, without its title or a link to the
memo. Unlike other memo views, which show HTML in a memo as text, it renders the
HTML subset a GitHub profile README uses: layout tables, images, links,
<details>/<summary> and text formatting such as <b>, <br> and <sub>,
with Markdown inside them. Only align, alt, colspan, height, href,
open, reversed, rowspan, src, start, title, valign and width
attributes are kept. Images load only from absolute http(s) URLs; links may
be http(s), mailto or relative, and open in a new tab. Everything else is
dropped, including scripts, event attributes, style, class, id, data-*,
SVG, MathML, forms and embedded frames. Attach memo files with Markdown image
syntax; an HTML <img> does not resolve files/ paths.
GET /namespaces/:slug/introduction returns the memo's metadata and a
short-lived presigned body URL, or note: null and content: null when the
namespace has no live public match. It ignores credentials: members and share
link holders receive the same public-only answer as anonymous readers, so a
private memo with the matching slug is never returned. Unknown or deleted
namespaces, and namespaces whose owning user or organization is deleted, return
404. Like other read-only content reads, the body is the last persisted
snapshot and can trail an open editing session by a few seconds.
Contributing session registration
Switching Memos preserves open session tabs and their panel placement. Opening another Memo's contributing session selects that session in the conversation panel and leaves the previous session open in the background. A session already open is focused instead of duplicated. Drag tabs between panels to arrange the workspace. A standalone Sessions list panel can be closed; closing a panel or tab does not terminate its session.
Viewing a Memo, selecting a session tab, switching Memos, and moving panels do not create contributing-session links. Automatic affiliation follows an acknowledged content write; explicit Link/Unlink actions remain available. Temporary presence is separate from a persistent session association.
CLI 0.82.0+ with the matching session API records native Codex/Claude provenance after an acknowledged content write. If a native UUID has no saved descriptor, metadata-only registration creates one without a host enrollment or terminal launch. A native UUID and a DreamLake saved session ID are different identifiers.
New sessions default to PUBLIC, including automatic registration and imports.
Existing private/team records keep their sharing. Set
DREAMLAKE_SESSION_VISIBILITY=private for a private new automatic registration,
or DREAMLAKE_SESSION_AFFILIATION=0 to disable affiliation. This policy applies
to sessions only; it does not change the Memo's visibility.
A metadata warning never invalidates an acknowledged Memo save. Retry only
session registration, linkage or explicit conversation upload; do not repeat the
Memo write. Use dl sessions register --provider codex --session <native-uuid> --cwd /original/directory --json, then sessions link <saved-id> --namespace <personal-namespace> --resource-namespace <note-namespace> --note <note-id>. A target-discovery 403 is separate from metadata registration and
must not be repaired by changing credentials or restarting a terminal.
Conversation upload stays explicit. Recognized credentials are redacted by both CLI and API, and historical archive reads are sanitized. Review custom secrets before selecting an export: pattern redaction is not exhaustive. Public readers can read public session metadata and saved conversations but cannot execute in the terminal or read private resources merely because they are linked.
Shared article author attribution
The optional-auth GET /notes/:noteId/content response includes note.createdBy
for a Memo the caller may read. Resolve this creator user ID against the public
GET /auth/namespaces directory's userId to link the author's personal profile;
the publishing note.namespaceSlug may belong to an organization. Private or
unavailable Memos retain their existing access checks and do not return author
metadata to an unauthorized reader.
Shared article narration
POST /notes/:noteId/narration returns a complete audio/mpeg recording for a
live public or unlisted Memo without requiring sign-in. Private, deleted and
missing Memos return 404, including when audio was previously cached. Access is
checked again before the recording is returned.
The server reads the saved article and sends its complete prose to ElevenLabs
using Eleven v4 (eleven_v4) and Chris — Charming, Down-to-Earth
(iP95p4xoKVk53GoZ742B), with natural stability (0.5). Browser-supplied
text and voice settings are ignored. Markdown and inline HTML become plain text;
code, media and citation markers are excluded. Narration is never silently
truncated. Up to 10,000 characters use one provider request; longer prose is
split within that limit, preferring paragraph, sentence or word boundaries, and
generated sequentially with the same voice and adjacent text context. Completed
request IDs connect up to three preceding sections for voice continuity. The server joins those MP3 sections into one
complete recording without re-encoding. Pause, resume and replay reuse the recording. The browser prepares the full recording before playback starts.
The public player's speed button cycles through 0.75×, 1×, 1.25×, 1.5×, 1.75× and 2× without changing the speaking pitch. Inline and sticky-header controls share the same playback and speed. The selected speed is saved in this browser and reused across public articles and reloads; changing it does not regenerate narration. If browser storage is unavailable, speed still works for the open page. If the pitch-preserving audio engine is unavailable, playback returns to 1× and displays an explanation. The reading-time estimate remains based on 1.25×; actual playback uses the selected speed.
The server caches audio by Memo, text sections, voice, model, voice settings and
output format; earlier Flash and v3 recordings are not reused. Responses
use Cache-Control: private, no-store; X-Speech-Cache identifies a cache hit or
miss. Simultaneous requests for the same recording share generation within a
server process. New generation is bounded to two concurrent requests and 60,000
characters per client IP per hour in each process; a busy request returns 429.
Cached recordings do not consume that generation budget.
Empty prose or prose exceeding 40,000 characters returns 422. Source inputs are also bounded to 1 MB of recorded size and 250,000 source characters; output is bounded to 16 MB across all sections and the joined recording, with a shared 180-second generation deadline. Missing provider API-key configuration returns 503, and provider or audio preparation failures return 502. The ElevenLabs API key remains on the server. This endpoint does not grant access to the separate signed-in Notes speech API or activate a live editing session.
The editor’s Read Aloud player also starts with v4 and Chris unless you have saved speaker or model preferences. Explicit favorites remain available. Its speed button saves a separate browser-local setting across reloads, from 0.75× through 2×. Closing the editor player releases its local passage audio and text-render caches; reopening can reuse the authorized server cache.