NDDev-it-com/nddev-qoder-cli-app

nddev-qoder-cli-app

Target-explicit NDDev setup manager for Qoder CLI.

This module manages one isolated Qoder target selected by --target. It never defaults to the caller's live Qoder configuration, does not mutate live trust state, and does not inherit caller home-directory credentials.

Supported runtime baseline

• Command: qodercli
• Package identity: @qoder-ai/qodercli
• Install manifest: https://qoder-ide.oss-accelerate.aliyuncs.com/qodercli/channels/manifest.json
• Managed config root: QODERCONFIGDIR=<absolute-target

The immutable official observation, release-page split, archive names, sizes, and SHA-256 digests are in references/qoder-cli-baseline.json.

Usage

python3 cli-tools/nddev_qoder_cli.py list
python3 cli-tools/nddev_qoder_cli.py plan --target /absolute/qoder-target --workspace /absolute/workspace
python3 cli-tools/nddev_qoder_cli.py install --target /absolute/qoder-target --workspace /absolute/workspace
python3 cli-tools/nddev_qoder_cli.py update --target /absolute/qoder-target
python3 cli-tools/nddev_qoder_cli.py switch --target /absolute/qoder-target --profile safe
python3 cli-tools/nddev_qoder_cli.py restore --backup 0 --target /absolute/qoder-target
python3 cli-tools/nddev_qoder_cli.py remove --target /absolute/qoder-target
python3 cli-tools/nddev_qoder_cli.py software-status --target /absolute/qoder-target
python3 cli-tools/nddev_qoder_cli.py install-cli --target /absolute/qoder-target
python3 cli-tools/nddev_qoder_cli.py update-cli --target /absolute/qoder-target
python3 cli-tools/nddev_qoder_cli.py remove-cli --target /absolute/qoder-target
python3 cli-tools/nddev_qoder_cli.py launch --target /absolute/qoder-target --workspace /absolute/workspace -- --help

install-cli uses the official manifest archive for the current supported product host. The official https://qoder.com/install script is pinned as evidence, but production install uses the verified release asset directly because the installer has no target-prefix contract.

Setup And Profiles

Content setup is exactly nddev-builder. Launch permission behavior is selected separately:

• full-auto: canonical --permission-mode bypasspermissions.
• safe: canonical --permission-mode dontask.

The manager owns the launch permission argument. Caller attempts to pass --permission-mode, --dangerously-skip-permissions, --yolo, --config-dir, --cwd, --plugin-dir, or related config/tool override flags fail closed. Upstream safety checks or administrator policy may still constrain bypasspermissions.

Launch Environment

Launch uses isolated target-owned runtime directories:

• HOME=<target/home
• USERPROFILE=<target/home
• TMPDIR=<target/runtime/tmp
• XDGCONFIGHOME=<target/runtime/xdg-config
• XDGCACHEHOME=<target/runtime/xdg-cache
• XDGSTATEHOME=<target/runtime/xdg-state

• QODERCONFIGDIR=<target

Only locale/terminal variables and QODERPERSONALACCESSTOKEN are inherited from the caller. External Git, package-manager, and provider credentials from the caller's home are intentionally not inherited.