Introduction¶

DSH’s model calls connect directly to official channels by default, requiring you to top up keys and enter addresses yourself. In a lab scenario, both of these are troublesome: the group shares a quota, and member machine IPs often change—once DHCP changes the address, previously configured interface addresses become invalid.

deliver0/dsh-labai-gateway is a plugin designed for this scenario. Maintained by Deliver0, it runs a reverse proxy locally. DSH only needs to connect to 127.0.0.1:8801; the plugin handles finding the gateway and injecting the key. After the gateway changes its IP, the plugin automatically rediscover the address, so user-side configuration remains unchanged. The category is admin-security.

Below is an introduction to how it works, the installation process, and verification methods.

Positioning¶

In one sentence: The administrator connects to the DeepSeek official website using a group account, and your DSH borrows this group account to send requests via the gateway. Quotas are deducted from the group account, and the gateway records who used it each time.

Architecturally, it is divided into two layers:

1. The user-side plugin runs on the local machine 127.0.0.1:8801, responsible for forwarding requests to the real gateway and injecting member keys starting with sk-lab-.
2. The gateway machine verifies the member corresponding to the Key and the source IP; after passing, it requests the official website using the group account and returns the results the same way.

You don’t need to manually fill in the gateway address in the configuration; this is exactly one step saved compared to the approach of “filling in the API base URL yourself.”

Core Features¶

• Local Reverse Proxy: The plugin provides an OpenAI-style /v1 interface at 127.0.0.1:8801. Simply fill in this address in DSH; the plugin injects the Key, so you don’t need to fill it yourself.
• Gateway Auto-Discovery: After the gateway host IP changes or restarts, the plugin rediscover the gateway address and reconnects; users do not need to change any configuration.
• Single Member Key: Starting with sk-lab-, issued by the administrator based on name, email, or IP, and can be bound to an IP.
• Track Usage by Member: There is “Usage Monitoring” on the gateway side, allowing administrators to see specific members’ call counts and token usage.
• Provides two model groups, Lab436, for DeepSeek Flash and DeepSeek V4 Pro.
• Provides status and refresh interfaces, see the troubleshooting section below.

Prerequisites¶

Requirements from the plugin README:

• Windows with DSH 0.2.1 or later installed.
• Connected to the campus network (not a mobile hotspot or home broadband).
• Obtained an sk-lab- prefixed Key from the administrator.

The plugin’s package.json declares "engines": { "node": ">=20" }, license is MIT, current version 1.0.2.

Before installation, it is recommended to read the lib/ and bin/ scripts in the repository yourself to ensure no unexpected behavior.

Installation¶

The official installation uses a download script; the repository does not provide a command in the form of dsh plugin add.

Step 1: Find out your campus network IP.

ipconfig | findstr /i "IPv4"

Take the address starting with 10.16, for example 10.16.35.101. 127.0.0.1, 192.168.x.x, 172.x.x.x are not campus network addresses; when there are multiple lines, select the line labeled “Ethernet” or “WLAN / Wireless LAN”, avoiding VMware, VirtualBox, and WSL virtual network cards.

Step 2: Send your name, email, and the just-found IP to the administrator to get an sk-lab- starting Key. If the administrator replies that IP binding is not needed, just send the name and email.

Step 3: Completely exit DSH. Right-click the tray icon to exit; there should be no DeepSeek Harness process left in Task Manager; clicking the X in the top right corner of the window does not count as exiting.

Step 4: Download and run the installation script.

https://github.com/Deliver0/dsh-labai-gateway/releases/latest/download/LabAI-Setup.bat

When running, paste the Key obtained in Step 2 as prompted and press Enter. The script will download the plugin; if the channel plugin is missing, it will install one as well. If you see the “This file is unsafe / Unknown publisher” prompt, click “Keep” → “Run anyway”. If the link cannot be opened, download from the repository homepage green Code → Download ZIP, then double-click install.bat after extraction.

Step 5: The end of the script will display:

申请已提交，正在等审批

When you see this line, tell the administrator “I have installed it” and wait for them to approve it on the gateway side. After approval, reopen DSH to use it.

Enable and Verify¶

Reopen DSH, start a new conversation, and find the Lab436 group in the model selection; it contains two models:

DeepSeek Flash is the same model as the commonly used v4.1-flash. The address and Key are already configured by the plugin, so you don’t need to fill them yourself. If you want to switch back to the original model group, just switch back; the two sets do not interfere with each other.

To verify that it is actually using the lab quota: ask a random question; if it answers normally, it is connected. Then ask the administrator to confirm your name and call count appear in “Usage Monitoring”.

When some tools force you to fill in the interface address:

Address  http://127.0.0.1:8801/v1
Key   Fill in anything, or leave empty

Troubleshooting¶

First, open the status page:

http://127.0.0.1:8801/__labai/status

• The return contains "ip": "10.16.x.x", indicating connection to the gateway; if approval is pending, it means it hasn’t been approved yet, keep waiting; if approval is active but still reports an error, it is mostly because the local IP changed.
• If "ip": null is returned, it is mostly because you are not connected to the campus network, the gateway host is not on, or the gateway has moved to a new network segment.

The prompt “This Key is not allowed to be used from x.x.x.x” indicates that the local IP has changed. Re-run ipconfig | findstr /i "IPv4" to check the new IP and send it to the administrator to rebind or re-register.

To force rediscovery of the gateway:

http://127.0.0.1:8801/__labai/refresh

If the problem is not resolved, send a screenshot of the status page to the administrator. Note: Do not change the address in DSH yourself, and do not give the Key to others. If a Key is bound to an IP, it cannot be used on a different machine; if it is not bound to an IP, anyone who gets it can use it, and the usage will be counted on the account.

Uninstall¶

Double-click uninstall.bat in the plugin directory, then restart DSH once.

Applicable Scenarios and Notes¶

Suitable for Windows users in labs or research groups who want to share a DeepSeek quota and whose member machine IPs change. The premise is being inside the campus network; the administrator needs to have created the group account and Key beforehand and gone through the approval process.

A few points to note:

• The plugin runs with the permissions of the current DSH process; the installation script and code under bin/ and lib/ execute locally; before installing, read the source code and confirm the license (currently MIT).
• Primarily used in conjunction with the LabAI gateway; the README does not provide usage instructions for non-campus network environments.
• On the author’s side, only admin features are written in ADMIN.md; ordinary users do not need to look at it; this article only covers the perspective of an ordinary member.

Summary¶

The plugin’s role is to eliminate the three manual steps of “configuring the address yourself, topping up money yourself, and reconfiguring when the IP changes.” DSH only faces a fixed local address, and quota management is left to the gateway side. The directory page is at https://www.skillhub.cn/plugins/Deliver0/dsh-labai-gateway, and the repository is at https://github.com/Deliver0/dsh-labai-gateway.