DreamLake

Memos

Memos were previously called Notes. Existing /notes URLs, API fields, saved references, and document IDs remain compatible.

Read Markdown authoring, Embeds and query arguments, Panels, and Linked memo items for focused guides. The Memos API design specifies the unreleased shared-interface target with tabbed CLI, TypeScript, Python and model-tool examples. Its proposed methods and guarantees are not a claim of installed-client or server support. The detailed guides and CLI/API reference are on the pages below. Whole Project and owned resources transfer includes Artifact/Env with CLI 0.64.0+ or SDK 0.31.0+ and the matching backend; CLI 0.63.0 / SDK 0.30.0 support the Memo-only manifest. Standalone Memo transfer across namespaces remains unsupported. Dated release notes below describe their original verification scope.

Release status — October 9, 2026: the serving API includes the verified saved-version catalog readers, attachment compatibility readers, transactional attachment sharing, atomic attachment move/trash, and enabled immutable attachment uploads. The verified API release now also includes atomic attachment copy and named-version catalog publication by default. Durable attachment purge remains disabled. Strict runtime verification and read-only metadata/header checks do not establish production attachment-copy, saved-version-write or user acceptance. That October 9 verification did not enable a transfer adapter or establish continuous Memo-read availability.

Attachment journal release — October 10, 2026: the known-byte text/copy publication journal and admitted-only cancellation are enabled in the strictly verified API release 5d64f024. Its running image and digest were verified; selected status checks returned anonymous 401 and authorized 404 with no-store. Those two read-only checks performed no attachment write, body read, RTC call or provider-failure recovery. CLI 0.48.2 public npm/native distribution and isolated Linux installations are verified; the other seven OS targets were byte-verified, not runtime-tested. Raw upload journaling, durable purge and transfer adapters were disabled in that release. Current whole-Project transfer support is documented separately below.

A memo is a collaborative Markdown document. This is how a script — or a coding agent working through bash — edits one while people have it open.

See Panels and agent control for artifact previews, pinned tabs, and programmable native layouts. The session-library button in the chat tab row opens an available terminal beside the memo, keeping the editor in place. Session permissions remain separate from memo permissions.

In live preview, an opening H1 with content below it is positioned above the viewport once, before interaction. Scrolling back to the title keeps it visible; typing, blur, and idle time do not automatically hide it again. Raw Markdown, title-only memos, and explicit search or section navigation retain their existing behavior. Formatting remains enabled while editing. Vim visual selections remain visible in both rich and raw views. Each connected browser session shares its cursor and selection, including other sessions of the same account. Clearing a selection updates it immediately; leaving editor focus removes its shared cursor and selection. Hidden tabs leave visible presence. Visible sessions renew presence every 30 seconds; peers expire after 90 seconds without renewal. Cursor labels size to their names, capped at 20 characters of display width with ellipsis. Remote text updates preserve the visible text position in the memo pane; a new scroll gesture, keystroke, or selection takes precedence over a pending viewport correction.

Use a collaborator avatar to navigate to its current cursor when the location is available. A cursor at the beginning of the memo shows a popup saying Cursor is at the start of the memo and leaves your view in place. An avatar without a current cursor shows a popup saying No location available. Other available cursor locations support the existing jump action.

History timeline previews return to the current working draft when the pointer leaves the timeline. An explicitly placed edit marker or selected change range keeps its historical view open; clicking a version label alone does not pin it.

Catalog person filters

Availability: These person filters are pending the matching app rollout. The corresponding backend support is included in this release.

The matching app and server add Everyone, Owned by me, Created by me, and Edited by me filters to the Memo, Project, and Artifact catalogs. Memos and Projects start at Owned by me; Artifacts starts at Everyone. Everyone includes the readable catalog entries in the selected scope; it does not grant access.

The selected person filter is a chip in the search bar. Click its × or press Backspace with the caret at the start of the search to remove it and return to Everyone. Text after the caret is preserved. With several chips, Backspace removes the chip nearest the input first. Person filters combine with the catalog's visibility or artifact-kind filters.

Ownership follows the current namespace owner; creation follows the original creator, including after a transfer. Edited by me uses recorded contributions, not edit permission or the last-updated timestamp. Edit attribution starts with the matching server and app release; older editing history and legacy artifact creators are not inferred. Browser Memo edits are recorded after a local text operation is acknowledged, not when another collaborator's edit arrives.

In this section

The Memos API section covers programmatic access: the Memos API design, reading, editing and search from the CLI, Memos v2 merge and exact patches, agent presence and HTML reads.

Install

bash
curl -fsSL https://dl.dreamlake.ai/install.sh | bash
dl login

Both read the same saved login. pip install dreamlake installs the Python SDK; install the standalone CLI using the CLI tab before running dl login. The Python package is not the supported CLI installer.

For coding agents

bash
dl init                          # once: pick your agent and scope
dl skill install dreamlake-memos

dl skill update then updates it. dl init chooses between your user directory and one project, and the dreamlake-cli skill that the Memos skill requires is installed with it. Without the CLI, download skills.tar.gz from the latest dreamlake-skills release and copy dreamlake-memos/ and dreamlake-cli/ into your agent's skills directory.

The skill's reference pages are fetched from this guide's published Markdown; its procedures are written in the dreamlake-skills repository. Correct a fact here first and a step there; see Skills.