Who is who can run it. Everyone means anyone signed in, limited by their role. Admin means a Workspace Admin. A command you aren't allowed to use is refused by Data Visions with the reason.
Changes marks commands that change something in your workspace (or, for websites, on the public internet). Everything else only reads.
Local commands work on files on your computer and don't need you to be signed in.
Everything else acts in the workspace shown by dv dev status. Check it before any command that changes things.
<CODE> is a module code such as TOOL_CALIBRATION. [folder] in square brackets is optional.
Every command has --help for its full list of options. Many list commands take --json for machine-readable output.
Runs the same checks the platform runs on upload, on your own copy. Each finding shows where, what, why and the fix. Exits with an error when there are errors.
--json, --include-info, --marketplace (also fail on anything that would block a listing)
Local
dv modules scan <folder>
Security scan, with the same scanners and severities as the platform. Critical findings block a deploy; high findings block a Marketplace listing.
--json
Local
dv modules rules
The review rules (R1 to R11) every module is built and reviewed against.
--json
Local
dv modules review <folder>
Runs the full module check without deploying: validation, security scan, vulnerable libraries and the AI code review. Takes a minute or more. A deploy of the same files reuses the result.
--json
Admin
dv modules escalate <sha256>
Appeals a build the module check blocked to Data Visions staff, who approve that exact build or reject it with notes. For findings that are wrong, not for skipping real fixes.
All of these change your workspace and need a Workspace Admin.
Command
What it does
Main options
dv modules deploy <folder>
Checks the module on your computer, uploads it, runs the module check, registers the new version as owned by your workspace and restarts your workspace's modules with it. Existing subscribers get the new version.
--subscribe <your-workspace-slug> on the first deploy, so the module appears for your people. --no-promote stops after the upload and the server's checks.
dv modules promote <CODE>
Registers your latest checked upload. deploy does this for you.
--version
dv modules update <CODE> [CODE...]
Moves your installed copy to the newest listed version and restarts your modules. Name two modules to update them together when their libraries depend on each other.
--discard-fork throws away your own changes to a Marketplace module (can't be undone)
dv modules data-migrations <CODE> --retry
Runs the pending data migration steps now, starting at a failed one, after you fixed what made it fail.
The version in module.json must go up with every deploy: a version that's already stored with different files is refused. Without --subscribe, a first deploy registers the module but nobody sees it in the sidebar. You can only subscribe your own workspace. See Versions, drafts and history.
For modules your workspace owns. A check-in never goes live by itself: it becomes the next revision of the module's draft, which an admin previews and publishes in the Module Builder.
Command
What it does
Changes
Who
dv modules checkout <CODE> [folder]
Copies the module's latest code (live, or the open Module Builder draft) into a new folder. With Git installed, the folder is a Git repository: you work on main; the branch platform holds the platform's copy.
No
Admin
dv modules pull [folder]
Merges the platform's latest into your check-out. Commit your own work first; Git marks any conflict.
No (your folder only)
Admin
dv modules checkin [folder]
Sends your changes as the draft's next revision, and reports any errors the check found. Refused if someone checked in since your check-out: pull, resolve, commit, check in again.
Submits your module's latest version for Marketplace review. On approval it's listed for other workspaces. The manifest must allow a Marketplace listing. -m "release notes" for the catalog.
Yes
Admin
dv modules buy <CODE>
Without --confirm, shows the price and what you get and give up by buying your own copy of a Marketplace module. With --confirm <CODE>, buys it: you're charged, you change it in the Module Builder from then on, and it no longer gets Marketplace updates. Can't be undone.
Everything a module's screens can do is an action: one of the module's own routes, with the same permission and rules as in the app. Only the actions your role allows are listed.
Command
What it does
Main options
Who
dv actions list <CODE>
The module's actions you can run.
-q "words" to search, --json
Everyone
dv actions show <CODE> <ACTION>
One action: what it does, the permission it needs and its arguments.
Everyone
dv actions run <CODE> <ACTION>
Runs the action as you. Actions that change data change real records.
--args '{...}' (path and query values by name, the request body as "body"), --args-file args.json
Everyone (changes data when the action does)
Some actions need a person's approval in the app and can't be run here.
Sends one message to an agent and prints its reply and the tools it called. The agent runs in your workspace with your permissions, so it can change records. --json for the raw reply.
Everyone (as far as the agent's tools allow)
dv tools list
The modules' assistant tools, with the permission each needs and whether it waits for an approval. --module <CODE>.
Your workspace's public websites. View, Manage and Publish below are the View websites, Manage websites and Publish websites permissions. Commands marked Live change what the public sees.
Command
What it does
Main options
Needs
dv sites list
Your websites.
--json
View
dv sites show <SITE>
One website: its versions, domains and the DNS records each domain needs.
--json
View
dv sites templates
Websites the platform can make from its own templates.
View
dv sites feeds-available
The module feeds you can give a website.
Manage
dv sites create <SLUG>
Creates a website.
--name, --feed <FEED> (repeatable)
Manage
dv sites create-from-template <SLUG>
Creates a website from a platform template. Its first version builds to a preview.
--template, --name, --setting KEY=VALUE
Manage
dv sites template-update <SITE>
A new version of a template website, with the template's current code and any changed settings.
--setting KEY=VALUE, --notes
Manage
dv sites feeds <SITE>
Replaces the module feeds a website reads. Issues a new read-only key; the site gets it with its next version.
--feed (repeatable; none removes all)
Manage
dv sites env <SITE> KEY=VALUE ...
Sets the website's own non-secret settings, applied with the next version. KEY= removes one.
Manage
dv sites pull <SITE> <folder>
Downloads a version's code (default the live one) to change it.
--version, --force
Manage
dv sites deploy <folder>
Uploads the folder as a new version, builds it and prints its preview address. Not live until published, except a site's very first version.
--site, --notes, --force (upload even though the live site moved on since your pull)
Manage
dv sites refresh <SITE> <VERSION>
Checks a version that's building.
View
dv sites publish <SITE> <VERSION>
Live. Puts a version live. Publishing an earlier version is the rollback.
Publish
dv sites archive <SITE> <VERSION>
Takes a never-live version off the list.
--reason
Publish
dv sites dns <SITE> [DOMAIN]
Checks DNS now: the records to add, what DNS has, records to remove, and the certificate.
View
dv sites screenshot <SITE>
Takes a new picture of the live landing page for the Websites tile.
Manage
dv sites domain add <SITE> <DOMAIN>
Attaches a domain and prints the DNS records to add.
Manage
dv sites domain verify <SITE> <DOMAIN>
Checks the ownership record and marks the domain verified.
Manage
dv sites domain remove <SITE> <DOMAIN>
Live. Detaches a domain. Asks first (--yes skips).
Manage
dv sites route add <SITE> <DOMAIN> <PATH> <TARGET>
Live. Serves a path on one website's domain with another of your websites, such as yourcompany.com/updates.
Check the workspace first. Every command that changes something acts in the workspace dv dev status shows.
dv and platform are the same tool. Guides that write platform modules deploy mean dv modules deploy.
validate, scan, rules, interfaces, version and guide work offline, so you can check a module before signing in.
dv modules preview and dv dev token show your sign-in. The preview address carries your session token; don't paste it or the token anywhere others can see.
Very large modules (over about 8 MB or 400 files) are deployed with the CLI rather than through an AI app. Uploads are limited to 50 MB.
Some commands in dv --help aren't for workspaces, such as turning a module off for every workspace. Data Visions refuses them.