dkucc-clash-forwarding

name: dkucc-clash-forwarding description: Record, inspect, and maintain the verified VS Code/Cursor plus SSH RemoteForward workflow that exposes local Clash proxy traffic to DKUCC remote hosts. Use when working on dkucc-login-01 / dkucc-login-01-proxy, debugging remote port forwarding failed for listen port 17890, documenting the current forwarding setup, or updating the local/remote files that control this workflow.

DKUCC Clash Forwarding

Overview

Use this skill to inspect and maintain the current Windows local plus DKUCC remote workflow for forwarding local Clash traffic to DKUCC through SSH.

The current verified bridge is:

remote 127.0.0.1:17890 -> local 127.0.0.1:7890

Workflow

1. Read references/current-config.md first.
2. Treat the files listed there as the current source of truth for this setup.
3. If the task is about failures or reconnect behavior, also read references/troubleshooting.md.
4. When updating the setup, preserve the separation between:
   • dkucc-login-01: normal work host
   • dkucc-login-01-proxy: bridge host with RemoteForward
5. Prefer the validated operating mode:
   • open one manual ssh dkucc-login-01-proxy bridge
   • connect Cursor / VS Code to dkucc-login-01

Files To Inspect

Check these files before making claims about the current setup:

• C:\Users\27538\.ssh\config
• C:\Users\27538\AppData\Roaming\Code\User\settings.json
• C:\Users\27538\agent.md
• C:\Users\27538\.cursor\worktrees\Obsidian_Vault\bht\01-研究项目\PACE\01-Notes\SpectralMAE\DKUCC.md

If remote state matters, verify it directly on DKUCC instead of assuming the local docs are still current:

env | grep -i proxy
ss -lnpt | grep 17890
tmux show-environment | grep -i proxy

Output Expectations

When documenting or updating this setup:

• Separate verified behavior from hypotheses.
• Include copy-pastable commands.
• Call out any mismatch between local config, remote config, and notes.
• Do not claim Cursor can safely connect to dkucc-login-01-proxy if a manual proxy bridge is already active.

Current Operating Rule

The currently preferred mode is:

ssh dkucc-login-01-proxy

Then use:

dkucc-login-01

for Cursor / VS Code and additional normal shells.