Writing and formatting
Native rich Markdown editor
Memos uses the native rich Markdown editor. The former CodeMirror fallback and browser experiment switch have been removed, including for browsers that saved the old fallback preference. Source mode uses Monaco and keeps the same shared Markdown document.
The native editor keeps canonical Markdown in the same collaborative RTC document. It supports rich Markdown presentation, formatting and insertion commands, comments and suggestions, references, folding and section navigation, Vim mode, audio controls, and collaborator cursors and selections. Memos keep their existing save, sync, version history, and recovery controls. Switching between rich presentation and raw Markdown does not change the memo source.
In rich presentation, native headings align with the surrounding prose: the heading marker and its separator whitespace do not add a visual indent. Paragraphs and lists use consistent spacing, and blank lines retain a visible editing position. These presentation rules preserve the original Markdown, including heading spaces and line breaks; raw Markdown keeps the source visible.
Stable prefixes and structural Backspace
The native rich editor keeps heading (#), list (-, 1.),
and quote (>) prefixes in a fixed left gutter. Activating a line keeps its body
text in the same position and preserves its wrapping. Nested lists keep a stable
indent at each level, and task items keep a stable checkbox slot.
With a collapsed caret at the start of visible text, Backspace converts an
#-style (ATX) heading to a paragraph; outdents a nested list or task item one level together
with its subtree; converts a root list or task item to a paragraph; or removes
one quote level. Within text or at a soft wrap, Backspace performs ordinary
character deletion. Undo restores the structural edit as one action. Raw
Markdown mode keeps literal deletion behavior. These changes apply only to the
native editor. Underlined (Setext) headings have no leading marker and
retain ordinary deletion behavior.
The native editor does not change the CLI, API, memo format, or permissions.
See Markdown authoring for named footnotes and LaTeX math.
Only inline citations are superscript; reference entries use normal-sized
[1]: labels on the text baseline, with a space before their content. Uncited
definitions remain visible, including suggestions, without broken return links.
Rendering never rewrites their source.
Use the DreamLake CLI for supported operations. Use Python or TypeScript APIs only when a required operation is unavailable through the CLI or the task explicitly requires SDK integration.
Links and Cmd+K
There are three ways to make a link in the rich editor:
- Paste a URL over selected text. Select the words and paste an
httporhttpsURL to get[words](url). This applies only when the selection is one line of plain text that isn't already a link, a URL or code. Any other paste is inserted as it is. - Type
/linkat the start of a line. The "/" menu's Link command inserts[link text](https://)with the URL selected, ready to type over. - Press Cmd+K (Ctrl+K on Windows and Linux). This inserts the same link around the selected text, with the URL placeholder selected.
In developer mode, Cmd+K means one thing everywhere: it opens the agent's ⌘K
window. This includes the memo editor, Vim mode and source mode. The memo's text
and selection stay as they were, so Cmd+Enter can still hand the selection to
the agent. Use paste or /link for links there. With developer mode off,
Cmd+K in the rich editor inserts a link as before. Source mode (Monaco) has no
link shortcut.
Also in developer mode, Cmd+Option+K (Ctrl+Alt+K on Windows and Linux) opens or closes the agent's ⌘K window from anywhere, with no exceptions: memo editors, source mode, any input, the agent's own input and browser terminals. A browser terminal otherwise keeps Cmd+K for its shell.
Placeholders
Use square brackets with whitespace immediately inside both brackets for text
that still needs to be filled in: [ xxxxx ],
[ owner name ], or [ launch date ]. Memos show these as blue highlighted inline
boxes with visible brackets and inner spacing: [ owner name ]. Hover over
a box to see placeholder. This works in the editor, table cells and
read-only view. Keep the brackets until you replace
the placeholder with its final value; the saved Markdown remains plain text. [text], [ text], and [text ]
are plain text, not placeholders. Empty brackets and whitespace-only content
are not placeholders.
References take precedence: Markdown links such as [guide](https://docs.dreamlake.ai/notes/),
reference links with a definition ([guide][docs] or [docs]), images, and
#note:<full-note-id> keep their reference behavior. Do not turn a reference
into a placeholder. Task markers ([ ] and [x]) and brackets inside code
are not placeholders. Escape the opening bracket (\[literal]) when you want
ordinary bracketed prose without a highlight.
Inline text color and highlights
Use a color directive to style an inline span in Memos previews, table cells, and the app’s rendered Markdown:
The content is plain text, including any Markdown markers. Escape brackets and
backslashes with a backslash in bracket content. Color values must be quoted:
3, 4, 6 or 8-digit hex colors, or black, silver, gray, white, maroon,
red, purple, fuchsia, green, lime, olive, yellow, navy, blue,
teal, aqua, orange or rebeccapurple. Unknown attributes and invalid colors
remain literal. Code, escaped directives and Markdown links remain literal too.
Selecting a directive in the editor reveals its original editable source;
saved Markdown is unchanged. :color changes the foreground; :highlight adds
a translucent background tint and keeps the surrounding text color. Omit the
color attribute to use yellow: :highlight[Important] or
:highlight{text="Important"}. Highlights
accept the same colors and plain-text content as color directives, including the
attribute-only form :highlight{text="Review needed" color="yellow"}.
Raw HTML and arbitrary CSS styles are not enabled.
See the Markdown authoring guide for formatting examples, color choices, tables and portability. CLI/API HTML snapshots currently keep color directives as source text.
Highlight metadata
Attach optional user and comment strings to a highlight:
Highlight annotations reuse the Memos inline/sidebar comments toggle. Inline mode shows no annotation cards or hover popups. Click highlighted text in the editor to reveal its editable source. Sidebar mode shows the handle and comment in compact cards in the table-of-contents column, with an edit action for writers. Cards follow the passages visible in the current viewport; a dense group scrolls inside the column. Narrow panes fall back to inline mode. Read-only sidebar cards show metadata without edit controls.
user is the canonical public user handle, such as geyang, not an internal
user ID or a display name. A single leading @ is accepted; the saved source is
not rewritten. Autocomplete inserts the canonical handle. Compact sidebar cards
show the handle. Legacy display-name values remain literal; the app never guesses
an account from a name. Attribution is self-declared and does not verify authorship
or grant access.
These are plain-text annotations on a highlight, not saved comment threads. Either field may be omitted; empty strings add no label. Existing plain highlights and colors keep their behavior. Select the directive in the editor to edit its source, including metadata. Metadata does not change the highlighted text or its source offsets, including in table cells and read-only app views.
Attribute values use JSON string escaping: \" for a quote, \\ for a
backslash and \n for a newline. HTML in metadata stays text. Unknown or duplicate
attributes and malformed quoting leave the whole directive literal. Use user,
not author; only color, user and comment are accepted secondary attributes.
Agents should first read the memo and retain its revision, then replace the exact
existing directive using --if-match and read it back.
For example, set NOTE_ID to the target memo ID and read its legacy ETag
(the replacement helper uses an ETag, not a v2 rtc: revision):
The existing notes create --text / --file commands also accept this syntax.
There is no dedicated highlight command: these are ordinary Markdown directives,
so matching text with notes replace is enough; no line numbers are needed.
Do not overwrite the whole memo to update one annotation. CLI/SDK storage already accepts this Markdown; no new client method or package version is required. CLI/API HTML snapshots retain rich directives as source text; the app renders them.
Web preview tags
Open a web page beside a Memo with a preview tag:
The URL is required; the title is optional. Tags work in the editor, tables and rendered Markdown. A normal click opens the built-in web preview panel beside the Memo. New targets open as tabs in the existing panel on the right; a right panel is created only when one is absent. Reopening the exact URL reuses its tab; different URL fragments retain separate preview tabs. Memo references follow the same rule. References opened from a side Memo add tabs in that same side panel, preserving the current Memo and its edits. Modified clicks keep ordinary browser link behavior. Only absolute HTTP(S) URLs without embedded credentials are accepted. Invalid syntax, duplicate or unknown attributes, unsafe schemes, code and escaped tags remain literal text. The saved source is unchanged by rendering.
A target must allow iframe embedding. Its own authentication and framing policy still apply. A temporary tunnel URL works only while its tunnel and server run. Browser static rendering retains an inert label before hydration; server CLI HTML snapshots currently leave preview directives as literal source with the existing source mapping. They do not load the target or create a panel.
Embeds
See Embeds and query arguments for responsive ratios, fixed
sizes, zoom, and the artifact/preview query API. Inline references stay in the text
flow; embed shows a content block; opening a reference shows its standalone
page in the preview/browser.
Artifact references (development preview)
Use :memo[id] for new Memo references. Existing Markdown links remain supported. Rich resources use
Markdown directive notation:
This follows the remark-directive convention,
a Markdown extension, not core CommonMark. Brackets hold primary content; braces
hold optional named attributes. Resource semantics are DreamLake-specific.
The namespace and artifact ID are both required because artifact IDs are scoped
to their owner; memo IDs resolve globally. Memo extraction and copy-reference
controls produce :memo[id] with the full resource ID. Insertion menus and
search/create flows use the same form. Copy URL continues returning a URL.
Memo headers show a clickable #… badge with the last six ID characters.
Artifact headers use a copy icon and copy the complete artifact reference,
including its owner namespace. Copying either reference does not create a share
link or change access.
Saved :note[<full-note-id>], #note:<full-note-id>, #artifact:geyang/pitch-deck,
:note{id="note-id"}, :artifact{namespace="geyang" id="pitch-deck"} and all
existing attribute-only rich components remain accepted. Do not bulk-rewrite
stored memos. Bare :note{ID} and :artifact{namespace/id} are invalid.
Secondary attributes currently include asset caption; values are double-quoted
JSON strings. Unknown/duplicate attributes, conflicting primary values, missing
fields and invalid IDs remain literal. Preserve exact source on reads and patches.
Placeholder content can escape brackets and backslashes with a backslash.
References grant no access and never change sharing. Missing/inaccessible resources
remain unavailable. Code, escapes and Markdown links stay literal. Imported ChatGPT
citation forms stay unresolved and retain their original source; never invent a
Memo or artifact to replace them. Existing [ owner name ] placeholders remain supported.
Click an artifact tag in a Memo or a project's Memo pane to open the reusable artifact panel to the right of that memo. The memo stays open. Clicking another reference to the same artifact reuses its panel, including references to a different slide. Panels retain the artifact viewer's preview, version, zoom and authorized sharing controls, and use the common draggable tabs and close controls. Control/Command-click keeps the ordinary artifact link behavior. The current implementation is a development preview until the companion UI is deployed.
The browser resolves titles through authorized artifact metadata. API HTML previews map each full token atomically and leave it unresolved, without fetching private metadata or embedding capability URLs. Artifact tags are implemented in the local development UI/API; production deployment is not yet verified. There is no artifact insertion picker yet: type/paste the complete token.
Fragment reference syntax (development preview)
Use :memo[id#overview] or :memo[id]{fragment="overview"} to retain a section target.
Existing Markdown links with URL fragments also remain supported.
Artifact directives can also retain a slide target:
Existing :note[id#overview] and :note[id]{fragment="overview"} remain
readable. Preserve those saved forms; use :memo for new references.
Specify the fragment only once. The parser separates it from the resource ID and
preserves the exact raw token, including percent encoding. Malformed fragments
remain literal. Static API HTML maps the complete reference atomically without
fetching metadata or creating capabilities.
Artifact references pass their fragment to the panel's local dreamlake.route.
For example, :artifact[geyang/landing-pages#slide-3] opens the landing-page copy
at stage 3. Selecting another slide updates the existing iframe without reloading
it or changing the surrounding Memo/project URL. Memo-section scrolling remains
separate from this artifact behavior. An existing artifact ID or an author-defined hash route must supply
the target; do not infer slide numbering or invent a section.