Preface¶
The design philosophy of DeepSeek Harness (DSH) is “everything is a plugin.” After an agent completes a task, there needs to be a way to notify the user of the result. Native push notifications are often not intuitive enough, while directly accessing mobile system APIs can involve high development costs. This plugin solves the need to push task completion messages from a DSH agent to the Huawei HarmonyOS Today screen (Smart Assistant · Today).
What It Is¶
This is a DSH plugin that pushes task completion messages to the Huawei HarmonyOS Today screen service card. It is wire-compatible with the OpenClaw today-task skill (using the same upload endpoint and payload contract), meaning the two use the same authentication method and card rendering rules. The plugin itself does not provide a client UI and does not depend on additional runtime libraries; it uses the built-in fetch in Node.js for HTTP communication.
Installation¶
Run the following command in the terminal to install the plugin:
dsh plugin --profile web add github:Entity-Him/dsh-hiboard-push
After installation, restart the dsh process to load the plugin.
Configuration¶
Before use, you need to obtain and configure the authorization code on your HarmonyOS mobile device.
-
Obtain the authCode
- Open the Today screen (Smart Assistant · Today) on your phone.
- Navigate to “Me” → “Dynamic Management” → “Associated Accounts” → “Claw Agent.”
- Obtain and copy the authorization code (for example,uhIzvTvjwnAD). -
Configure the authCode
Use the provided command to write the authorization code into the configuration file:
dsh-hiboard-auth your-auth-code
This command writes the authorization code to ~/.dsh/hiboard-auth.env (file permissions are 600, hidden), and ensures that the dsh process can read this credential every time it starts.
- Restart the service
After running the configuration command, restart dsh to make the settings take effect.
Core Features¶
The plugin registers two tools for the agent to call.
hiboard_push¶
Used to push task cards. The parameters are described as follows:
| Parameter | Required | Description |
|---|---|---|
name |
✅ | Task name, used as the card title, scheduleTaskName, and summary. |
content |
✅ | Body content in Markdown format (≤ 5000 characters), rendered as-is on the card. |
result |
❌ | Result summary/status label. Defaults to Task Completed. |
schedule_id |
❌ | Periodic task ID. Keep the same ID to aggregate repeated cards. |
dry_run |
❌ | Boolean. Set to true to only build and validate the payload without sending the actual card. |
hiboard_verify¶
Used to test the connection. Calling this tool will deliver a “dsh Connection Test” card to your phone’s Today screen, which verifies whether the authCode and network path are working properly.
Notes¶
- Security Risk: The authCode is a personal credential. Anyone who holds this code can push cards to your Today screen. Do not paste it into group chats or commit it to code repositories.
- Compatibility: Because it uses the same endpoint as OpenClaw, if you previously configured OpenClaw, you can reuse its authCode.
- Storage Location: The authorization code is stored only in the local file
~/.dsh/hiboard-auth.env.