DreamLake

Markdown authoring

Write Markdown directly in a Memo. Live preview renders formatting while retaining the source for editing and collaboration. Use headings for structure, lists for steps, and color sparingly to emphasize a status or phrase.

Everyday formatting

markdown
# Project update

**Decision:** proceed with the pilot.

- Owner: Ada
- [ ] Confirm the schedule
- [x] Review the proposal

Read the [project brief](https://example.com/brief).
Use `status` for inline code.

Template variables

Write named placeholders directly in the note:

markdown
Write for {{audience}} about {{topic}}.
Use {{project.name}} as the heading.

The editor highlights these placeholders and preserves their Markdown source. Open the right sidebar, then choose Variables from Sidebar options to see each variable once, in order of first appearance. The list follows edits and the memo revision being displayed. It is read-only: the panel does not assign values or substitute text.

Names start with a letter or underscore and may contain letters, digits, underscores, periods and hyphens. Spaces around the name inside the braces are allowed. Code, escaped placeholders, links and images remain literal and do not add entries to the Variables panel.

Footnotes and reference entries

Use a named citation in the prose and a matching definition on its own line:

markdown
This claim has a source[^robotics]. Another claim uses the same source[^robotics].

[^robotics]: Reference text with a [source link](https://example.com/research).

[^background]: Background reading that is not cited yet.

The app renders citations in prose as linked superscripts. Reference entries use [1]: labels at the same size and baseline as their text, including a colon and a space before the entry content. They are not superscripts. The ^ belongs to the Markdown syntax and does not appear in rendered entry labels. The editor reveals the original syntax when editing it, and source mode always retains it.

Numbers follow first citation order, rather than the spelling of the source key. Uncited definitions receive numbers after cited definitions and remain visible in both the editor and read-only view, including any suggested edits inside them. An entry without a citation has no return link. A cited entry links back from its editor label; the reader shows separate return links. Inline citations navigate to their matching definition within the current memo preview.

A defined [^name] takes priority over placeholder syntax. A citation without a matching definition remains literal, as do escaped references and references inside code. Keep keys and canonical source unchanged when making a display-only correction; do not replace [^name] with its rendered number in saved Markdown.

LaTeX math

Use \( and \) for inline math, and \[ and \] for display math:

markdown
Inline \(x^2 + \frac{1}{2}\) stays in the paragraph.

\[
E = mc^2
\]

\{ is not a display-math delimiter. Math renders in the rich editor and read-only view while preserving its LaTeX source. Move into the expression to edit its source. Code spans and fenced code keep these delimiters literal.

Nested ordered lists

Write ordered lists with numeric Markdown markers (1. or 1)) and indent children beneath their parent:

markdown
1. First step
   1. First substep
      1. First detail
      2. Second detail
   2. Second substep
2. Next step

Rendered Memos preserve each numeric marker as written, including its number and . or ) delimiter. Nesting does not change the marker style. Each nested list is indented, with wrapped lines aligned beneath the item text. The editor retains the source markers too.

Inside an ordered list, a child may start at 2., 10), or another number; the editor and rendered Memos preserve the same nesting and marker. For example:

markdown
1. Parent
    2) Child
        10. Grandchild

Press Tab on an item to nest it under the preceding sibling, or Shift+Tab to move it back out. Tab leaves the first item at its current level when there is no preceding sibling; repeated Tab presses do not turn it into a code block. The shortcuts also work with the caret at the start of the item line.

Four spaces also work for a child beneath 1. Parent; the indentation must belong to a parent list item. At the top level, four leading spaces create an indented code block. In the editor, continuation lines keep their structural indentation when the cursor moves away; extra spaces within prose still collapse in live preview without changing the saved source.

Typed a., a), (a), i., ii., 一、, and (一) are plain text, not Markdown list markers. Chinese text is supported inside ordinary numeric or bullet lists. A numeric 1) marker displays as 1) in rendered Memos.

Color a phrase

Brackets hold the text; braces follow the brackets and hold named attributes:

markdown
:color[Needs review]{color="#b45309"}
:color[Ready]{color="green"}
:color[Blocked]{color="#ef4444"}

These are DreamLake color directives using the Markdown directive convention :name[content]{attribute="value"}. Standard Markdown has no text-color syntax. The :color directive changes the foreground text color. Use :highlight for a background tint; arbitrary CSS is not supported.

Use a visible word such as “Blocked” as well as color, and check readability in both light and dark themes. A fixed color stays the same when the theme changes.

Preview in light and dark themes

The same memo renders an inline phrase and a colored table status in both themes:

Light theme: red Important text above a table with a green Ready status.

Dark theme: the same red phrase and green table status on a dark background.

Captured from the deployed app using a sample read-only memo. Fixed colors do not adapt to the theme; choose a color with enough contrast in the theme you use. The sample uses :color[Important]{color="#ef4444"} and :color[Ready]{color="green"}.

Supported values and text

Color values must be double-quoted. Use 3, 4, 6 or 8 hexadecimal digits after # (the 4 and 8-digit forms include alpha), or one of these case-insensitive names: black, silver, gray, white, maroon, red, purple, fuchsia, green, lime, olive, yellow, navy, blue, teal, aqua, orange, rebeccapurple.

Content is plain text: nested Markdown, HTML and nested directives are not rendered. Escape brackets and backslashes with a backslash. Attribute-only syntax is also accepted:

markdown
:color[Review \[draft\]]{color="orange"}
:color{text="Ready" color="green"}

Place a directive at the beginning of a line or after whitespace or an opening parenthesis. Select the directive in the editor to reveal and edit its source. Invalid colors, missing text, duplicate attributes and unknown attributes remain literal. A backslash before the colon or a code span keeps the syntax visible. Directives inside Markdown links remain literal.

Highlight a phrase

markdown
:highlight[Review needed]
:highlight[Key finding]{color="#60a5fa"}
:highlight{text="Decision" color="orange"}

Highlights use a translucent background tint and inherit the surrounding text color in light and dark themes. They accept the same quoted color values, plain-text content and escaping rules as :color. Select the highlighted phrase to edit its original source. Omit color for yellow; an explicitly empty or invalid color remains literal. ==text== and raw HTML <mark> are not supported highlight syntax.

Add user="geyang" comment="Check the source" alongside color to attach plain-text metadata: :highlight[Key finding]{user="geyang" comment="Check the source"}. Use the inline/sidebar comments toggle: inline shows no annotation cards or hover popups. Sidebar mode shows compact metadata cards in the table-of-contents column, following passages visible in the current viewport. Click highlighted text in the editor or use the sidebar edit action to reveal its original source. Use canonical public handles, not display names or internal user IDs. Attribution is self-declared; legacy names remain unresolved. See Highlight metadata for escaping and revision-safe agent edits.

Highlight preview in both themes

Light theme: yellow, blue and orange highlights in the live editor and rendered Markdown.

Dark theme: the same highlights inherit readable light text.

Captured from the app's actual editor and Markdown renderer using scripts/highlight-preview.html (serve with pnpm exec vite --config scripts/highlight-preview.config.ts; add ?dark for dark mode).

Use color in tables

markdown
| Item | Status |
| --- | --- |
| Proposal | :color[Ready]{color="green"} |
| Schedule | :highlight[Needs review]{color="yellow"} |

Color and highlights render in Memos live preview, table cells and the app’s read-only Markdown views. Saved text, revision handling and collaborative edits retain the exact source. CLI/API HTML snapshots and external Markdown readers may show the directive literally; they do not automatically gain the app’s color renderer.

Link resources

Use :memo[id] to reference another Memo. Existing Markdown links remain supported:

markdown
:memo[6ab5aaeed3b4339ea2f4c162]
:artifact[namespace/artifact-id]

Both :memo and legacy :note forms remain readable, including named attributes and fragments. Prefer :memo[id] for new references; never rewrite saved content.

See Memos for resource attributes and API editing, and Linked memo items for extracting a list item into a Memo.

Chat directives

Regular Chat and the built-in agent share Memo's directive validators. Message source is stored unchanged. Typing : opens the insertion menu; typing more filters it. Arrow keys choose, Enter or click inserts, and Escape dismisses. Menu selection never sends a message. Complete the selected content slot before sending. :: offers standalone leaves and ::: offers row/column templates. Code spans, fenced code and URLs do not open this menu.

All 19 rich-token names below accept the existing inline form and a standalone block-leaf form with exactly two leading colons. Leaves must occupy their own line. Triple or longer fences belong only to row/col; other combinations remain literal. Invalid or incomplete directives do not activate resources.

NameContent and attributesContext and interaction
colorText; colorValidated CSS color, plain text content
highlightText; color, user, commentStyled text and review metadata
placeholderPrompt textDisplay placeholder; no input mutation
insert, deleteText; user, reason, commentDisplay a suggested change only
replaceOld text; with, user, reason, commentDisplay old/new text only
commentComment text; userDisplay comment; no implicit Memo write
memo / noteMemo ID; fragmentNew authoring uses :memo[id]; :note remains compatible
sessionnamespace/24-character-session-idOpen session; permissions checked by destination
artifactnamespace/id; fragment, embed, inline, width, height, zoom, borderPermission-checked metadata; open or inline frame
previewHTTPS URL; title and the same embed optionsSafe external preview; does not carry application credentials
asset-referenceAsset ID; captionPermission-checked asset metadata and download
bindrBindr IDResolve accessible Bindr and open its location
filefiles/pathNeeds explicit owning Memo and file-opening callback; context-free Chat disables it
dashboardnamespace/project/folderOpen the dashboard for that path
experimentnamespace/project/runOpen the specified experiment
projectnamespace/projectOpen project
foldernamespace/project/folderOpen folder
chatgpt-content-referenceImported citation indexUnresolved marker; does not invent a citation target
videoHTTPS URL or Memo files/path; required nonempty title, optional paired width/heightStandalone :video or ::video; attachment media needs its explicit owner
grid:::grid{columns=2}; 1–6 columns, default 2Equal-width cells wrap into rows; stack below 480px
row, colBalanced fences of three or more colonsRow container; grouped columns require a shorter fence than their row

Legacy brace-attribute rich tokens, #artifact:namespace/id, imported ChatGPT private-use citation markers and :contentReference[oaicite:…]{index=…} remain readable. Existing Memo #note:… references, placeholders, <Lead>, template variables and <Columns> are compatibility features, not new colon directives. Ordinary Markdown, math and footnotes retain their existing surface-specific behavior. New Chat menus generate :memo[id]; legacy :note remains readable.

markdown
::highlight[Needs review]{color="yellow"}
::artifact[namespace/artifact-id]{embed="4:3"}

::::row
:::col
First column heading

First column detail
:::
:::col
Second column
:::
::::

A Chat embedded next to a Memo does not borrow that Memo's attachments or editing authority. Resource menus search the explicit Chat/agent namespace; assets also need project context. Missing context and inaccessible resources remain explicit. Rendering a reference neither grants access nor executes a command. Review markup in a message never accepts or rejects edits in a document.

The built-in agent receives a compact capability hint and can retrieve this reference through dreamlake_web_read when available. It should use only known resource IDs, look up exact syntax when needed, and keep ordinary answers plain.

Lists, numbered checklists and grids

Use - item for bullets, 1. item for numbered steps, - [ ] item for checks, and 1. [ ] item for a numbered checklist. Use [x] for a completed check. Numbered checklist in the / menu inserts the combined form. The number stays visible when you check the item.

Consecutive items form a tight list. A blank line between items or between blocks within an item makes that list loose, with extra space between its items. Indent continuation paragraphs and child lists to the parent's text column (three spaces for 1. ; two for - ). Their text remains aligned, including under a checkbox. The last block has no extra trailing margin.

Collapse an item with its chevron to keep its first line. Expand it to recover its paragraphs and nested lists; sibling items and nested fold states are independent. Folding is a local view state and does not rewrite Markdown.

markdown
1. [x] Freeze the evaluation set.

   Keep the scene manifest and random seed with the report.
2. [ ] Review failures before approving the release.

   Separate collisions, timeouts and slow responses.
3. [ ] Record the rollout owner and rollback trigger.

A grid distributes cells into equal-width columns across as many rows as needed. Use Grid in /, or type :::grid. Omit the attribute for two columns; columns=1 through columns=6 are supported, including quoted values such as columns="3". The grid stacks into one column when its memo is narrower than 480px. Each top-level block is a cell; :::col groups several blocks into one cell, inside an outer fence with more colons. Rows, grids and grouped columns cannot be nested inside one another. As with rows, grids are top-level only; unsupported attributes or malformed/unclosed fences remain visible source.

Download the complete example memo and paste it into a disposable Memo to try folding and checkbox changes.

This fictional evaluation brief keeps the result, remaining work and rollback plan together; the numbers illustrate the format rather than a real benchmark.

markdown
::::grid{columns=2}
:::col
### Baseline

92% success over 500 held-out episodes; 84 ms median response.
:::
:::col
### Candidate

95% success on the same episodes; 89 ms median response.
:::
:::col
### Go criteria

1. [x] No training-scene overlap
2. [ ] Review collision clips
3. [ ] Meet the response budget
:::
:::col
### Rollback

Owner: release engineer. Restore the baseline if collisions increase or
latency exceeds the response budget in two consecutive windows.
:::
::::

Click the space around a grid's cells or move the caret onto it to edit its source. Images keep their captions and open in the memo image viewer. Markdown exports preserve the fences; other Markdown viewers may show them as text. The built-in agents can author these forms in Memos and Chat using the same syntax. Checkboxes in read-only output display status; they do not update a memo.