Panels and agent control
DreamLake views use the native UIKit panel surface: drag, dock, resize, tab and close work the same for memo editors, memo lists, artifact views and explicitly opened web previews.
Memo and artifact tabs share a 240px preferred width and 130px minimum width in compact layouts. Titles use an ellipsis when needed; the reference control stays after the title, before the close button. Memos retain their short hash labels and artifacts use a copy icon.
The UIKit layout controller owns destination addressing and the forkable starting-layout → command → result catalog. DreamLake supplies resource descriptors, view loaders and interaction policies. The TabbedContainer component presents those alternative scenarios in the docs.
Share the current view
The address carries the panel tree and its display state. After opening, closing, tabbing or resizing views, copy the current address to reopen that arrangement. It restores sidebar collapse and folds, list search/filter/order and selection, and note/list scroll positions. Folder and project location stay in the ordinary route. Changes settle for 250 ms, then the latest snapshot is encoded during idle time; scrolling does not compress or rerender on every event.

Two exact memo references, restored at 35/65 width. The route supplies the primary memo ID; auxiliary references retain full IDs. Repeated strings compress through references to earlier sequence segments. Artifact query strings and fragments travel with their references. Internal iframe state requires the artifact to represent it in that address; the host does not introspect iframe memory.
Sharing a view grants no additional access. Unavailable auxiliary memos leave empty panes or are omitted from a populated tab group, while the primary memo keeps its normal access flow. No catalogue lookup or fuzzy ID resolution is needed. The codec caps the escaped layout value at 32,000 characters and the decoded form at 64,000; these are application limits, not a universal browser URL guarantee. If a layout is unsupported or exceeds the cap, the last usable URL is retained. Existing version 5, DEFLATE and prototype layout links remain readable.
Artifact references
Clicking an artifact tag in a memo opens its artifact beside the source memo. The default request first activates an existing instance of that artifact. A fragment such as a slide or section navigates that same mounted view.
For a different artifact, the request chooses the latest preview destination associated with that source memo tab. It replaces an eligible unpinned preview. Pin the current tab to retain it; the next artifact then opens as another tab. Dragging a preview out preserves its named association and role, so subsequent requests can target the original destination, the last one, or a spatial match. The UI default is the last destination for that source instance.
Pinned tabs can still be moved or explicitly closed. Notes that are still syncing retain their disposal guard. A failed replacement or stale layout leaves the existing view intact. Ordinary web links keep browser navigation.
Memo and web-preview references
Memo tags and :preview[https://example.com/#section] open new targets as tabs
in the existing panel on the right, creating a right-hand panel only when one
is absent. Clicking an already-open target activates it. Different preview URL
fragments are separate tab targets. Opening either kind of reference from a
side Note adds a tab in that same side panel. Existing tabs stay mounted and
retain editor and preview state; these reference clicks do not replace content.
Sessions beside a memo
Memos and all artifact kinds can have multiple saved sessions linked to them. The session library offers All sessions and Linked to memo (or Linked to artifact). Use the row's Link or Unlink action to change affiliations. On an artifact page, Sessions in the header opens the same session panel beside the artifact. Opening or viewing a resource does not create a link. Links preserve exact saved-session IDs and remain separate from the tabs currently open in a panel.
Click a Codex or Claude row in Contributing sessions to open its terminal in the panel to the right. An uploaded conversation is not required. This action keeps terminal intent even when the saved session has no verified host binding: the terminal panel explains the missing connection, and Check connection again reloads that exact descriptor. It never selects a host from the title or directory, requests a transcript upload, or changes the Memo. Standalone conversation history remains a separate reading action.
Affiliations grant no additional access. Listing a link requires current read access to both the resource and the session; changing it requires resource write access and session read access. Moving a resource rechecks its current owner and permissions. Deletion or revoked access hides the corresponding links. A private session never becomes team-visible merely because its memo or artifact is public.
CLI 0.78.0 can link successful note/artifact writes to an explicitly selected
saved session, or an unambiguous owned session matching the current native
conversation UUID. An unresolved context leaves the successful content write
intact and reports the affiliation failure separately. Historical resources are
linked only from verified evidence or explicit selection, never from title matches.
Set DREAMLAKE_TERMINAL_SESSION_ID and DREAMLAKE_SESSION_NAMESPACE to select
an exact saved context; opening a terminal does not inject these variables.
The same native UUID registered under multiple machine bindings can be ambiguous,
so automatic affiliation is not guaranteed for every native session.
The session-library button at the left of the chat panel's tab row opens the sessions available to your account. Select a session to open a terminal in that same panel, beside the memo you are editing. Selecting an already-open session activates its tab. The memo and inactive chats and terminals keep their mounted state while you switch tabs. A tmux terminal keeps running when its viewer closes. On a machine without tmux, an owner can use direct mode; closing or losing that connection may stop its foreground process. Direct terminals show this limitation, require an explicit reopen to resume, and have no managed Stop or shared attachment. They do not reconnect automatically. This requires the matching runtime gateway and client; screen and other persistent adapters are not implemented yet.
Use Up/Down while a list row has focus to move through visible entries; Enter activates the focused entry. Arrow navigation does not open terminals or replace the memo. This behavior is shared by actionable memo, project, Bindr, session, Compute and other item lists. Inputs and editors keep their normal caret controls, and inactive panes never reclaim keyboard focus on refresh.
Restoring a terminal tab from an address shows Open session; restoring a layout never starts a command. The address contains the saved session ID, not terminal output or connection credentials.
The library includes your private sessions and sessions shared with an organization you belong to. Sharing a memo or its layout does not share a terminal. Session access is checked separately each time it is opened or reconnected. See Browser terminal for sharing, machine requirements, discovery and managed-session behavior.
Agent requests
Each mounted PageViewLayout registers in window.dreamlakeLayouts protocol v1.
Agents select a layout, inspect its revision and flat regions, resolve a request
without mutation, then apply it with an optional expected revision. Page reloads
and unmounts invalidate session IDs; list and inspect again instead of guessing.
Use CLI layout control for an explicitly selected local browser debugging session. Remote unattended control is not part of this transport. A successful layout request means placement was accepted, not that an artifact's asynchronous authorized loader succeeded.
| View kind | Resource identity | Required content metadata |
|---|---|---|
| session-library | namespace | namespace |
| terminal-session | namespace/session ID | namespace, sessionId |
| memo | memo ID | namespace, noteId; optional fragment |
| artifact | namespace/artifactId | namespace, artifactId; optional fragment |
| resource | namespace/notes | namespace, resource: memos |
| web-preview | normalized URL, or blank for an empty preview | url |
The application validates descriptors and their resource identity before changing the layout. Inspection exposes descriptors, pins and layout metadata—not memo bodies, credentials, share tokens, editor state or iframe authorization context. Applications can supply additional content metadata to the generic UIKit layer; DreamLake's current descriptor table above defines what this adapter exposes.
Layers and ownership
- UIKit PanelLayout handles low-level geometry and interaction mechanics.
- UIKit's controller handles named families, original/first/last, spatial and content queries, placement scope, reuse, pinning and guarded mutations.
- DreamLake handles target validation, content loading and the default artifact click policy. Memos content remains governed by the normal revision and authorization contracts; layout control cannot grant access to a resource.
The generic request reference lives in UIKit; CLI connection and command recipes live in the CLI docs. This page describes DreamLake's integration rather than maintaining a second copy of either API.