domino-cli
Use the Domino command-line client (domino login, run, create, init, get, restore, sync, upload, download, download-results, upload-dataset, create-snapshot, create-dataset-from-snapshot, help, version) and the Domino R package (library(domino) with domino.login, domino.get, domino.run, domino.download, domino.sync, domino.init, domino.upload) that wraps it. Covers installing the CLI graphically or headless on Linux, signing in with a browser or the device-code flow over SSH, working on a Domino File System project from a laptop, large uploads to Datasets, downloading run results, moving a project between deployments, force-restoring a broken local project, and proxy settings in domino.vmoptions. Use when the user mentions the Domino CLI, a `domino` shell command, syncing project files from a laptop, the Domino R package, or running Domino jobs from R or a terminal. Not the `dom` SSH tool kit and not python-domino.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 5
- Forks
- 4
01 前言 Front Matter
- name
- domino-cli
- description
- Use the Domino command-line client (domino login, run, create, init, get, restore, sync, upload, download, download-results, upload-dataset, create-snapshot, create-dataset-from-snapshot, help, version) and the Domino R package (library(domino) with domino.login, domino.get, domino.run, domino.download, domino.sync, domino.init, domino.upload) that wraps it. Covers installing the CLI graphically or headless on Linux, signing in with a browser or the device-code flow over SSH, working on a Domino File System project from a laptop, large uploads to Datasets, downloading run results, moving a project between deployments, force-restoring a broken local project, and proxy settings in domino.vmoptions. Use when the user mentions the Domino CLI, a `domino` shell command, syncing project files from a laptop, the Domino R package, or running Domino jobs from R or a terminal. Not the `dom` SSH tool kit and not python-domino.
- compatibility
- Domino 6.3 and Domino Cloud. CLI builds older than 6.2.3 can no longer sign in; download the installer from the deployment you use. The R package (CRAN domino 0.3.1, 2017) shells out to the installed CLI and is documented as possibly outdated.
02 资源文件 3
- 参考文档CLI-INSTALL.md4.9 KB
- 参考文档CLI-REFERENCE.md4.6 KB
- 参考文档R-PACKAGE.md5.0 KB
03 SKILL.md 正文
Domino CLI and R package
Applies to Domino 6.3 and Domino Cloud.
Product pages: https://docs.domino.ai/cloud/reference/cli (index, install, reference, download
files, force-restore, move a project, proxy) and
https://docs.domino.ai/cloud/reference/r-package/domino-r-package. The 6.3 pages are the same
content under /6.3/.
What it is, and what it is not
| Tool | Use it for | Not for |
|---|---|---|
Domino CLI (domino) |
a laptop or server working on a Domino File System project: pull and push files, start a Job, download results, bulk-upload to a Dataset; on a Git-based project, the DFS-backed Artifacts | REST automation (use the API with a token), Git-based project code (use git) |
R package (library(domino)) |
the same CLI commands from an R console | calling the Domino API from R (write httr calls against the API instead) |
dom tool kit |
SSH into a running Workspace for local IDE development | project file sync |
| python-domino, REST | automation and integrations | interactive file sync |
The CLI is a Java application (the headless install needs a JRE); it keeps its project link in
.domino/config.json and its proxy settings in domino.vmoptions.
Install and sign in
- Account > Download CLI in the Domino UI, pick the OS, run the installer (macOS prompts
for admin credentials; cancel and add
/Applications/dominotoPATHyourself if you lack them). Headless Linux:apt install openjdk-8-jre-headless,wget https://<domino-url>/download/client/unix -O /tmp/domino-install-unix.sh,sh /tmp/domino-install-unix.sh. - Close and reopen the terminal, then
domino login https://<your-domino-url>. The CLI opens a browser to the Domino sign-in page and receives the authorization itself. - No browser on this machine (SSH, a Workspace)?
domino login --device https://<your-domino-url>prints a verification URL and a short code; open it on any device, sign in, Grant Access. The code expires quickly; rerun the command for a new one.
A CLI older than 6.2.3 uses a retired authentication client and cannot log in; reinstall from
Download CLI. After domino login the CLI keeps its own session; there is no token or
API-key login for the CLI. Full install notes, OS support and proxies:
CLI-INSTALL.md.
Everyday workflow (DFS project)
domino get owner/project # first copy of an existing project; creates ./project
cd project
domino run train.py 20 # upload changed files, start a Job with arguments, return at once
domino run --wait train.py # block until the Job ends
domino run --direct "pip freeze | grep pandas" # shell command instead of a file
domino run --tier "Large" train.py # hardware tier by name
domino download # pull results and collaborators' changes
domino sync # download then upload
domino upload -m "add data" # push without starting a Job
domino download-results --filter 'results/*' 42 # files from run number or id 42 into results/run-42
File and run commands act on the project folder you run them in (the CLI keeps the link in
.domino/config.json); domino get and domino create make that folder. domino init [name]
turns the current folder into a new project without uploading; domino create [name] makes a
new folder and project; domino restore reconnects a folder (for example a git clone) to its
project. --owner <org> on create and init assigns the project to an organisation. --no-sync
runs server-side code without uploading local changes; --local records a run that executes on
your machine. Every command, flag and example: CLI-REFERENCE.md.
Datasets from the CLI
domino upload-dataset --fileUploadSetting Overwrite --targetRelativePath raw/2026-10 owner/project/dataset-name /local/folder
domino create-snapshot owner/project/dataset-name
domino create-dataset-from-snapshot owner/project/dataset-name 3 new-dataset-name
upload-dataset overwrites existing files unless --fileUploadSetting Ignore|Rename (values are
case-sensitive). Tune big uploads with DOMINO_UPLOAD_CHUNK_BYTES (default 3 MB) and
DOMINO_UPLOAD_THREADS (default 8). Quotas and limits: domino-datasets.
R package in one screen
install.packages("domino", repos = "http://cran.r-project.org", type = "source")
library(domino)
domino.get("owner/project") # or setwd() into an existing project folder
domino.run("myScript.R", 1, "someString") # arguments become the script's command-line args
domino.download() # bring results back, then load() them
domino.sync(); domino.init("name"); domino.upload("message")
CRAN domino 0.3.1 (2017) runs the installed CLI with system(), so install and log in with the
CLI first (the browser or device flow above). Its domino.login(username, password, host) feeds
a username and password to the CLI's old interactive prompt and may fail against the current
CLI; prefer a terminal domino login. Exported functions,
signatures and limits: R-PACKAGE.md.
Pitfalls
- The CLI syncs the Domino File System. On a Git-based project that is the Artifacts section; code goes through git and Jobs through the UI or API (domino-jobs).
- "blob file not found" on
domino run: rundomino syncfirst. - More than about 1,000 files in one
uploadcan time out; upload in batches. - "too many open files" during
sync: add an empty.noLockfile at the project root. - Keep files out of sync with
.dominoignoreat the project root;.git/is always ignored. - Broken local metadata:
rm -rf .dominothendomino restore(force-restore); files on the server that are missing locally come down, local changes go up on the nextsync. - Moving a project to another deployment copies only the latest files, never history or collaborator settings.
Related skills
- domino-projects: DFS versus Git-based projects
- domino-datasets: Datasets, snapshots, quotas
- domino-jobs: what a run becomes, logs, scheduling
- domino-workspaces: the
domSSH tool kit for Workspaces - domino-python-sdk, domino-api-intro: API automation instead of the CLI
04 同仓库更多 Skills
tags-and-properties
Manage Domino tags and properties via the Tags (Taxonomy) API at /api/taxonomy/v1. Covers namespaces and tags (create, list, update, deprecate, delete; tag entities such as projects, models, datasets, apps, project templates, NetApp volumes, environments; query by tag; autocomplete; merge; CSV import/export) and properties (typed metadata fields - text, number, date, boolean, url, user, organization, select, multi_select - with per-entity values, groups and versioned entities like model_version/app_version). Use when organizing entities with tags, building hierarchical namespaces, defining typed metadata fields, setting property values, finding entities by tag, bulk-tagging during onboarding, or migrating a taxonomy across environments.
netapp-volumes
Work with Domino Volumes for NetApp ONTAP (NetApp Volumes) - shared, multi-terabyte storage with near-instant snapshots. Covers creating volumes, attaching them to projects, mount paths (/mnt/netapp-volumes/ or /domino/netapp-volumes/), snapshots and tags, roles, deletion, mounting volumes in jobs, and the NetApp Volumes REST API (/remotefs/v1). Use when managing large-scale shared data, taking fast no-copy snapshots, or integrating NetApp ONTAP storage with Domino.
domino-workspaces
Work with Domino Workspaces - interactive sessions running Jupyter, JupyterLab, VS Code or RStudio on a hardware tier with a compute environment. Covers launching and configuring a Workspace, what persists across stop and resume, file paths and syncing for DFS and Git-based Projects, package and home-directory persistence, SSH access from a local IDE, the Workspace API routes, and troubleshooting. Use when setting up or debugging an interactive development session in Domino.
domino-ui-bootstrap
Bootstrap or retrofit a Vite + React 18 + TypeScript project so it uses the Domino design system (`@dominodatalab/extensions-tools`). Scoped to a **fully standalone SPA frontend for a Domino application or extension**, not snippets, library additions, or work inside an existing Domino monorepo package. Use whenever the user wants to create, scaffold, refactor, retrofit, or set up such an SPA (a React app, web app, frontend, UI, or extension) that should "look like Domino", use Domino components, follow the Domino design system, or integrate with the Domino platform, including when they mention DominoThemeProviderDecorator, extensions-tools, or base-components without saying "Domino". Also use to make an existing standalone React/Vite project "Domino-styled" or add Domino theming. Handles React 18 / react-router 5 pinning, Storybook MCP registration, theme provider wiring, and build verification.
domino-trace-setup
Set up GenAI tracing for an LLM or agent application in Domino by checking the Domino SDK and MLflow requirements (the DSE needs nothing installed), then adding a tracing_setup.py helper, span evaluators, a config.yaml, and @add_tracing / DominoAgentContext wiring. Use when the user asks to add tracing, observability, or evaluation to an agent or LLM app running on Domino.
domino-rust-apps
Build a Rust web app (axum) in Domino and ship it as a Domino App that starts from a prebuilt binary. Covers installing a pinned Rust toolchain into a Compute Environment with rustup, Cargo project defaults (edition 2024, rust-toolchain.toml, Cargo.lock, Clippy pedantic, rustfmt, cargo-nextest, cargo-deny), rust-analyzer for the IDE and coding agents, check hooks, calling Domino as the viewer with extended identity propagation, dev and release build profiles, keeping target/ out of Git and Domino storage, and an app.sh that runs the binary in App Preview and deployments without compiling. Use when the user wants a Rust app, API, dashboard or Proa site on Domino, a performance-sensitive or correctness-critical App, or asks to set up Rust, cargo, Clippy, nextest or rust-analyzer in a Domino Workspace or environment.