DreamLake

ML experiment tracking for robotics and embodied AI. Record, store, browse, and search multimodal episode data — video, audio, tracks, logs, and parameters — from one CLI, one Python SDK, and one dashboard.

Install

One command, and there is no runtime to install first. The dreamlake CLI is a single native binary that lives in your home directory and keeps itself up to date.

curl -fsSL https://dl.dreamlake.ai/install.sh | bash

irm https://dl.dreamlake.ai/install.ps1 | iex

powershell -NoProfile -Command "irm https://dl.dreamlake.ai/install.ps1 | iex"

Then open a new terminal and check it worked:

dreamlake --version

Platforms, release channels, version pinning, troubleshooting, and uninstall steps are in the install reference at the bottom of this page.

Your first episode

The walk-through below takes about five minutes. Every command assumes dreamlake is on your PATH.

Authenticate

dreamlake login

Opens your browser for OAuth device auth and stores a token locally — you only do this once per machine. On headless machines, add --no-browser to get a QR code instead. Point at a self-hosted server with --url <server>.

Upload

dreamlake upload ./run01.mp4 \
  --episode alice@robotics:run-042 \
  --to /camera/front

That single command chunks the file, uploads it to S3-backed storage, registers the asset on the server, and (for video) triggers HLS splitting — the episode is immediately browsable in the dashboard. File type is auto-detected from the extension. Large files are chunked (10 MB parts, 4 parallel workers) and uploaded via S3 multipart, so an interrupted upload resumes where it left off.

List and download

dreamlake list --episode alice@robotics:run-042
dreamlake download --episode alice@robotics:run-042 --from /camera/front -o ./video.mp4

Organize with bindrs and datasets

A bindr is a curated collection of files matched by glob; a dataset groups bindrs into a training-ready unit:

dreamlake create bindr "front-camera" --project robotics@alice --episode "2026/04/*"
dreamlake create dataset "training-v1" --project robotics@alice
dreamlake update dataset "training-v1" --project robotics@alice --add "front-*"

See the CLI Reference for the full create / update / delete / list surface.

Episode syntax

The --episode flag everywhere uses [namespace@]project[:episode]:

Environment variables

How it fits together

dreamlake CLI  /  Python SDK
    ├── Upload file ──→ BSS (S3 storage, HLS splitting)
    └── Register asset ──→ DreamLake Server (catalog, auth)
                              ├──→ Dashboard (browse, render, share)
                              └──→ Qdrant (semantic search)

Explore the docs

Ready to go deeper? Jump straight to the Architecture overview.

Install reference

Everything below is the long tail of installing and maintaining the CLI. You do not need any of it to get started.

Supported platforms

32-bit Windows is not supported. Inside WSL, use the Linux command rather than the PowerShell one — you are installing into the Linux side.

Staying up to date

At most once every four hours, a command may start a short detached background process that checks for a new release and installs it; the new version takes effect the next time you run a command. To update right now:

dreamlake self-update

Release channels

latest (the default) gets every release as it ships. stable trails by about a week and skips releases with known regressions.

dreamlake self-update channel stable   # switch channel
dreamlake self-update                  # apply it

Pin a version

Asking for an exact version pins it: auto-update stops until you choose a channel again. This is what you want in a CI image or when a release regresses.

Windows (PowerShell) tab: On Windows, pass the target through the script block:

curl -fsSL https://dl.dreamlake.ai/install.sh | bash -s 0.3.0
dreamlake self-update 0.3.0            # or, once installed
dreamlake self-update channel latest   # unpin and resume updates

& ([scriptblock]::Create((irm https://dl.dreamlake.ai/install.ps1))) 0.3.0

dreamlake self-update --status shows whether you're pinned.

Turn updates off

Troubleshooting

dreamlake doctor prints where the binary lives, which version the launcher points at, your channel, and the last auto-update result — no network calls, no session started.

command not found after installing. The installer appended to your shell rc but the current shell predates it. Open a new terminal, or:

export PATH="$HOME/.local/bin:$PATH"

dreamlake still runs an old version. Something else on your PATH answers to the same name — usually an npm install of the CLI, or the retired Python console script. The installer warns about this, and doctor names the file under on PATH:. Check with:

which -a dreamlake

Then remove the other one, or put ~/.local/bin ahead of it:

npm uninstall -g @dreamlake/dreamlake-cli     # if it came from npm

This one is worth ruling out first, because it does not look like a failure: the old binary keeps answering and every command appears to work.

From source

For working on the CLI itself:

git clone https://github.com/dreamlake-ai/dreamlake-cli.git
cd dreamlake-cli && pnpm install
pnpm cli --help

Uninstall

Windows (PowerShell) tab: On Windows:

rm -f  ~/.local/bin/dreamlake
rm -rf ~/.local/share/dreamlake ~/.local/state/dreamlake ~/.dreamlake

Remove-Item "$env:USERPROFILE\.local\bin\dreamlake.exe" -Force
Remove-Item "$env:USERPROFILE\.local\share\dreamlake" -Recurse -Force

Add rm -rf ~/.config/dreamlake to also drop your saved logins. On macOS and Linux, remove the # added by the dreamlake installer block from your shell rc; on Windows, drop %USERPROFILE%\.local\bin from your user Path in System Properties → Environment Variables.