Your project.
Always monitored.
Carefully automated.

wsl --install --no-distribution
wsl --update
wsl --list --online

Restart Windows if prompted. Confirm that Ubuntu-24.04 appears in the online list before using that distribution name.

wsl --install -d Ubuntu-24.04 --location "E:\TunnelLab-AI\Ubuntu" --no-launch
wsl --list --verbose

On WSL builds that do not recognize --location, stop and update WSL; don't fall back to a default C: installation. For a dedicated restricted Linux user, follow the installer script or the security notes below before starting any agents.

sudo apt update
sudo apt install -y git python3 python3-venv tmux curl ca-certificates build-essential gh
# Install Node.js 24 using the maintained NVM project first:
# https://github.com/nvm-sh/nvm#installing-and-updating
# In a new Ubuntu shell, after NVM is installed:
nvm install 24
nvm use 24
npm install -g pnpm@11.7.0
node -v
pnpm -v
git --version
tmux -V
python3 --version
gh --version

The final commands check versions. Install Node.js 22.19+ (or 24+) and pnpm using their official Linux instructions, not an outdated Ubuntu package. Git must be 2.32+ and gh 2.48+.

npm install -g @deepseek-ai/dsh@0.2.1-rc.3
dsh --version

The version is pinned by the upstream Super Agent deployment guide. Confirm compatibility before upgrading.

mkdir -p ~/src
cd ~/src
git clone https://github.com/deepseek-ai/dsh-superagent-prototype.git dsh-superagent
cd dsh-superagent
git checkout 8c32a9dc5d72c033816c6a8110b37f40cf94fba4
pnpm install --frozen-lockfile
pnpm typecheck
pnpm build
export DSH_HOME="$HOME/.local/share/dsh"
mkdir -p "$DSH_HOME"
# Only for a NEW profile — stop if superagent already exists:
test ! -e "$DSH_HOME/profiles/superagent" || { echo "Profile already exists"; exit 1; }
dsh superagent --from-default-profile web --dump-config > /dev/null
dsh plugin --profile superagent add "link:$PWD"

Run profile creation ONLY once on a new installation. On an existing profile, the creation command can overwrite settings; use the official Upgrade guide instead.

Copy examples/profile.cordis.patch.yml to $DSH_HOME/profiles/superagent/cordis.patch.yml. Replace the stateDir placeholder with an absolute path (for example $DSH_HOME/state/superagent); use localhost port 3082. Set the dedicated GitHub CLI later in Settings → Sources, not in this YAML. Preserve existing configurations; do not overwrite a previously configured profile.

mkdir -p ~/.local/bin
cat > ~/.local/bin/gh-agent <<'EOF'
#!/bin/sh
GH_CONFIG_DIR="$HOME/.config/gh-agent" exec gh "$@"
EOF
chmod +x ~/.local/bin/gh-agent
gh-agent auth login
gh-agent api user --jq .login

Create the dedicated GitHub user and accept the test repository invitation manually. Only sign in as the bot for gh-agent. Don't reuse your main GitHub CLI credentials.

scripts/dsh-superagent start
scripts/dsh-superagent status

Open the panel URL shown in the start output; select Superagent in the sidebar. Set Sources, Policy, Execution and Prompts in that order. If status reports setup pending (exit 3), finish the missing settings rather than restarting repeatedly. If Node 24 reports MainThread and the process-detection script times out, verify the real process identity before any reviewed fix.

Initialize a disposable GitHub repository with README, invite a dedicated GitHub bot, clone with that bot's isolated gh-agent identity, and configure Settings → Execution → Prepare command from upstream Deployment. Set Eval and Execution to the working model (for example openrouter/free), select the same model in Open main Session, pause Executor and leave auto-merge off. Receive-mode Observe does not prevent explicitly addressed requests from becoming tickets; confirm safeguards before retrying.