Preface¶

The ecosystem philosophy of DSH (DeepSeek Harness) is “everything is a plugin”; tool capabilities are plugged into the Agent’s invocation list via plugins. Actions like daily check-ins for WorkBuddy, claiming growth tasks, and claiming rewards for sending cats on trips are essentially “accessing pages, clicking a few buttons, recording points”—activities that are naturally suitable for Agents to handle. Doing it manually involves opening the webpage multiple times a day; forgetting to do it means losing a day’s points.

dsh-plugin-workbuddy-checkin is the plugin designed for this, maintained by cl2458228286-creator, published in the “Networked Tools” category of the community plugin directory SkillHub. It consolidates the five categories of WorkBuddy credit actions into a single call, does not touch tokens, and works based on an independent Chrome login state. The following text first explains the capabilities it provides, then installation, usage, and precautions.

What is this¶

One-sentence positioning: Trigger official WorkBuddy event interfaces via an Agent to automatically complete daily check-ins and credit claiming.

It solves two problems: remembering to click every day, and clicking multiple scattered locations on different pages. The plugin uses puppeteer-core to drive the local Chrome, stores the login Cookie in an independent directory, and then uses same-origin requests to call the official interface every time—just like clicking “Check-in” on a webpage.

Core Features¶

The plugin registers three tools with clear division of labor:

1. workbuddy_checkin_status: Read-only checkup, returns today’s check-in, streak days, task progress, cat travel status, and lottery times. Does not claim anything, suitable for a quick look before deciding.
2. workbuddy_claim_credits: Formal claiming, idempotent, does not repeat requests if already checked in.
3. workbuddy_login: Opens a dedicated Chrome window for QR code login once, then remains logged in long-term.

Credits that can be claimed are divided into five categories:

There is a boundary that needs to be clarified, which the README also states: The progress of Growth Center tasks is recorded by the server based on real behavior; the plugin does not fake it. It saves the “repeatedly going to the task page to click claim,” but it cannot save “using the product” itself.

Installation and Enabling¶

The recommended method is the graphical interface, no command line needed. Specifically two steps:

1. Copy this address:

https://github.com/cl2458228286-creator/dsh-plugin-workbuddy-checkin

2. Open DeepSeek Harness → Bottom left Settings → Plugins → Add Plugin, paste the URL above into the input box, and click confirm.

After installation, no restart is required, it takes effect immediately.

Afterwards, you need to log in once. Say “Login WorkBuddy check-in plugin” to the Agent in the chat. It will open an independent Chrome window, complete the login inside, and the script will automatically save and close the window upon success. The login state directory is ~/.workbuddy-checkin, do not delete, or you will need to log in again.

Prerequisites: Google Chrome must be installed (used by the plugin to save login state and call interfaces); DSH Desktop version 0.2.1-rc.1 or above.

If you are indeed using the dsh CLI (installed in development environments), the command is:

dsh plugin --profile <your-profile> add github:cl2458228286-creator/dsh-plugin-workbuddy-checkin

The value of --profile is the actual directory name being used under ~/.dsh/profiles/, fixed to desktop on the desktop. Ordinary users do not have the dsh command, ignore this line.

Uninstall path: Settings → Plugins → Find dsh-plugin-workbuddy-checkin → Uninstall. The login state directory will not be automatically deleted; manual deletion is needed for a thorough cleanup.

Typical Usage¶

The most hassle-free way is to just speak naturally to the Agent:

You: Help me claim WorkBuddy credits
Agent → workbuddy_claim_credits
       Gained 100 points this time (Check-in 100 / Tasks 0 / Travel 0 / Streak 0 / Lottery 0)

When you want to take a look before deciding:

You: Which credits haven't I claimed yet?
Agent → workbuddy_checkin_status (Read-only)
       Today's check-in: Yes (Streak 10 days) | Tasks: Total 18, 1 pending, 15 in progress

If you want to run it automatically at a scheduled time, tell the Agent:

Automatically claim WorkBuddy credits for me at 8:50 every day, then tell me the result.

The Agent will use DSH’s scheduling capability to create a daily task.

Configuration¶

By default, fully automatic, no configuration needed. In unconventional environments, you can add config in profile patch:

- id: workbuddy-checkin
  name: 'dsh-plugin-workbuddy-checkin'
  config:
    chromePath: 'D:\Chrome\chrome.exe'       # When Chrome is not in default location
    nodeExecutable: 'C:\nodejs\node.exe'     # When you want to specify node

There are four environment variables:

Node lookup order: config.nodeExecutable → WORKBUDDY_NODE → WorkBuddy built-in node → Host process itself → node on PATH.

Security Notice¶

The README is quite specific here, I’ll translate a few key points:

• Does not touch any tokens. The login state is browser Cookie, stored in a local independent directory; the plugin does not read its content or send it out.
• Tool return values contain only credit amounts and status, not Cookie or other credentials.
• Only accesses www.workbuddy.cn and www.codebuddy.cn, no telemetry, no uploads.
• Write operations are limited to claim endpoints of official event interfaces, no simulation of clicks, no reverse engineering of encryption, no bypassing of risk control.

Applicable Scenarios and Notes¶

Suitable for two types of people: DSH desktop users who indeed use WorkBuddy to claim credits daily, and those who want to add a “networked action” instance to an Agent that can be executed and use it as a reference for their own plugin structure.

Points to note:

1. The plugin runs with the permissions of the current DSH process; before installation, check the source code and license (MIT), and ensure lib/engine/web_checkin.mjs and cordis.patch.yml match your expectations.
2. It is a networked tool, relying on local Chrome. Headless environments do not support the login process.
3. In the return value, partial indicates sub-steps failed; the common cause is that task progress is not full and is intercepted by the server, running it the next day will naturally arrive.
4. There is one inconsistency in version numbers: the README writes 1.0.0, package.json is 1.0.1; during installation, the actual version installed takes precedence.
5. The tested environment marked in the README is DSH 0.2.1-rc.5, Windows 10 / x64, desktop profile.

Common troubleshooting items: If the tool doesn’t appear, first confirm it is installed in the current profile being used; if it reports Unable to resolve dependency puppeteer-core, it means the dependency isn’t installed, re-run dsh plugin add or go into the package directory and run pnpm install; if it reports not_logged_in, call workbuddy_login to scan the code once.

Conclusion¶

The value of this plugin lies in completely entrusting this small task of clicking a few times a day to the Agent, without using any tokens. Installation is two steps in the graphical interface, one-time login for long-term no-login, no extra config files needed. The repository comes with a self-test script (node scripts/selftest.mjs, no login required) and multi-platform release instructions. The plugin structure is clear and suitable as a reference sample for DSH plugin development.

Directory Page: https://www.skillhub.cn/plugins/cl2458228286-creator/dsh-plugin-workbuddy-checkin

Source Code: https://github.com/cl2458228286-creator/dsh-plugin-workbuddy-checkin