d1v

D1V CLI

Deploy, inspect, and work inside D1V projects from your terminal.

Project-aware by default. Works with Codex and Claude Code. Supports cloud and local runtimes.

English ┃ 简体中文

Quick Start

Install, authenticate, and deploy the current directory:

curl -fsSL https://d1v.ai/install/d1v-cli.sh | bash
d1v auth login --browser
d1v --preview   # or: d1v --prev
d1v --prod

The CLI reads D1V_PROJECT_ID from the current directory's .env first, then from the process environment and .d1v/project.json. Explicit project arguments always win. When no project can be resolved interactively, choose one from the project picker. Cloud environment variables are merged into .env; local values are kept by default when keys conflict.

Run d1v --help for the complete command list.

Coding Agent Skill

The official, versioned d1v Skill lives at skills/d1v/SKILL.md. It gives Codex and Claude Code safe instructions for project workspaces, container commands, preview deployments, and user-confirmed production releases.

The curl installer uses --install-skill auto by default. It installs only for Codex and Claude Code executables already available on PATH; it does not install either coding agent and succeeds without changes when neither is found. Use the same behavior manually:

d1v skill install --agent auto

Use --agent codex, --agent claude, or --agent all to explicitly choose targets. Skills are written below ${CODEX_HOME:-~/.codex}/skills/d1v and ${CLAUDE_CONFIG_DIR:-~/.claude}/skills/d1v. An identical Skill is left alone; a different existing SKILL.md is backed up beside it as SKILL.md.d1v-backup-<UTC timestamp> before replacement. The legacy https://www.d1v.ai/cli-skill.md URL remains available and redirects to this canonical file.

D1V Mobile App

Pair the terminal workflow with d1vai_app, the official open-source Flutter client for d1v.ai. Use the CLI for fast local and CI workflows, and the mobile app to create projects, continue AI sessions, inspect files, monitor deployments, and manage your workspace away from a desk.

The companion app supports iOS and Android and includes its own screenshots, release downloads, and developer guide:

• d1vai_app repository
• Mobile releases
• d1v.ai documentation

Local Runtime

D1V supports a local runtime in addition to the existing cloud runtime.

Role split:

• opcode-api: the local runtime server
• d1v-cli: installer, launcher, supervisor, connector
• backend_admin: control plane and runtime router
• d1vai: unified frontend

The frontend never connects directly to the user machine. The local agent opens an outbound connection to D1V cloud.

Local Runtime Quickstart

1. Install and inspect the local runtime:

d1v runtime doctor
bash scripts/install-opcode-runtime.sh --home ~/d1v-home

1. Pair the machine:

d1v agent pair

Or keep using a pairing code generated in the web UI:

d1v agent pair --code <pairing-code>

1. Start the local runtime:

d1v agent start

1. Create or bind local project directories:

d1v agent project create --project-id <project_id> --name my-app
d1v agent project import --path ~/work/my-app --project-id <project_id>
d1v agent project bind --project-id <project_id> --path ~/work/my-app

Backward-compatible entry:

d1v agent init-runtime --project-id <project_id> --path ~/work/my-app

Local Runtime Behavior

• Runtime switching affects new sessions only.
• Existing sessions stay pinned to the runtime where they started.
• If a project is bound to local runtime and the device is offline, requests return an explicit local-runtime error instead of silently falling back to cloud.
• Project creation/import flows may still use cloud opcode directly before runtime binding exists.

Public Expose

CLI free expose does not require a running node agent:

d1v expose 3000
d1v expose list
d1v expose close <binding_id>

Platform node ingress stays on a separate command path:

d1v node expose 3000 --node-id <platform-node-id>
d1v node expose list
d1v node expose close <binding_id>

Current expose modes:

• cli_free_relay: returns a public https://*.cli-free.d1v.dev URL for login-backed temporary CLI relays
• cloudflare_tunnel: returns a public https://*.node.d1v.dev URL for platform nodes
• reverse_relay: internal fallback mode used by local/customer relays behind the CLI-free entry

d1v expose currently targets HTTP traffic. Browser terminal and session WebSocket flows still use the existing backend relay path.

Platform Node

Platform nodes now use a single control origin for runtime-agent ingress. The recommended bootstrap form is:

d1v node start --key <platform-node-key> --control-origin https://{your-host-or-name}-node.d1v.dev

If --control-origin is omitted, the runtime-agent falls back to its own public IP detection and control-plane registration flow.

Privacy Boundary

Current phase:

• paired devices only
• outbound-only relay
• short-lived pairing code
• stored device public key

Current limitation:

• relay traffic is not zero-knowledge
• platform metadata and chat/session records still follow existing D1V persistence behavior

For deeper architecture details, see docs/d1v-agent-architecture.md.

Install

Recommended:

curl -fsSL https://d1v.ai/install/d1v-cli.sh | bash

Install page:

https://d1v.ai/cli-install

Alternatives:

brew install d1vai/tap/d1v
cargo binstall d1v-cli
cargo install --locked d1v-cli

After install:

d1v auth login
d1v project list
d1v github status

To authenticate through an existing browser session and save a revocable device API key, use d1v auth login --browser. The browser approves a one-time, 10-minute session; the CLI stores the resulting key in ~/.d1v/config.toml.

Upgrade later:

d1v upgrade
d1v upgrade --version v0.1.5
d1v uninstall

d1v upgrade replaces only the executable. Your login remains in ~/.d1v/config.toml; upgrading does not sign you out or copy credentials into the release archive.

Global Options

Environment Variables

| Var