Memos
Use dl memos (or dl memo). The previous notes and note commands remain aliases. Existing /notes URLs, --note flags, SDK methods, and JSON fields keep their compatibility names.
Memos are shared Markdown documents you can read and edit in DreamLake or from your terminal. Choose a guide for the task at hand.
Basics
- Create and find memos — login, search, create, and first read.
- Reading and changes — sections, passage search, and change history.
- Editing with patches — targeted edits that preserve concurrent work.
- Live collaboration — task identity, presence, and following edits.
- Saved versions — immutable checkpoints and retained history.
- Legacy commands — older ETag-based scripts.
Rich content
- Markdown and highlights — text color, references, and HTML snapshots.
- Videos — upload a clip and embed its player.
- Columns and rows — two-column blocks and repeated pairs.
- Attachments — upload, manage, and preview files.
- Suggested-edit redlines — propose document changes for review.
Management
- Sharing and visibility — links, access roles, and private/unlisted/public visibility.
- Project filing — create and inspect project affiliations.
- Ownership transfers — preview and transfer a standalone Memo.
- Archive memos and folders — hide inactive work and restore it on edit.
- Delete a memo — remove a whole Memo.
Cross-interface API design
The Memos API design is the detailed implementation target shared by the CLI, TypeScript, Python and model-facing tools. Its method-family pages cover reading, editing, collaboration and replay, resource lifecycle, moving and renaming, and stdin/stdout/stderr.
The redesigned examples are unreleased contracts, not installed-command
availability. Use this CLI site's command guides and installed --help for
current syntax. Publishing the design does not upgrade clients, deploy server
capabilities, or update the pinned agent skill.
Current commands already support canonical source, mapped reading views, original-revision patches, and presence/live following. The redesign changes some defaults and argument shapes; do not substitute them into existing scripts:
| Area | Current CLI | Implementation target |
|---|---|---|
| Read default | Canonical source with metadata | Source-mapped default; explicit exact-source export |
| Mapped inspection | read --view markdown or --view html | Shared mapped read contract with explicit scope and ranges |
| Line selection | Existing separate start/end flags and compatibility constraints | One --lines START:END pair |
| Namespace | --namespace in current Memos examples | Consistent --namespace / --ns source-context aliases |
| Create | Positional name required | Name and initial text optional |
| Watch | read --linger with current debounce/throttle behavior | Bounded watch, normalized events and durable net content catch-up |
| Append | Existing separator-LF behavior | Verbatim supplied text with no automatic separator |
| Move | Current filing/transfer workflows and flags | One move facade with separate destination fields |
A source revision, content hash, metadata version and watch continuation have different purposes. Keep original edit baselines and acknowledged receipts; never replay an uncertain mutation solely because a newer design offers a cleaner name for it. The family pages identify remaining implementation and protocol decisions explicitly.
Related resources
CLI 0.133.0+ with the companion resource-relationships API release lets a Memo record an
explicit association with an Artifact or Annotation, independently of references
in its body. Use dl resources link note MEMO_ID artifact ARTIFACT_CATALOG_ID
and read back dl resources relationships note MEMO_ID. See
resource relationships and history
for identity lookup, removal, related sessions, activity and SDK methods. A
relationship grants no access and does not change the Memo's content.