Release notes
0.134.0 — Optional Nymph install
Native installs accept an explicit --with-nymph flag, through both
install.sh and dl install. It installs the Nymph binary into
~/.local/bin with Nymph's official installer, or reuses an existing one
without upgrading it. Nymph is not configured, started or enrolled, and no
login is needed. Without the flag, only the CLI is installed. Supported on
Apple Silicon macOS and glibc Linux, including WSL; Intel macOS, musl Linux and
native Windows get a clear error. npm installs never install Nymph. See
Installing Nymph with the CLI.
Team roles, archive, guests and slug renames
- Roles:
dl team member add|role --roleacceptsowner,admin,maintainerandmember. A new team's creator becomes itsOWNER. Teams with only maintainers keep working as before. - Archive:
dl team archiveanddl team restorearchive a team without losing its members, grants or invitations; while archived it grants no access.dl team list --archivedlists archived teams. - Renames:
dl team update --slugrenames a team. The old slug stays reserved for that team and still finds it indl teamcommands. - Your permissions:
dl team showprints the current slug, earlier slugs, your role and what you can do on the team. - Guests:
dl team guest invite|list|revokeinvites an outside collaborator to one team without organization membership.- DreamLake sends no email;
inviteprints the join link the server returns (/teams/invitations/<invitation id>) for you to share. - Only the invited, verified email's account can accept, through that link
or
dl team guest inbox,acceptanddecline. - Guests get the team and the Projects shared with it, never SSH, web terminal or host sessions through team grants. This holds even if they later join the organization while still a guest; other access they hold is unchanged.
- DreamLake sends no email;
- TypeScript:
client.teamshas the same operations, andTeamFeatureUnsupportedErrorreports a server without them.
Requires the matching team API. See Teams.
0.133.1 — Relationship skill procedures
The bundled dreamlake-cli skill now uses DreamLake skills v2026.11.19,
including procedures for resource relationships, activity history and saved-session
associations. The matching Memo, Artifact and Annotation skills route related-work
requests to their existing actions. References use published CLI 0.133.0 and
product docs 0.1.185; session privacy, registration and opt-in export recovery
procedures are preserved. See Skills and
Resource relationships and history.
0.133.0 — Resource relationships and history
dl resources link|unlink|relationships records and reads explicit links between
Memos, artifacts and annotations using stable catalog IDs. resources history
reads best-effort server activity, and resources sessions lists saved sessions.
Relationship and history cursors are explicit; commands do not automatically page.
sessions link|unlink --annotation records saved-session associations. The
TypeScript client exposes the same operations through client.resources.
Requires the matching resource-relationships API. See Resource relationships
and history.
Ordinary Artifact and Annotation CLI requests now forward available optional session context for activity attribution. Context does not authenticate requests, grant access or upload terminal output. Activity retains 90 days of observed read/view/edit events; links do not fabricate events or constitute a complete audit.
The embedded skill remains pinned to the published v2026.11.18.1 skills release. The updated relationship task guides follow separately after these docs publish.
0.132.1 — Bundled skills v2026.11.17.2
The embedded dreamlake-cli skill and bundled catalog now pin
v2026.11.17.2.
It adds the host-sharing procedures for CLI 0.132.0: granting a team connection
access to a host enrollment, and filing a Host in a Project, optionally tagged into a Bindr
(dl project attach --type host --bindr), as placement only. References are
refreshed from CLI docs 0.132.0 and product docs 0.1.174. The skill's minimum
CLI is 0.132.0. Existing skill installation, update and local-edit conflict
handling are unchanged.
0.132.0 — Team host connection grants and Hosts in Projects
Requires a DreamLake server with team host grants and Host filing. Against an older server, --team and --type host are refused and hosts access list reports team grants as unsupported; existing --user grants and other attach types are unchanged.
dl hosts access grant HOST --enrollment ID --team SLUGlets every current direct member of one team in the Host's organization connect to one enrollment, all as its Unix account; team maintainers decide who that is, and members of parent or child teams are not included. Exactly one of--useror--teamis required. Requires the team-grant backend; an older server rejects--teamwithinvalid_host_access_grant. See Team grants.dl hosts access listasks for every grantee kind and shows a KIND column (userorteam).--jsonaddsteamGrants,teamsandteamGrantsSupported. Against a server without team grants it says so rather than claiming only you can connect.dl hosts access revoketakes person or team grant IDs and reports connections that stayed open because their user still holds another current grant (stillAuthorizedConnections). A grantee'sdl hosts statusnames the teams their access comes through.dl project attach|detach --type hostfiles a Host you own in a Project, or unfiles it. Filing is placement only: organization members who can read the Project see the Host's name and owner, and no Project role grants SSH or any other host access. Attach help no longer says every attached resource's access is inherited by Project grantees. See Hosts in Projects.dl project attach --bindr NAME_OR_IDalso adds the filed node to a Bindr in the same Project, for every type exceptsource. If adding it fails, the filing is kept and the command exits 1 with thenodeId; run the same command again to finish.dl hosts movepreviews and receipts showProject placements: N will be removedwhen the Host is filed in Projects (optionalprojectPlacements: {count, policy: "unfile"}; TypeScriptHostMoveProjectPlacements). A whole-Project move is refused while a Host is filed in it; unfile Hosts first.dl hosts access grant --teamtreats a receipt naming a different team as an unknown outcome. The TypeScriptgrantAccessrefuses a non-stringgranteeorteambeside the other instead of ignoring it.- TypeScript:
hosts(ns).allAccessGrants(id)(HostAccessGrantsAll,HostTeamGrantsUnsupportedError),grantAccess(id, { enrollmentId, team })(HostTeamAccessGrantResult),HostAccessRevokeResult.stillAuthorizedConnections,HostSharedAccessgrantvia/team, andProjectAttachmentTypeincludinghost. ExistingaccessGrants,grantAccess(id, { enrollmentId, grantee })and their types are unchanged.
0.131.0 — Memo and Bindr workflows
Bindrs support child creation and reparenting with --parent, returning to the
root with --top-level, and exact folder membership with --add-folder or
--add. Memo selectors resolve existing readable filings in other projects and
authorized retained filings owned by another workspace; ambiguous source
filings require --from-project. list bindr --json now emits JSON with the
flag before or after the subcommand. See Bindrs.
Transfer errors retain structured blocker details. Matching servers identify
blocking service-account grants and include those grants in admin project
inspection. A blocked legacy memos move preview gives the separate transfer
preview command. Existing transfer capability and recipient-acceptance gates
still apply; no access grants are removed to force a transfer.
The bundled skill and catalog pin the published v2026.11.16.2 skills release, including whole-agent release guidance and references from CLI 0.130.0 and product docs 0.1.170.
This release also includes dl launch SCRIPT --mount [namespace/]prefix from
the merged mounted-launch work. It submits through a management connection's
stored credential, with a stable invocation ID for recovery. Requires the
matching backend. See Launch through a mount.
0.130.0 — Whole-agent releases
dl runnable definition list|show|publish|activate and the matching TypeScript
SDK methods publish the saved agent draft as an immutable complete definition,
inspect its README and prompt, and activate an earlier release while preserving
the draft. Writes require the reviewed updatedAt; stale writes fail without
automatic retries. Built-in agent selection supports published and draft views
and carries an explicit definition version into execution. Requires the
definition-version backend. See Whole-agent versions.
0.129.0 — Independent SSH timeout policies
dl ssh and dl tmux honor the host’s negotiated inactivity limit and adapt keyboard-activity reports for shorter limits. Nymph 0.1.42+ uses max_duration_s for total lifetime and idle_timeout_s for inactivity; protocol grace stays internal. See Keyboard-idle disconnect.
0.128.2 — Bundled skills v2026.11.16
The embedded dreamlake-cli skill and bundled catalog now pin
v2026.11.16.
This release adds the host connection-sharing procedure: the dreamlake-cli skill routes
sharing a host's connection access to dreamlake-lakeshore, which covers
dl hosts access list|grant|revoke (CLI 0.128.0+). References are refreshed from CLI docs 0.128.0
and product docs 0.1.166. Existing skill installation, update and local-edit conflict handling
remain unchanged.
0.128.1 — Backend-owned memo ancestry and dotted tags
- The matching backend update selects causal ancestry when a checkpoint omits its parent, including before checkpoints from existing
memos reviseclients. Explicit roots and parent choices remain supported; existing saved versions are unchanged. Dotted numeric tags retain any number of parts and leading zeros, with UI support for using the tag as the displayed version label.
0.128.0 — Share connection access to a host
dl hosts access grant HOST --enrollment ID --user USERNAMElets one member of an organization namespace connect to one enrollment of a Host you own. They connect as that enrollment's Unix user and share its files, processes, credentials and OS permissions; DreamLake creates no OS user. Both flags are required; nothing is guessed.dl hosts access list HOSTshows grants, anddl hosts access revoke HOST GRANTrevokes one. Revoking denies new connections at once and reports how many open connections it closed. Any it could not confirm closed are reported with the time they end on their own; the command then exits 1, and running it again tries to close them again. A grant or revoke without a clear answer is reported as unknown and is never retried automatically. See Share connection access.- A Host reached through a grant shows
sharedin an ACCESS column ofdl hosts list(also{access}) and anAccess:line indl hosts status, taken from the server'saccess.kindmarker. Owner output is unchanged. - TypeScript:
hosts(ns).accessGrants(id),grantAccess(id, { enrollmentId, grantee })andrevokeAccess(id, grantId), with exportedHostAccessGrantList,HostAccessGrantResult,HostAccessRevokeResultandHostSharedAccess.
0.127.0 — SSH sessions end after 30 minutes without keyboard input
dl sshanddl tmuxdisconnect 30 minutes after the last keystroke or paste, printdl: disconnected after 30 minutes without keyboard input.and exit 124. Remote output, mouse, focus, terminal replies, resizes and keepalives never keep a session open; while you type, it renews on the same connection without reconnecting. Hosts, backends or installs that cannot do this keep a fixed 30-minute session and say so.--durationasks for a fixed lifetime;--timeoutstays an absolute limit;dl execis unchanged. See Keyboard-idle disconnect.- After any SSH session ends, the terminal is restored and modes a remote program left on are switched off, so an abrupt disconnect no longer prints mouse movement as text such as
35;1;36M. A session the server already ended no longer warns that cleanup could not be confirmed. dl hosts upgradenow reaches Nymph running under a lingering systemd user manager on Linux; it previously stopped withsystemd_user_unavailablebecause relay sessions have noXDG_RUNTIME_DIR.
0.126.1 — CI/CT status names person-only steps
dl cict statusalso lists person-only steps that can happen alongside the next one (for example asking for DreamLake GPU while the GitHub App is installed), and the ready line names every runs-on label.
0.126.0 — CI/CT setup status
dl cict status NSshows where a namespace stands on CI/CT (GitHub, DreamLake GPU, your own machines), which steps are done and the next one with its page, command and API call;--jsonfor agents. TypeScript:dl.cict(ns).onboarding().
0.125.4 — Source, Folder and Bindr visibility
Sources, Folders and Bindrs support Private, Unlisted and Public visibility. Unlisted items remain readable through their direct links and are excluded from public discovery. Visibility commands and TypeScript methods use the observed revision to reject stale changes. Existing unset Folder and Bindr settings retain inherited visibility; their parent Project and independent resource permissions remain separate.
0.125.3 — Bundled skills v2026.11.14.1
The embedded dreamlake-cli skill and bundled catalog now pin
v2026.11.14.1.
This includes the Project address procedure and refreshed references from CLI
docs 0.125.2 and product docs 0.1.161. Existing skill installation, update and
local-edit conflict handling remain unchanged.
0.125.2 — Canonical Memo references
Memo creation JSON and TypeScript handles include directive with the returned
immutable ID. Text output includes the same ready-to-insert :memo[full-id].
An unconfirmed ID stops before a body write; inspect existing Memos before
retrying. Titles and slugs never replace reference IDs. Saved legacy references
remain readable.
0.125.1 — Bundled skills v2026.11.13.1
- The embedded
dreamlake-cliskill and the bundled skills catalog are pinned to dreamlake-skills v2026.11.13.1. Itsdreamlake-experimentsskill covers experiment evaluation and analysis (Python SDKdreamlake0.51.0);dl skill install dreamlake-experimentsordl skill updateinstalls it. - Docs: the experiment guide names the tested Python 3.13 environment for planned sweeps.
0.125.0 — CI/CT usage by person, per-job machine specs
dl cict usageadds GPU time by the GitHub user who triggered each job;--jobslists the jobs newest first,--sender LOGINnarrows them and--limitcaps them. The TypeScriptusage(month, { sender, limit })returnsbySender,runsandrunsTotal.dl cict platform admin list --month YYYY-MMshows that month and the platform total.- Machine types are what one job gets:
platform show,admin listandadmin machineprintper job: 1x RTX 5090 · 8 CPU · 32 GB · 02:00:00. That spec is read from the provider's launch layer, soadmin machinedrops--gpus,--gpu,--cpus,--mem-giband--time-limit. The newdl cict platform admin providerslists the platform namespace's Slurm providers and what one job gets on each.
0.124.0 — DreamLake GPU authorizer
dl cict platform shownames who authorizes DreamLake GPU result writes and says when they can no longer write; jobs then wait, shown asheld: re-authorizeinruns listand "waiting for re-authorization" inruns show.dl cict platform source NS --source <current Source>re-authorizes.platform admin listflags namespaces that need it.
0.123.0 — CI/CT commands
dl cictmanages CI/CT through GitHub Actions:github connect/installations;pools list/create/update/delete/targets;runs list/show/compare, wherecomparegives case-by-case regressions against the default-branch baseline;- DreamLake GPU:
platform show/start/sourceandusage; platform admin list/allow/pause/limit/machinefor platform namespace admins.
- The TypeScript API adds
dl.cict(namespace)anddl.cictPlatformAdmin. See CI/CT with GitHub Actions. memos revisepreserves authored wording as pending redlines, protects native resource references, publishes edit intent, and verifies reviewed before/after versions with durable recovery receipts.
0.122.0 — Annotation URL rename
dl annotation list/get/update/renameand the TypeScriptclient.annotations(namespace)client read metadata and change titles or canonical URL slugs.- Slug updates preserve immutable identity, data/history and old links. Namespace management permission and observed ID/slug/revision guards prevent collisions and stale concurrent writes.
- Servers without the new capability reject a rename before any write. See Annotations.
0.119.2 — Exact host terminal targets
dl exec,dl sshanddl tmuxlook up SSH targets for the selected host (and--enrollment, when given) instead of reading the namespace's whole terminal catalog, so other hosts, including archived ones, never block a connection. Archived hosts remain reachable by full name or ID. Host, enrollment, delegation and host-key checks are unchanged.- Terminal API failures name their code, for example
HTTP 503: terminal_inventory_limitorHTTP 409: terminal_not_ready, with recovery text for both. - Bundle DreamLake skills
v2026.11.11, which adds experiment task routing and USD preview and scene collection guidance since 0.119.1; no CLI behavior change.
0.119.1 — Source workspace skill
- Bundle DreamLake skills
v2026.11.10.4. Freshdl initinstallations include the guarded Source text-edit procedure and the published workspace-file guide. The procedure requires an explicit Source, preserves revision checks and keeps Project edits and associations separate from Source edits.
0.119.0 — Agent chat and Source text workspaces
- Chat with the server-owned built-in agent through
dl agent chat, with streamed receipts, conversation continuation and explicit opt-in writes. - List, read, create and edit managed Source text using
dl source filesand the exported TypeScript file adapter. Edits use revision guards and literal replacement; Project associations do not select a writable Source.
0.118.1 — Native file upload fix
- Fix native run and project file uploads, including whole-run
.dashuploads, sending an empty file when the source is a disk-backed Blob under Bun. Multipart requests now stream the original file bytes and preserve filenames, MIME types, size and checksum. - The existing native packaging check now uploads a disk-backed binary through a real HTTP receiver before a release can pass CI.
0.118.0 — Native experiment parity
- Transfer complete experiment runs with
dl experiments upload|downloadin the interoperable.dashformat, preserving paths, metadata, Bindrs and protection. Downloads verify files before replacing an existing local run; failed transfers retain recovery state and the previous copy. - Manage native writer registration, inspection, rotation and retirement through
dl experiments writers; submit and inspect project-bound compute jobs throughdl experiments jobsand the TypeScript API. - Preserve Unicode, double quotes and literal percent sequences in native run and project file uploads, including content replacement. The existing exported FormData builder remains available for compatibility.
0.117.0 — Restricted Project sharing and terminal permissions
dl project permissions selects an organization and Project, explains effective
human access, and previews user/team grants, revocations and Workspace/Restricted
changes before confirmation. project audience --json returns the same complete,
bounded snapshot. project access --mode restricted --visibility private removes
the organization-member READ baseline; explicit grants and owner recovery remain.
Restricted creation is atomic and requires advertised backend support. Unsupported
contracts and uncertain receipts stop without automatic retries. TypeScript gains
matching access, audience and restricted-creation APIs. Independent attached-resource
shares remain separate. See Project permissions.
0.116.0 — Persistent remote tmux shells
dl tmux HOST and dl hosts tmux HOST create or attach to the remote tmux
session dl-session. Use --sess NAME or --session NAME for another name.
The host remains explicit, and the command reuses the existing authenticated,
host-key-pinned SSH relay. Detach with Ctrl-B, then D; reconnect with the same
command. Remote tmux and an interactive local terminal are required. Missing
tmux reports how to open a plain shell with dl ssh HOST.
See persistent tmux shells.
0.115.0 — Exact Codex root binding
Saved Codex sessions retain their explicit codexHome when reopened. The CLI
requires the session and launch descriptor to agree on the canonical remote root;
omitted roots keep legacy behavior. The TypeScript SDK exposes Session.codexHome
and accepts it in terminal(namespace).create(). This requires the companion
API/gateway root-binding release. No new flags or terminal interaction are added.
See Codex root binding.
0.114.0 — Session aliases and search
Use dl sess, dl session, or dl sessions, and --sess or --session.
dl sess search "release" shares the existing list filters and pagination.
--search-in title|all and the TypeScript searchIn field select title-only or
broad search; title-only search requires the companion API release. Searches
retain existing access checks and never launch a session.
CLI output and SDK types preserve observation timestamps, the last observed state, and outstanding attention when current state becomes unknown. See session commands and search.
0.113.0 — Memo cover images
dl memos cover (title-image alias) inspects, uploads, replaces and removes
header images without editing the memo body. TypeScript handles expose
metadata() and setCover({fileId}); namespace APIs expose setCover(id, fileId).
Use an existing attachment ID or null to clear. Permission checks and explicit
acknowledgements prevent unsupported writes from being reported as saved.
0.112.1 — Bundled dl command guidance
Bundles skills v2026.11.09.2 with procedures that prefer dl and retain
dreamlake for missing-command or conflict recovery. The embedded references
come from the published CLI 0.112.0 and product-docs 0.1.134 releases. Existing
installed skills can be refreshed with dl skill update; local edits remain
protected by the installer checks.
Automatic native alias setup is unchanged. Process management uses the observed
process name, which can be dl when launched through the alias; prefer
kill <PID>. See installation.
0.112.0 — Use dl everywhere
dl is now the preferred command in help, examples, and command hints.
dreamlake remains supported with the same arguments, settings and credentials.
Package names, installed paths, environment variables and service identifiers
retain their existing names. Process matching depends on the executable invocation.
Existing native installations create a missing dl on the first invocation of
this version, including installations upgraded by an older binary. This local
setup verifies the managed installation, preserves unrelated commands, and does
not download anything, change a version pin, or edit PATH. It works with updates
disabled. Windows accepts both short and long paths to the same verified launcher.
See installation for conflicts and compatibility.
0.111.2 — Bundled collaboration visibility guidance
Bundles skills v2026.11.09.1 with the published Memo presence, selection
and revision-diff references. The separately installable dreamlake-memos
skill routes observation requests through explicit availability checks and
source-bound selection handling. Latest-only artifact sharing guidance remains
included. See collaboration.
0.111.1 — Bundled latest-only sharing guidance
Bundles skills v2026.11.09, including latest-only artifact sharing guidance
and the published CLI/TypeScript API references. The separately installable
dreamlake-artifacts skill covers customer sharing, SDK readback and verification.
The controls introduced in 0.110.1 and the Memo selection features in 0.111.0
remain available. See Artifact sharing.
0.111.0 — Observe human Memo selections
memos presence --selections requests a source-bound selection snapshot without
joining. The TypeScript namespace and handle APIs accept {selections: true}.
Availability states distinguish inactive rooms, unsupported older servers and
failed observations from an available empty roster. Selection offsets use
Unicode code points at the returned source hash; recent edits still use revision
diffs rather than inferred human authorship. See collaboration.
0.110.1 — Latest-only artifact sharing
artifact share latest-only <id> on|off changes recipient version access without
uploading content or changing the link. share create and artifact push accept
--latest-only and --no-latest-only; omission preserves the policy.
share get reports shareLatestOnly. The TypeScript API adds
artifacts(namespace).share(id).latestOnly(boolean) and accepts
shareLatestOnly in publishing/registration input. See Artifact sharing.
0.110.0 — The dl command
Native installers and npm now provide dl alongside dreamlake, with the same
commands, arguments, settings, credentials, and exit status. The executable
works in Bash, Zsh, Fish, sh/dash, PowerShell, CMD, and scripts. Native installs
preserve unrelated dl commands and report conflicts.
For an older native installation, re-run the bootstrap installer to add dl,
or update and then run dreamlake install --no-modify-path. Subsequent native
updates maintain both names; npm updates and uninstall manage both bin entries.
See installation for exact pins, PATH, completion,
conflict handling, and uninstall.
0.109.0 — Editable public article URLs
dl memos permalink <memo-id> --json gets or allocates a public URL.
Add --slug my-article to edit it while preserving previous slugs. TypeScript
handles expose memo.permalink({ slug: "my-article" }); both surfaces return the
canonical URL and alias history. Namespace collisions are refused without retries.
See Sharing and visibility.
0.106.0 — Memo help and native experiment commands
Memo examples, identifier placeholders, generated command help, and move results consistently use Memo terminology. Existing aliases and HTTP contracts remain compatible during the phased rollout.
This release also includes the merged native experiments command stack: run data, files, tracks, folders, protection, batch operations, and bindrs. Native writes check server capabilities; protocol 6 operations require matching server support. Verified downloads use a temporary file before installation, and logout follows the shared login contract.
0.105.1 — Published Memo skill
The bundled agent skill now pins published v2026.11.06.1. Installation guidance and generated CLI help use dreamlake-memos; new references use ordinary links, while saved :note directives remain readable. The refreshed skill includes the current Memo SDK and structured snapshot guidance.
0.105.0 — Canonical Memo TypeScript API
Use client.memos, memosApi, Memo* types, and the Memo editing helpers. SDK modules and CLI implementations now use Memo names; old public exports remain aliases during the phased rollout. Existing HTTP routes, response fields, and editing semantics stay compatible.
0.104.6 — Memo branding
Use dl memos or dl memo for the shared space with your agents. Help, messages and documentation now call these resources Memos. Existing notes and note command aliases, SDK APIs and data remain compatible during the phased rollout.
0.104.5 — Actionable Memo transfer failures and diagnostics
Metadata-transfer commands preserve API error codes, HTTP status, request IDs and supported grant reasons in JSON failures. Memo move and transfer diagnostics record blocked previews even when HTTP returns 200, while uncertain writes retain their dispatch state and are never automatically retried. Existing telemetry opt-out and privacy controls remain in place. Requires the matching API collector for the new optional diagnostics; this release does not broaden cross-workspace Memo transfer admission.
0.104.4 — Declared public data origins for artifact sites
Static sites can declare exact public HTTPS data origins in artifact.config.json or an explicit --site-config file. The CLI checks server support before uploading and obtains an authorized, manifest-bound grant before publishing the site version. Sites without declarations retain the existing v1 format. This requires matching server and frame support.
0.104.3 — Host IP addresses and machine inventory
dl hosts shows reported interface IPs, hostname and Unix user by default, with one row per enrollment. --wide adds enrollment ID, OS, architecture, CPU count, Nymph version and last-seen time; hosts status HOST includes interface details and observation freshness. --fields and --format support custom rows.
Automatic IP inventory requires the matching API and Nymph 0.1.36+. Older daemons show unknown addresses; explicit --probe performs SSH diagnostics for interface IPs, MACs, public egress IP and uptime. Default listing makes no SSH or external-IP requests. Addresses do not prove reachability. See Host inventory.
0.102.3 — Reviewed cross-project Infrastructure paths
infra movepreserves a stack's resource-tree path when moving its registration to another Project. Preview binds the source path and intended destination; an explicit--destination-pathselects another placement.- Confirmation verifies path, identity and completion before reporting success. Unconfirmed writes retain the stack UUID and operation ID for reconciliation, without an automatic retry.
- The TypeScript API exports
InfrastructureStackMovePreviewInputandInfrastructureStackMoveRequest. UUIDs, HTTP state backends and Terraform resources remain unchanged.
Requires the matching cross-project Infrastructure move API. Bindr membership and runbook blockers remain enforced. The separate recipient-accepted infra transfer lifecycle is capability-gated and has no fallback to relocation. Bundled skills remain pinned to published v2026.11.03.2.
0.102.2 — Memo contributing sessions
notes contributorslists persistent sessions and their observed creation/edit evidence, separately from manually linked sessions.- Memo presence and editing share optional native or saved-session context. The server records confirmed contributions; the CLI no longer follows each Memo write with a separate affiliation request.
- The SDK exposes
notes.namespace(namespace).contributors(noteId). Missing or malformed optional metadata does not prevent content saves; no-op and failed writes do not establish authorship.
Requires the matching Memo contributor API. Artifact affiliation and explicit conversation uploads retain their existing behavior. The bundled skills remain pinned to published v2026.11.03.2.
0.102.1 — Faster repeat incremental artifact uploads
Repeated incremental uploads validate and reuse known chunk boundaries for unchanged inputs of at least 64 MiB, avoiding the rolling chunk scan. Bounded artifact-scoped S3 listing checks replace individual chunk requests where supported, with parallel HEAD checks as a fallback.
Each push still creates a version and restores missing stored chunks before publication. Changed inputs retain content-defined chunking; small inputs avoid the additional manifest read. The incremental format and its 512 MiB limit are unchanged. See Incremental uploads.
0.102.0 — private Host moves and persistent CLI namespace selection
Move a personally owned Host into another namespace without changing its Host ID or re-enrolling its machine. hosts move --dry-run previews private owner access and dependency blockers; applying requires the reviewed revision, preview hash and stable request ID. The TypeScript API exposes hosts(namespace).movePreview and move. The matching server enforces ownership, private access and exact-input replay. Agent namespace selection is available as /su <namespace> in the matching built-in agent GUI.
dl su <namespace> persists the default namespace for later CLI commands while keeping your login identity unchanged; an explicit --namespace wins. Login and environment changes clear the selection. Native SSH now maintains bounded backpressure under large output bursts and preserves TLS identity checks and timeout cleanup.
0.101.0 — Static artifact builds with on-demand files
dl artifact push ./dist/client --sitekeeps a built client site's HTML, CSS, JavaScript chunks, media, WASM and data as separate versioned files. The browser loads requested assets on demand; unchanged file hashes are reused on later uploads.--spaexplicitly enables extensionless document fallback.- Site uploads have no fixed aggregate size cap. Files are hashed with bounded buffers and streamed from disk. HTML pages remain limited to 32 MiB, manifests to 2 MiB and builds to 4096 files; the current single-PUT transport accepts up to 5 GiB per individual file. Existing upload formats retain their limits.
- Source checks and signed SHA-256 checksums bind uploaded files to the immutable manifest. Failed file uploads do not publish the manifest or artifact version.
- Static sites are available on DreamLake hosting. Self-hosted installations need compatible server, viewer and frame deployments with isolated content hosting. The CLI checks hosting capability before uploading. See Static artifact sites.
- Native SSH validation now checks pause/resume independently of OS socket read sizes while retaining bounded rejection of already-decoded bursts.
0.100.0 — ssh and exec pick a host from a keyword
dl ssh <keyword>anddl exec <keyword> -- …: when the selector names no host and the command runs in a terminal, a picker lists the hosts whose name or ID contains the keyword, best match first and highlighted, with the top row selected. Typing filters,↑/↓move, Tab completes the typed text toward the selected host one/segment at a time, Enter connects and echoes the full command, Esc cancels with the original error. With stderr on a terminal but stdin piped, the error is followed by the same table as static text and nothing is connected. Without a terminal the error is unchanged and no inventory is read. See SSH and remote commands.
0.99.0 — Sessions: live state, restart with a raise rule, wrappers; skills read
Sessions control plane, batch 2 (control plane, hooks). The server routes these commands use ship separately; against an older server they answer 404.
sessions control restart <id> --permission <level> [--raise] [--prompt] [--mode] [--reason]: stop and resume the same conversation under a new recorded level. Lowering always passes; raising needs--raise, a typed confirmation on a terminal, and a runner started withsessions serve --max-human-permission <level>(advertised ascapabilities.humanPermissionCap, shown bysessions runners). The built-in agent never raises; a child never passes its parent. Receipts echoargv(the exact command line, every turn kind),previousPermissionLevel,stoppedandeffectivePermissionLevel; pods refuse (pod_restart_unsupported).sessions permission <id> <level> [--raise] [--reason]moves the record only (PATCH …/permission); the runner records the launch level of every tmux process and relaunches a live one under the record before typing into it when the two differ (unrecorded: refused until a restart). A session registered without a runner start has no level and is refused until onecontrol restart --permission … --raiserecords it.- Hook relay:
sessions heartbeat --state <liveState> [--tool] [--prompt-head] [--hook-stdin] …andsessions event --kind SubagentStart|SubagentStop [--subagent] [--name] [--finished] [--tokens] [--hook-stdin], one bounded request each, the prompt head truncated to 200 characters and never printed, exit 1 never 2.--hook-stdinreads Claude Code's hook JSON (onlysession_id,tool_name,prompt,agent_id,agent_type) and finds the saved session through the env filesessions register --write-envwrote, also viaCLAUDE_CODE_SESSION_ID. The runner reportsrunningevery 10 s while it executes a turn, then the outcome. Ready-to-copysettings.jsonhooks: Claude Code hooks for live state. sessions status <id>reads the descriptor first (live state, current tool, permission level, runner) and answers for native and runner sessions instead of the gateway's 503 / 409;sessions tree <id>shows managed children and native subagents;sessions watch [--session <id>] [--json]follows the SSE stream (readable lines, or NDJSON) and exits 0 on the server's 15-minuteend.dl claude …/dl codex …: start the stock CLI under DreamLake — register first (Claude; Codex adopts its rollout afterwards), export the saved-session pair, map--permissiononto--permission-mode/--sandbox, upload the transcript on exit, keep the provider's exit code.- Runner fixes (batch 1):
CLAUDE_CONFIG_DIRis exported only for the user's own, logged-in, non-default profile (receipts sayclaudeConfig.reason); the writer guard ignores the runner's own previous turn; tmux 3.5a targets (=name:), launch nonces and orphan teardown that removes only a worktree carrying this creation's identity file at the tip git created;sessions register --write-envwrites exported, shell-quoted assignments; failed and uncertain receipts carryresult.errorwith exit code, signal and redacted output tails; the runner deregisters itself on exit (DELETE …/session-runners/:id,runners.deregister); an owner's cancel reaches the provider within about 2 s on its own clock. dl skill read <name> [--file <path>] [--local|--remote]prints one file of any catalog skill without installing it, from the server's registry when logged in or the embedded bundle, naming the source, tag and commit;skill listshows the same catalog. TypeScript:dl.skills.list(),dl.skills.skill(name),dl.skills.read({ skill, path }),dl.skills.file({ skill, path, ifNoneMatch }).@dreamlake/dreamlake-cli/api:sessions(ns).permission,heartbeat,event,tree,watch(async generator),runners.deregister;PERMISSION_LEVELS,isPermissionRaise,LIVE_STATES,WatchEvent,SessionTree,restartinCOMMAND_KINDS.
0.98.0 — Memos API contract: callable facade, mapped default, verbatim append
@dreamlake/dreamlake-cli/api:dl.notes(noteId)opens a local handle (IDs are primary; the owning namespace is read from the memo's metadata on first use) withread({ view, at, lines, section, address }), verbatimappend,replace/insert/removewith exactly one selector,write,patch,outline,find,diff,presence,visit,versions,files.moveandmove;dl.notes.listanddl.notes.createare the collection operations anddl.notes.namespace(ns)scopes a dynamic namespace. Every operation takes one named object;atis a snapshot or a revision, never a hash.dl memos readprints the mapped Markdown view by default, in a terminal or a pipe;--view sourceprints the exact source bytes only (no header, no added newline);--jsonis one snapshot object.--lines a:breads a focused slice with its code-point address andscope.notes appendis verbatim: exactly the given text, no separator added.--nsaliases--namespace.replace,remove(alias ofdelete) andinserttake the memo ID positionally with--lines a:b,--address ID,--before/--after ID,--cursor Nand--file;createwithout a title makesUntitled;move --to-project/--to-folder;find/toc --atreportnote,hashandrevision;list --offset.--command-id <id>onappend,patch,write,replace,insert,deleteandnotes command-status NOTE ID: public command identity, the answer to safe replay of a lost-response append (opt-in; server support ships separately). Write receipts carryoutcome,commandIdandreplayed; failures are typed outcomes: not submitted (exit 1), settled refusal (3/5), uncertain (4).- Scripts that parsed plain
notes readtext or the old--view sourceheader must switch to--json. See Reading and Editing.
0.97.2 — Session titles from Claude Code transcripts
- Session discovery reads the
aiTitleandcustomTitlerows that Claude Code writes, so a session imported from a transcript carries its title. A custom title set in Claude Code wins over generated ones; among rows of one kind the last one wins. Older exports with a plaintitlefield still work. See Terminal sessions. - New guide Third-party API keys in pass and Vault: one
convention for keeping a service API key in the local
passstore and in Vault under<owner>/cli/<service>/api-keywith the variable its tooling reads. - The embedded
dreamlake-cliagent skill is dreamlake-skills v2026.10.31, which adds theapi-keysaction and carries that page.
0.95.0 — Relative entry expiry
vault add --expires-in <duration> sets a retrieval expiry relative to the local
clock at upload time (90d, 12h, 1w3d; units s, m, h, d, w, each at
most once). It converts to the same UTC RFC3339 value that --expires-at sends,
so no server change is required. --expires-at, --expires-in and --no-expiry
are mutually exclusive; omitting all three still preserves the current expiry on
replacement. Guide.
0.94.0 — Bound executions on a pinned worker
dl runnable bind | execute | execution-receiptbind a registered UDF version to one configured snapshot and locked runtime, submit recoverable queue attempts and read their receipts. With--target <namespace/group/host>, DreamLake submits the attempt to that host's worker and returns the receipt; the submitting CLI and the UDF need no control-plane token (the server and the worker daemon keep their normal credentials). An identical repeat returns the same invocation instead of running again. Needsdreamlake-lakeshore0.5.1 or newer on the submitting machine and the worker. See Execute a bound UDF on a queue.dl queues createcreates a queue, anddl queues worker-pinshows, sets or clears the queues one worker claims from (--hostis required to change it). See Pin a worker to dedicated queues.- Existing commands and their
--jsonoutput are unchanged.
0.93.0 — Skills for Claude Code and Codex in one run
dl initand everydl skillsubcommand accept--agent all, or a comma-separated list such asclaude,codex. Each agent gets its own managed copy, in.claude/skills/and.agents/skills/, from one catalog and one download. The guideddl initoffers "Claude Code and Codex" as a choice. See Where it goes.- With one agent, every command and its
--jsonoutput are unchanged. With several, results carryagents, andremoveandlistreport per agent. A choice of several agents is saved so that older CLIs still read its first agent.
0.92.0 — Stop a worker from claiming jobs
dl queues worker-claims <prefix> <worker-id> [--disable|--enable]shows or sets whether one worker claims new queued jobs and tracked runs through a queue mount. A disabled worker keeps heartbeat, control commands, setup and remote exec. The command prints the value the control plane stored. Jobs already claimed are not cancelled. See Stop a worker from claiming jobs.
0.88.1 — Trusted home aliases for Nymph settings
- Managed Nymph commands accept trusted home-directory aliases such as
/home/geyang -> /export/work/geyang, resolving the home before looking up the existing enrollment. This avoids rejecting an otherwise private setup. - Settings beneath the resolved home still reject symlinks. Home ownership, directory permissions and private-file checks remain enforced. No enrollment identity or access permissions change.
0.88.0 — Agent skills installed from dreamlake-skills v2026.10.27
- Agent skills are authored in the public dreamlake-skills
repository and installed from its releases:
dl initpicks the agent and scope and installs the embeddeddreamlake-cliskill offline;dl skill install|update|remove|listwork from the release'scatalog.jsonandskills.tar.gz(checksum-verified), record every install in<skill>/.dreamlake-skill.json, and never delete or overwrite a file that manifest does not vouch for. See Agent skills. - This release embeds dreamlake-skills
v2026.10.27(skills.lock: tag, commit and tarball sha256, verified at build time; the embedded catalog lists 14 skills). The embedded skill is no longer generated from this site, and the downloadable skill zip is gone. skill updatenever downgrades on its own (--allow-downgrade),--forceonly overwrites files you edited, andskill removekeeps edited files.- Every markdown export of this site (
<page>.md,llms-full.txt) now opens with<!-- source: <page url> @ <cli version> <git hash> -->so a fetched copy records where and when it came from.
0.84.0 — Recoverable resource transfer clients
- Project moves negotiate the server's explicit streaming version and preserve that version through review, apply, progress and receipt replay. Existing v1 requests remain exact; v2 errors never cause a downgrade.
- Generic singleton metadata transfers support the separately advertised Pipeline profile without reading code or history.
infra transfer plan/create/status/acceptuses Infrastructure's dedicated review and immutable receipt protocol; namespace transfer authority does not grant stack state or provider permissions.- Library push/add/rm use immutable upload generations only when the server advertises protocol v2. Private local recovery journals retain file fingerprints and multipart progress; bounded session status/presence reconciles uncertain responses. Once v2 is selected, errors never fall back to the legacy writer.
These are client capabilities, not a declaration that every server adapter is enabled. Each requires its matching server reader/storage floor and admission capability. Source transfer remains unsupported; Project streaming v2 covers Memo, Artifact, Env/Scene and Annotation, while Pipeline and Infrastructure use their separate transfer profiles. No provider launch or IAM authority is added.
0.83.0 — Recipient-accepted metadata transfers
Adds notes transfer and ownership transfer note|artifact|env|annotation with
saved request review, per-type capability checks and exact committed receipts.
scene aliases env. Content and RTC history are not loaded or exported.
--accept-if-authorized uses destination authority; --accept-if-owner remains
a compatibility alias. Each resource profile requires its matching enabled API
adapter; recognizing a CLI type does not enable the backend.
0.82.0 — Session registration and public defaults
Adds metadata-only native session registration, automatic registration before post-save affiliation, explicit private creation overrides, actionable target access errors, and credential redaction before conversation upload. Requires the matching API release; deployment and public package propagation are separate checks.
0.80.0 — Stack paths in the project resource tree
infra create --path places a new stack in its Project's resource tree, next to
Memos and folders (default infra/NAME/ENVIRONMENT). infra status and infra list
print Path:. infra move --destination-path changes only a stack's path inside
its own Project; the review pins the current path, and UUID, backend URL and state
are unchanged. Stacks that have a path cannot yet move to another Project. Requires
the matching stack-path API; older servers keep working and show Path: unassigned.
0.78.0 — Memo and artifact session affiliations
sessions link, unlink, and paginated resources connect exact saved sessions
to Memos and artifacts across namespaces. Links preserve both resources' current
permissions; they do not share terminals or launch processes.
Acknowledged memo content writes and artifact pushes can automatically record an
exact saved-session or native-session context. Reads and failed writes add no
affiliation traffic. The bounded lookup refuses ambiguous or missing registration;
a link failure warns without turning a successful content write into a failure.
Retry only the relation using sessions link. Requires the matching resource-session
API. See Terminal sessions for context variables and limits.
0.77.0 — Claude Code and observed session states
Provider-aware session commands support Claude Code with --provider claude,
--session, and optional --claude-config-dir. Listings report observed run states
separately from managed terminal lifecycle. Requires matching API, gateway and
machine collector releases; existing Codex flags remain compatible.
0.76.0 — Collection defaults and combined help
Collection groups with an existing list command now default to listing.
For example, dl hosts --all is equivalent to dl hosts list --all.
Parent -h combines listing options and the command menu; explicit list -h
remains available for focused help. This applies to nested collections too,
while required scopes and other subcommand options remain unchanged.
Managed Sessions filters and pagination from 0.75.0 are preserved: bare
sessions accepts the same registry query, machine, cursor and sort options as
sessions list. No backend or Nymph update is needed for this CLI change.
0.75.0 — Managed terminal lifecycle and explicit Codex discovery
sessions status, start, reconnect, and guarded stop --yes distinguish
observing, starting, attaching and terminating the saved session’s exact tmux
runtime. Legacy live sessions remain attachable; unrelated or unverified
processes are never adopted or stopped. Detach still preserves remote work.
sessions sync --target ID or explicit --all discovers one bounded page of
recent root Codex conversations per selected enrolled host. It preserves existing
titles, reports skips and omitted observations, and launches no terminal.
Registry listing gains pagination, query, machine filters and recent ordering.
Discovery reads the default ~/.codex index, not transcripts; Python 3, tmux and
Codex are never installed automatically. resume --json stays save-only, while
explicit start --json and sync --json perform their documented operations.
Requires the matching managed-session/discovery gateway and registry pagination API; updating the CLI does not deploy them. Native loopback gates cover lifecycle identity guards, explicit discovery scope and two-host concurrency alongside the existing Origin, terminal stream and bundled-skill checks. See Terminal sessions for exact limits and failure recovery.
0.74.1 — Native terminal connection fix
Native and npm installations now send the configured Origin header during the
terminal WebSocket handshake. Bun ignored the previous origin option, causing
0.74.0 to fail before attaching. Upgrade to 0.74.1 for sessions open and
interactive sessions resume; existing saved descriptors and remote tmux
processes are preserved. The gateway still requires its configured allowed Origin.
A compiled transport regression checks that header and the ticket, binary ACK, resize, UTF-8 input, detach and raw-mode restoration paths.
0.74.0 — Persistent Codex terminal sessions
dl sessions saves and reopens the same enrolled-host terminal in the CLI
and the Sessions page. Select a target with sessions targets, then use
sessions resume UUID --target ID --cwd PATH to save and attach, or
sessions open SESSION_ID to reopen its persistent tmux session. Ctrl-] detaches
without stopping the remote process. The selected host and Unix user must already
have the Codex conversation, working directory, codex, and tmux.
sessions create and sessions resume --json save descriptors without executing.
sessions list and sessions show read metadata, not live process status.
Requires the matching backend terminal-sessions API and terminal gateway Codex
launch support; updating the CLI does not deploy them. See
Terminal sessions.
0.73.0 — Host catalog archive and active inventory
hosts list now shows verified online hosts by default. Use --all to include
offline and unknown connections. --archived exclude|include|only independently
controls catalog visibility; use --all --archived only to find offline archived
entries.
hosts lifecycle, hosts archive and hosts restore inspect and change catalog
visibility using an exact Host ID, request ID and expected revision. Archive is
reversible and preserves runtime, credentials, reserved names and history.
Permanent deletion and runtime retirement are not supported. Requires the
matching backend catalog API. See Host enrollment.
0.64.0 — Artifact and Env in whole-Project transfers
CLI 0.64.0 accepts complete typed Project/Note/Artifact/Env plans with the matching backend. Saved reviews retain every typed resource, access choice and external-filing effect; a mixed plan is never reduced to its Memo subset. Artifact/Env outside placements always detach, their old namespace-based links cannot be retained, and all included resources become private. Storage stays in place and previously issued capabilities retain their TTL. Source, Workflow, Annotation and structural content remain unsupported, as do standalone moves. An enabled whole-Project backend is required; check the plan and preview before submitting the exact reviewed request. See Projects.
0.63.0 — Whole Project ownership transfer
project move previews and transfers a Project with its complete owned-Notes
manifest through one ownership journal request. Save a dry-run review and confirm
the exact preview hash and stable idempotency key; replay preserves that review
even after the source Project moves. Cross-user requests require acceptance by
the destination namespace owner.
Resources become private, old access is revoked and external Memo filings detach
by default. Access retention and --preserve-external-filings are explicit
opt-ins. Unsupported or partial plans fail closed. Requires the enabled companion
backend; standalone cross-namespace Memo and Source moves remain unsupported.
The bundled Projects, Ownership, Data and Memos guides describe this workflow.
See Projects.
0.62.0 — Project resource attachments
project attach and project detach organize Memos, Artifacts, Annotations,
Workflows, Scenes (env) and Sources by database ID. Explicit Project grants
cover current and future attachments; public Project visibility alone does not
expose private resources. Source retains its existing whole-Source association.
Attaching requires Project write and independent resource-sharing authority.
Requires the companion Project-sharing backend release. Ownership transfer remains a separate capability; this version does not execute a Project move. See Projects.
0.54.0 — Curated AWS starter guide
The bundled skill routes “connect AWS to DreamLake” to a first-time setup guide and a reviewed, checksum-verifiable starter download. It reuses the existing AWS Terraform template, separates infrastructure from enrollment and worker readiness, and provides a basic tools image with reusable Docker/Kubernetes SDK profiles and a reconnectable smoke command. See Connect AWS.
The source recipes repository remains private; only explicitly selected, reviewed files are distributed publicly. Local configuration, keys, tokens, Terraform state and logs are excluded. Organization-specific copies should keep secrets in Vault and reference them from private configuration.
Recipe validation covers local Docker/Kubernetes execution with SDK 0.5.0 and Nymph 0.1.17. Live AWS provisioning, paid jobs and arbitrary multi-node shared storage are separate acceptance steps; a generated handoff does not claim readiness.
0.52.2 — User-configured managed agent setup
The bundled agent skill and provider reference explain the optional agentSetup
launch layer: user-pinned Node/Codex/Claude versions and explicit Codex daemon
startup. The matching backend release is required; this CLI update alone cannot
add server support. The shared bootstrap no longer chooses workload harnesses
for new launches. Existing machines and persisted retry receipts are unchanged.
The CLI command surface and readable enrollment behavior remain unchanged.
0.52.1 — Readable host registration output
dl hosts enroll prints a readable registration summary by default,
including verified online or pending state and recovery identifiers. Errors use
text too. Add --json for a structured receipt without request-ID progress
output. JSON fields, readiness checks and exit codes are unchanged. --quiet
suppresses progress while retaining the final result. These defaults also appear
in command help and the bundled agent skill.
0.52.0 — Direct macOS host enrollment
hosts enroll --local supports macOS through a private per-user LaunchAgent,
with the same authorization, identity and verified-online checks as Linux.
Retries preserve the key and avoid restarting an unchanged healthy agent.
macOS requires Python 3, OpenSSL Ed25519 support and an active graphical login;
Homebrew paths are included for uv. No SSH server, sudo or system daemon is
used. See Host enrollment
for prerequisites, recovery, session availability and validation limits.
0.49.0 — Personal AI AWS setup and explicit state snapshots
provider create --provider aws-jump-worker distributes the editable Terraform
modules, typed inputs and enrollment mapper through the existing create → plan →
apply flow. The default controller is your existing enrolled Personal AI computer,
which can be outside EC2; only an explicit choice adds a separate EC2 jump.
An exact distinct EC2 worker remains required. Reentry preserves edits, and the
existing ec2 template remains compatible. See Provider lifecycle.
vault terraform backend|backup|restore supports explicit personal-Vault backend
references and encrypted-at-rest snapshots of selected private files. Restore
writes a new isolated snapshot only, with revision, lineage, serial and hash
checks. The locked/versioned remote backend remains authoritative; snapshots do
not replace Terraform locking or automatically upload active state. POSIX file
permissions and the 64 KiB serialized Vault envelope limit apply. See
Terraform state and Vault.
This release preserves authenticated enrollment and verifies existing enrollment before reuse. Automatic new-instance enrollment remains a separate interface dependency; an instance identity document alone never approves a new key.
0.45.0 — Scenes across CLI, API and docs
Use dl scene push|create|list|pull|compose|delete|restore. The legacy
env command remains an alias. Requests now use /namespaces/:slug/scenes,
and receipt links use /<namespace>/scenes/<name>. Existing storage, layer
formats and login environments remain compatible. See Scenes.
0.44.2 — Remove the old saved-version command group
The old notes version create/list/read paths are removed. Use
note tag NOTE LABEL, note hist NOTE, and
note read NOTE --version VERSION_ID. Both note and notes work.
0.44.1 — Tag, history and saved reads
Use dl note tag NOTE LABEL, dl note hist NOTE, and
dl note read NOTE --version VERSION_ID for saved checkpoints.
note aliases notes; the original notes version create/list/read commands
remain compatible. Saved reads refuse conflicting live-read options before
network access. See Saved versions.
0.44.0 — Saved Memo versions
Save immutable checkpoints on the existing Memo with notes version create,
list them with notes version list, and read retained text with
notes version read. Creation verifies one coherent full read and submits its
content hash; --hash pins a reviewed read, and 409 note_changed stops
without retrying. Optional tags, summaries, parent ancestry, namespace, JSON,
dry-run and pagination are supported. These commands neither copy the Memo
nor modify its live body. See Saved versions.
0.42.0 — State your purpose while lingering
notes read --linger --intent "…" (and notes visit --intent "…") publishes
a one-sentence, self-reported purpose with your presence session — for example
--intent "I'm reviewing this sequence to make the pacing clearer." The
sentence appears on your agent badge's presence card in the web app, alongside
the owner attribution and the observed activity label. The purpose rides the
join only: heartbeats preserve it, leave or lease expiry removes it, and a
later join never resurrects an expired purpose. The server trims the text and
rejects empty values and more than 280 Unicode code points. Requires a server
with the intent-enabled presence API; older servers reject the field with
invalid_presence. See Collaboration.
0.41.0 — Embedding model control, and splat directories get their viewer
library push --embed now takes --model <name> and reports which encoder
actually ran:
This matters because DreamLake semantic search only fuses a library whose
sidecar was embedded in the server's query space (SigLIP2,
open_clip/ViT-B-16-SigLIP2/webli); any other model leaves the library on
keyword-only search, by design and with no error. Previous CLIs passed no
model at all, so with dreamlake 0.24.x — which still defaulted to CLIP —
--embed produced a sidecar the server quietly ignored. dreamlake 0.25.0
and later default to SigLIP2; --model siglip2 pins it explicitly, and
--model clip is the legacy escape hatch. A sidecar outside the query space
now warns, with both fixes, and still completes the push.
Zero-config discovery also recognizes compressed splat directories. A
PlayCanvas SOG asset (meta.json plus its WebP planes) or SOG-LOD
(lod-meta.json with one set per node subdirectory) used to land as
kind: file with no entry, so the web app showed a file list instead of the
3D viewer. Both are now detected as kind: splat with format: sog / lod,
and the detected format reaches the manifest the viewer dispatches on. A
dreamlake.yml kind:/format: still overrides detection.
See Libraries.
0.40.0 — Cached library manifests
library stat, info, pull and push now keep a local copy of the
remote wire manifest under ~/.dreamlake/cache/libraries/manifests/,
keyed by the library's revision counter. A read against an unchanged
library costs one small catalog request instead of a full manifest
download (tens of MB on large libraries). Only the latest revision per
library is kept, under a 1 GiB total cap with LRU eviction; a corrupt
cache entry is re-fetched silently. --verify on stat, info and
push re-downloads the manifest, bypassing the cache.
0.39.2 — Clearer full-upload option
Use artifact push --full to upload the entire file in the original format.
Incremental uploads remain the default. --no-incremental continues to work
as a hidden compatibility alias.
0.39.1 — Incremental artifact uploads by default
artifact push now reuses unchanged compressed chunks automatically.
Use --no-incremental for the original single-blob format, including older
self-hosted viewers. Explicit --incremental remains supported.
See Artifacts.
0.37.1 — Staging receipt web links
Receipt open: URLs printed against the built-in staging environment now
target the web app (https://staging.dreamlake.ai/…) instead of the API
host (staging-api.dreamlake.ai), across env, artifact, workflow
and share receipts. Custom API hosts are still never guessed: only a
leading api. label is stripped, anything else prints unchanged. Released
CLIs (≤ 0.37.0) print the staging API host; setting
DREAMLAKE_WEB_URL=https://staging.dreamlake.ai is a working workaround
there. See Environments.
0.37.0 — Inline image upload
- Add
notes media upload <file>: upload an image or video and print its embeddable URL directly. Saved login credentials are reused;--jsonis optional. Media URLs allow access to anyone holding them; private memo attachments remain separate.
0.36.0 — Agent skill setup and update reminders
-
After CLI updates, remind users when installed Codex or Claude Code skills differ from the new bundle, with the exact update command. Reminders preserve local edits, stay out of automatic JSON/piped runs, and appear once per skill path per CLI version.
-
dl initguides agent selection and project/global skill installation. -
skill installandskill listsupport--agent codex(.agents/skills) and--agent claude(.claude/skills, the compatibility default). -
Top-level
-h,init -h, and skill help include setup examples generated from the agent skills guide. Existing modified skills still require--force.
0.35.0 — Env layers v3 component grammar
dreamlake.layers.json moves to schema dreamlake.env-layers/v3: every
stack entry is one flat op — Merge / Attach / Update / Remove /
Patch — with src as a single string (ns/name[@v] registry ref, or a
./-prefixed local path). Attach takes an identity-root key instead
of a prefix (one entry per placement); Update carries inline sparse
opinions (key addresses an element, every other prop is an MJCF
attribute); Remove is first-class. env compose requires
dreamlake ≥ 0.23.0 on the composing machine (pip install "dreamlake[compose]"). v2 stack files are refused with a migration map;
composition semantics are unchanged. See the
Env Layers Reference.
0.34.4
Read literal Markdown inside agent markup without added HTML or Unicode escaping. Accept the text transport and use trusted address metadata. Bundled skills explain literal source edits and unified diffs without manual inline-DFF escaping.
0.34.3 — 2026-09-28
- Fix native Memos patches read from redirected stdin silently submitting empty input; reject empty patches before sending.
- Preserve server patch error details and explain that legacy conditional edits require the quoted ETag rather than an RTC revision.
0.34.2 — Hierarchical list addresses
Memos references now describe standard ul/ol list prefixes and one li
item type. Addresses include their parent list/item paths while retaining the
shared section counter. Checkbox state remains an attribute. Existing 0.34.1
read commands already accept these server-issued IDs.
0.34.1 — Shared list ordering
Annotated Markdown includes list containers alongside paragraphs and items.
The server assigns p, l, li and cli IDs from one section counter; use
returned IDs and retain the snapshot revision for focused reads and edits.
0.33.0 — Addressed Memos reads
dl memos read can pin a retained snapshot with --at, inspect its
outline with --toc, and retrieve a section or exact tagged element with
--section and --tag. HTML reads expose revision-local section, paragraph,
and list-item IDs with source character and line ranges. --view markdown
adds address hints while preserving the original Markdown text. --since
continues to default to line diffs, and linger retains its source/SSE contract.
0.32.4 — Share-link management
Memos and artifacts now expose share get/create/revoke and visibility commands
for existing resources. Memos also support accepted-access listing/removal and
optional revocation of accepted grants. Link inspection never enables sharing.
0.32.3 — Task-based Memos examples
Memos help now demonstrates finding and reading a memo, previewing a precise
wording change, verifying it, and collaborating with distinct agent identities.
Normal reads use no JSON or view flags. Patch help retains revisions from normal
text output, and the local-editor recipe avoids zsh’s read-only status variable.
0.32.2 — Memos quick-start help
dl memos --help now includes practical examples for finding, reading,
following, and creating memos, inspecting sections and attachments, and finding
revision-safe edit recipes. The same examples ship in the bundled CLI skill.
0.32.1 — Highlight handles and hover guidance
The bundled skill uses canonical public user handles for highlight attribution and documents the minimal hover/focus popover, without an extra icon. Exact profile resolution is self-declared attribution; legacy names remain unresolved. The revision-safe matching-text example uses the same existing CLI commands.
0.32.0 — Agent selection by text
notes select --text "passage" --note NOTE resolves literal source and publishes
an agent selection through RTC. Ambiguous matches require --section or
--occurrence (-o); negative values count from the end (-o -1 selects
the last match). Stale hashes fail without guessing. CSS lookup remains compatible.
Section mode requires the server update adding a source hash and global
code-point range. Plain-text receipts include the selected text, scope, resolved
match and expiry times. JSON remains opt-in for explicit integrations.
0.31.3 — Highlight annotation guidance
The bundled CLI skill documents user and comment highlight metadata, the
shared inline/sidebar comment UI, click-to-edit, and a tested revision-safe
matching-text example. No CLI command or storage behavior changes.
0.31.2 — Clearer participant names
- Show people as
@usernameand agents by their configured name, without surrounding quotes. Keep quotes around selected text.
0.31.1 — Simpler Memos notifications
- Show names, actions and quoted selections in default linger output. Keep IDs, connection details, offsets and source hashes in JSON.
- Label agents and keep cursor moves, selection clears and syncing states silent in text. Print one timestamp per nonempty batch. JSON retains every state change; throttling is unchanged.
- Add notification examples to the collaboration guide and
notes read --help.
0.31.0 — Live Memos selections
-
Complete the simplified session interface:
presence <note>reads the roster;visitregisters once;read --lingermaintains the session. Remove the oldpresence <note> <action>and--watchcontrols. -
notes read --lingerobserves server events instead of polling the memo and roster. Requires the matching Memos events endpoint. -
Reports human selections and clears with source hashes and Unicode code-point offsets; unchanged selections and lease heartbeats stay silent.
-
Coalesces the latest selection per participant, limits output with
--throttle(default 2s), and debounces content diffs separately. -
Agent activity highlights expire after 8s and disconnected agent presence after 60s. Human selections clear on deselection, editor blur, or departure.
-
Stream gaps and stalled output fail explicitly rather than silently reconnecting.
0.30.0 — Layout control
- Added explicit local-browser layout listing, inspection, read-only resolution and guarded application.
- Agents select a browser page and layout ID; declarative requests use the page’s shared controller and authorization.
- Added loopback transport validation, JSON-only request arguments, timeout uncertainty reporting, and embedded command-help recipes.
0.26.2 — per-request EXACT patches
Memos command handlers now allow stdout to drain before process exit, preserving large piped JSON/source responses. Regression tests cover delayed pipe readers with more than 128 KiB of Unicode content.
Memos v2 patches default to ordinary native CRDT synchronization against the
original snapshot identified by --base-revision. --exact explicitly selects EXACT mode for that request; --if-match is a compatibility alias. The CLI never fetches a newer baseline
to hide a conflict, and rejected requests leave local drafts and baselines intact.
The matching Memos v2 API retains original RTC identities. This release also
includes complete mapped HTML reads with canonical-source/hash/revision checks.
Use --legacy explicitly with older servers. Package and deployed acceptance
receipts are tracked in workspace #706.
Versions 0.26.0 and 0.26.1 are superseded candidates. The 0.26.0 workflow was cancelled before publishing the npm wrapper or moving native channels; immutable versioned R2 objects and platform package uploads remain. Active install channels stayed at 0.25.0. Version 0.26.1 was never published, and neither candidate docs site was promoted.
0.26.1 — superseded, never published
notes read --view html emits the complete server snapshot without added
headers or newline. Embedded canonical source, identity, SHA-256 and revision
are validated before stdout; --if-match is guarded on both request and
readback. HTML rejects incompatible history, JSON, legacy and slicing options.
These changes ship in 0.26.2 with the matching Memos HTML server contract. Tracked in workspace #706.
0.26.0 — superseded, publication cancelled
Historical candidate: Memos commands changed to the v2 server contract. This candidate was superseded by 0.26.2 and must not be republished. The current MERGE/EXACT contract above replaces its required-guard interface.
Full reads emit source with SHA-256 and opaque revision metadata. Incremental
reads and multiline stdin uploads select inline or line diff. Uploads require
the saved revision, and verification reads preserve that exact token. Explicit
--legacy retains the prior text/ETag interface. Requires the matching v2
server; no package release, deployment, or live verification is claimed.
Tracked in workspace #706.
0.25.0 — Layered env stacks: env compose
dl env compose [stack] materializes a layered env stack —
dreamlake.layers.json, schema dreamlake.env-layers/v2 — into a runnable
env directory. The stack defaults to ./dreamlake.layers.json; -o/--out
names the output directory and --force writes into a non-empty one. The
CLI owns stack shape validation and source resolution: registry refs
({"env": "ns/name[@version]"}) fill the immutable, hash-verified cache at
~/.dreamlake/cache/envs/, so pinned refs with a cache hit cost zero
network, and public envs resolve without login.
Composition semantics (merge / attach / override, URDF import, compile
validation) are delegated to the Python reference engine
dreamlake.envlayer, installable as pip install "dreamlake[compose]"
(dreamlake 0.19.0 on PyPI). DREAMLAKE_PYTHON overrides the interpreter;
otherwise python3, then python. env push/pull/list need no Python.
Push discipline lands with it: env push (and env create) now refuses a
directory whose root dreamlake.layers.json still references local,
unpinned layers — the pushed provenance would not be re-openable.
--push-layers pushes each local layer directory as its own env first
(named by its basename) and stops for pinning + recompose; --allow-local
pushes anyway with the provenance marked non-resolvable.
Deep reference: Env layers.
0.24.7 — Memos revision diffs
dl memos diff <note> --since <etag> compares the current body with a
retained read/edit reference. --json includes both refs; plain output stays
pipeable. Requires the revision-diff server endpoint. Read, diff, and patch
help examples now document preserving and reusing the ETag. These examples
also flow into the generated CLI skill.
The feature merged in #114 without shipping: the published 0.24.6 binary
answers error: unknown command 'diff'. 0.24.7 is the version bump that
ships it. Published on the native channel (latest and stable both resolve
to 0.24.7 on dl.dreamlake.ai); as of 2026-09-23 the npm registry's newest
version is still 0.24.6, so npm users first get notes diff with 0.25.0.
0.24.6 — Memo file uploads no longer crash the native binary
dl memos files upload sent the Bun.file() object itself as the PUT
body. On Bun 1.3.14 on Linux, in a compiled standalone binary, that crashed the
runtime with a SIGSEGV once the response had arrived, when a GET on the same
host had run first — the shape this command takes, because it resolves the memo
before uploading. The body is now Bun.file(path).stream(): the same file, read
lazily rather than loaded into memory. The observed run was against a loopback
server on this machine, not a remote deployment: the upload exited 0 and stored
the expected 2048 bytes there.
Whether the crash reproduces on every upload, or on other runtimes, platforms or
build modes, was not established; the fix was verified on the configuration
above. No Content-Length is set under Bun, unchanged from 0.24.5, but this
release does not prove behavior against a production HTTP/2 endpoint — whether
the HTTP/2 upload hang of 0.23.0 can recur is pending a focused test. Node keeps
its existing createReadStream body.
The DreamDB 0.5.7 upgrade was prepared in 0.24.5, which was not completed as a
release: only two Darwin binaries were uploaded, with no manifest and no npm
publication. It carries forward unchanged here: half-open
[start, end) read ranges translated to inclusive HTTP Range bounds,
nonce-bearing genesis objects, and the requirement to migrate a legacy dataset
before writing to it. No dependency, command, flag or output shape changes in
this release.
0.24.5 — DreamDB 0.5.7 and half-open byte ranges
The bundled @dreamlake/dreamdb moves from ^0.4.0 to ^0.5.7. That release
passes read ranges as half-open [start, end), where the end byte is excluded.
The S3 backend previously forwarded such a range straight into an HTTP Range
header, whose end is inclusive, so every ranged read fetched one byte too
many. It now translates the bound and requests bytes=start-(end - 1).
Because genesis objects in 0.5.7 carry a random nonce, two datasets created from the same schema no longer share a genesis hash. A genesis hash is therefore an object identity, not a schema identity — do not compare one across SDKs to infer compatibility.
Migrate a legacy dataset before writing to it. Datasets written by the older DreamDB stay readable, but this release performs no automatic migration and rewrites no existing store, so appending to an unmigrated dataset with the new SDK is not supported. No command, flag or output shape changes.
0.24.4 — Memos sync and recovery guidance
The bundled CLI skill now explains browser sync states, local-draft recovery, and view-only history. CLI commands still read the server and keep their existing revision checks; they cannot clear a browser-held draft. This release updates guidance and packaging, with no new Memos command or protocol. Publication and fresh-install receipts are recorded in the GitHub release.
0.24.3 — native skills and docs-generated command help
Native binaries now embed all 37 generated CLI skill files. skill list and
skill install work without a checkout or environment override. Installed edits
remain protected; updates require explicit installation and reviewed --force.
Ten command help pages now include 26 command examples generated from reviewed docs,
including revision-checked Memos writes and patches. CI and release builds test
a copied native binary, byte readback, reinstall, conflict refusal and peer preservation.
See the release acceptance checklist.
Publication and fresh-install receipts are recorded in the GitHub release.
Unreleased — affected-entry preview pages
vault kms preview --affected-limit 100 requests one retained-entry metadata page. Use --affected-cursor for explicit continuation. Strict output validation retains only the supported metadata and refuses silent omission by an older server. No mutation or release is included. Guide.
Unreleased — selected-prefix policy preview
vault list --tree --preview-key <ref> adds explicit p preview using the existing
read-only KMS endpoint. Python uses its existing vault.kms.preview method.
The view is counts/blockers, not an affected-entry list or mutation approval.
No activation, migration or move is performed. Guide.
0.22.0 — unpublished release candidate
Adds candidate owner-only interactive metadata browsing and one-page JSON output,
with Python API parity. Actual local HTTP/Mongo and PTY acceptance passed; no
release or deployment claim. This requires the authenticated GET /v1/vault/tree route from backend PR576. That source is merged but not deployed at preparation time; older servers return 404 rather than a fabricated tree. Development memo.
0.21.2 — 2026-09-15
Adds a fixed recovery warning to human tracked-run output when the API reports an unresolved prior-daemon admission. Waiting reports each newer revision once; JSON stays unchanged and terminal results suppress the warning. Queue-mount and Vault behavior from 0.21.1 is retained.
Implementation #88 passed independent review, 1,253 tests and CI. Manual validation: sh scripts/test-run-recovery.sh exercises the real CLI against a loopback HTTP fixture. Source b8aa4e2 is pinned by tag v0.21.2; release preparation #89 is merged. All eight native public binaries match the manifest. All nine npm tarballs match the reviewed generated files, and native/npm latest read back as 0.21.2. The stable channel remains unchanged. A fresh macOS npm install passed reviewed wrapper/native hashes and recovery/queue HTTP checks. Hosted recovery acceptance is separate. Release and manifest.
0.21.1 — 2026-09-15
Published to native downloads and npm. Combines the queue-mount commands from 0.21.0 with the Vault uncertain-write transport fix released in 0.20.2.
Unreleased
-
Record independent closure of the literal OTP/pass/SSH apply criteria from combined scoped receipts and tests; source progress56/72. No runtime or package release. Criterion matrix and limits.
-
Add five runnable synthetic OTP import checks against published Python0.16.1 over real loopback HTTP: per-entry source changes, dropped-response uncertainty and conflict redaction. No runtime change or broad OTP/SSH completion claim. Evidence matrix.
-
Add synthetic OTP import regressions for a later source changing during an earlier upload. Both content replacement and symlink swaps stop dispatch while preserving completed entries. No runtime change or new deployment; audit and recovery boundaries.
-
2026-09-15: CLI 0.20.1 and Python 0.16.1 are published with
keep_alive_s = -1for enrolled user-systemd hosts. Owned bos14 acceptance passed with unchanged process IDs and zero restarts after Python 324.72s and CLI 302.83s idle windows. Existing hosts can use the paired repair commands; preserve the original request ID when reconciling an uncertain response. Publication and live evidence. Reboot survival and completed hosted private execution remain separate open acceptance checks.
0.20.2 — published native transport fix
CLI 0.20.2 disables pooled connection reuse in the native Vault transport so dropped PUT/DELETE responses remain available for explicit reconciliation instead of hidden transport retries. Fresh public native and npm installations passed all 34 HTTP/PTY import checks; nine compiled transport checks also passed. The release preserves concurrent newer package channels; use an exact version when selecting this patch. Publication receipt542 · Audit and recovery limits.
0.21.0 — superseded by 0.21.1
Introduced dl queues mount, mounts, inspect, list, jobs, workers, token and unmount, with explicit namespaces, hidden token input and Vault storage. Native artifacts and npm packages were uploaded, but this pinned source predates the Vault transport fix in 0.20.2. Native channel promotion was held. Use the combined 0.21.1 release to retain the Vault fix. Existing 0.21.0 artifacts remain unchanged.
0.20.1 — 2026-09-15
- Keep enrolled user-systemd hosts available while idle by explicitly setting
keep_alive_s = -1. Existing hosts require re-enrollment with this fix. Paired CLI/Python bootstrap tests parse the generated TOML and verify re-enrollment repairs the old configuration. Published in v0.20.1; hosted acceptance is tracked separately.
CLI source suite: 1,019 passed; typecheck and 33-page docs build passed. All eight platform binaries built. A fresh copied macOS ARM64 binary passed real HTTP enrollment with the unchanged portable bootstrap over a synthetic SSH wrapper; parsed configuration has keep_alive_s=-1. This published patch was based on the previous tag plus the reviewed host fix; unrelated Memos changes on main were excluded.
0.20.0 — 2026-09-15
Adds private repository setup with explicit selected credential mappings and authenticated capability discovery, paired with Python 0.16.0. Published to native downloads and npm from reviewed source f34ca03. All eight native downloads and npm platform binaries match the release manifest; the public npm wrapper matches reviewed source bytes.
dl run --setup setup.json --allow-vault-deliverysubmits a pinned public repository, uv-lock dependencies and explicitly selected env/file mappings to an enrolled host. The metadata file is explicitly selected and bounded; it contains no secret values. Unknown submission outcomes reuse the same request ID and payload.dl runs capabilities <namespace> --jsonreports authenticated server support and limits. Host readiness is verified separately at submission.- Existing password verification/reservation and Task commands remain included. This release does not implement remote password mutation or enable backend private execution.
Paired CLI/Python examples cover submission, discovery, status and cancellation. Private production activation requires the reviewed worker termination fix and fresh acceptance. Validation: 1,019 CLI tests, typecheck and the 33-page documentation build passed. All eight platform binaries built with embedded WASM checks; the native binary reports 0.20.0 with dependencies detached. A fresh isolated registry installation passed the installed binary hash, version and capability-help checks. Public native latest and npm latest/next resolve to 0.20.0. Release and manifest.
0.19.1 — 2026-09-14
Published to native downloads. All eight platform binaries passed public
checksum and size verification. At this historical release checkpoint native latest was 0.19.1. npm accepted the
packages, but macOS arm64 was still processing, so npm latest remained
at 0.19.0. Version 0.20.0 above is now published and verified on both channels.
- Task commands accept session scope defaults.
- CLI docs link to the DreamLake and Lakeshore documentation tabs.
Password APIs — release status reconciliation
CLI tag 0.19.1 includes password verification and reservation source. Python 0.16.0 is published to PyPI with matching public artifact hashes and a fresh registry version/API check; matching hosted password acceptance is still required. The old CLI 0.19.0 candidate in PR #66 is superseded and must not be republished.
vault password-rotation reserve|show|read|start|cancel|confirm has paired Python methods. Private metadata inputs and strict response validation keep ordinary operation output free of passwords; selected recovery reads are explicit. Real HTTP/native Mongo cross-client target/jump metadata flows passed. Requires backend #370; remote mutation and rollback resolution remain unfinished. Guide.
Password-only verification
vault verify-password and Python verify_host_password verify one saved password with isolated SSH and private askpass IPC. Candidate native/npm/Python real target/jump password success/denial checks passed with independent cleanup. Password rotation and fresh installed-client/hosted enrollment/KMS acceptance remain separate. Guide.
0.18.0 — 2026-09-13
Adds vault rotate-key preparation, pinned API requests, isolated SSH transport and recoverable phase journals. Candidate CLI/Python target and jump rotation passed real SSH acceptance with independent cleanup. CLI 0.18.0 is published to npm and native downloads, paired with Python 0.15.0. Published CLI 0.18.0/Python 0.15.0 hosted staging acceptance passed four target/jump rotations and committed-response-loss recovery, followed by verified owned cleanup (examples #34). Production acceptance remains separate. The frozen release excludes the password-only verification changes above. Development evidence.
Quoted target and jump SSH arguments beginning with -p are preserved rather than interpreted as the vault prefix.
0.17.0 — 2026-09-13
Published to npm and native downloads. Paired Python 0.14.0 is published. All eight public native artifacts and all nine public npm tarballs match the frozen reviewed release. A fresh registry installation with scripts disabled reports 0.17.0.
- Personal owners can inspect trusted prefix KMS policies, preview retained records, activate empty prefixes, and explicitly start/resume populated-prefix migrations. Immutable request IDs recover uncertain outcomes; explicit prefixes are checked before resuming. The SDK never prompts or advances migration in the background.
- Conditional host-binding replacement and owner-only operation recovery retain both credential identities until explicit cleanup. This metadata API does not install or revoke remote SSH keys; remote rotation candidates are excluded.
Migration requires backend #359. The operator migration flag defaults to false and must remain disabled until all writers enforce policy epochs. Installing this package does not enable migration, configure customer grants, or prove hosted acceptance. Paired KMS guide.
0.16.0 — 2026-09-13
Published to npm and native downloads. Paired Python release: 0.13.0. The matching backend is required; package validation does not establish hosted deployment.
- HOTP import defaults inactive. Explicit counter ownership, encrypted atomic issuance and a private immutable request file support safe retries; source pass registrations are never modified. See Vault operations.
- Metadata listing follows bounded pages; explicit
--limit/--cursorsupports one-page consumers. Retired inclusion remains owner-only. - The npm launcher preserves explicitly selected target/jump password descriptors (private files/real pipes, maximum descriptor 1024), including its permission repair retry, while closing unrelated descriptor gaps.
vault unbindreleases an exact personal retention reference while preserving active secrets and making no claim of remote SSH revocation.
Source: HOTP #50, pagination #52, and unbind #49, plus descriptor fix #53. A separately copied candidate launcher was verified against published native 0.15 and staging, with target/jump saving and cleanup. That is not publication evidence for this 0.16 package. All eight published native artifacts match the reviewed manifest; a fresh npm installation reports 0.16.0.
0.15.0 — 2026-09-13
Selected post-enrollment SSH password/private-key saving and account-owned host bindings are included. Target and jump credentials are selected separately; interactive saving defaults to N, quiet grants no consent, and automation uses explicit selections and protected descriptors. Enrollment success survives a saving failure; uncertain writes and saved-but-unbound entries retain recovery metadata. CLI/Python examples.
Paired Python release: 0.12.0. Source implementation is merged in CLI #47, Python #34, and backend #336. CLI publication is verified on npm and native downloads; all platform binaries match the release manifest and latest points to 0.15.0. Python 0.12.0 is published on PyPI/GitHub. Hosted acceptance remains pending. Earlier bos14 checks used a synthetic source snapshot, not these release artifacts. See the Vault Dev Note.
Unreleased — populated-prefix KMS migration
vault kms migrate, bounded resume, and shared status have paired Python methods. Preview includes retained entry/write/HOTP receipt counts. Metadata output strips ciphertext/KMS identifiers and uncertainty retains the original operation ID. Source candidate only; package and hosted verification are pending.
Password reservation candidates also acknowledge retained-record schema 2 on KMS migration start/resume and preserve separate password-snapshot/total counts in metadata. Compatible backend deployment must precede these commands. Source validation: target/jump cross-client reservation and snapshot reads over real loopback HTTP/Mongo; published CLI 0.17/Python 0.14–0.15 are safely gated, new clients advance the same migration. No remote password changes are included.