DingTalk Channel Auto Connection (Visual Browser)

This skill is used to automate the creation of DingTalk applications and binding with CoPaw channels via a visual browser.

Mandatory Rules

Must start in visual browser mode:

json

{"action": "start", "headed": true}

Must pause when encountering login barriers:
- If a login interface appears on the page (such as "Login", QR code login, phone number/password login), stop automatic operations immediately.
- Clearly prompt the user to log in manually first, then wait for the user to reply "Logged in/Continue".
- Do not proceed with subsequent steps until receiving user confirmation.
Any application configuration changes must take effect only after creating a new version and publishing it:
- Be sure to publish the bot after configuring the bot-related information
- Whether creating a new application or modifying application information (name, description, icon, bot configuration, etc.), you must finally execute "Create new version + Publish".
- Do not claim that the configuration has taken effect if publishing is not completed.

Pre-execution Confirmation (Mandatory)

Before starting automated clicks, initiate a "configuration confirmation" to the user, clearly informing them of customizable items, image specifications, and default values. It is recommended to use the following structured confirmation:

Allow users to customize the following fields:
- Application name
- Application description
- Bot icon image link or local path
- Bot message preview image link or local path
Clearly inform of image specifications (prominent prompt):
- Bot icon: Only JPG/PNG supported, above
```
240*240px
```
  ,
```
1:1
```
  aspect ratio, within
```
2MB
```
  , no rounded corners.
- Bot message preview image: Format
```
png/jpeg/jpg
```
  , no larger than
```
2MB
```
  .

Clearly inform of default values (automatically adopted if user does not specify):

Application name:
```
CoPaw
```
Application description:
```
Your personal assistant
```

Bot icon:

https://img.alicdn.com/imgextra/i4/O1CN01M0iyHF1FVNzM9qjC0_!!6000000000492-2-tps-254-254.png

Bot message preview image:

https://img.alicdn.com/imgextra/i4/O1CN01M0iyHF1FVNzM9qjC0_!!6000000000492-2-tps-254-254.png

If the user does not provide any custom values, must clearly reply:
- "Will continue with all default settings (CoPaw / Your personal assistant / default images)."

Image Upload Strategy (Both link/path Supported)

If the user provides a local path, use it directly for upload.
If the user provides an image link, first download it to a local temporary file, then perform the upload.
The upload action sequence must be:
- First click the page upload entry (trigger chooser)
- Then call
```
file_upload
```
  with the local path array (
```
paths_json
```
  )
If upload fails and it is judged to be due to non-compliant image specifications (size, aspect ratio, file size, format):
- Immediately pause automation
- Clearly ask the user to manually upload a compliant image
- After the user confirms "Uploaded/Continue", resume the process from the current step

Practical Experience with Upload Actions

The
```
paths_json
```
of
```
file_upload
```
must be a "JSON string array", note the escaping:

json

{
  "action": "file_upload",
  "paths_json": "[\"xxx.png\"]",
  "frame_selector": "iframe[src*=\"/fe/app?isHideOuterFrame=true\"]"
}

If the page is within an iframe, it is recommended to include
```
frame_selector
```
first, otherwise the upload control may not be found or the chooser may not be triggered.
Must click the upload entry before uploading; if directly using
```
file_upload
```
, the following error will be reported:
- ```
No chooser. Click upload then file_upload.
```
Common structural features of the bot icon area can be used for positioning (example):
- ```
text: "* Bot Icon"
```
- ```
button: "Use Application Icon"
```
- ```
button: "avatar"
```
  (usually contains
```
img "avatar"
```
  internally)
When both "Use Application Icon" and "avatar" appear in the snapshot, prioritize clicking the
```
avatar
```
button to trigger upload, then execute
```
file_upload
```
.

Automation Workflow

Step 1: Open DingTalk Developer Backend

Start the browser in visual mode (
```
headed: true
```
)
Open
```
https://open-dev.dingtalk.com/
```
Call
```
snapshot
```
to determine if login is required

If login is required, pause with the following message:

Detected that login to DingTalk Developer Backend is required. I have paused automatic operations. Please complete login in the popped-up browser first. Reply "Continue" after completion, and I will proceed from the current page.

Step 2: Create Internal Enterprise Application

Continue after user confirms login:

Enter the creation path:
- Application Development -> Internal Enterprise Applications -> DingTalk Applications -> Create Application
Fill in application information (prioritize user-defined values, otherwise use defaults):
- Application name: Default
```
CoPaw
```
- Application description: Default
```
Your personal assistant
```
Save and create the application

If the page copy or structure is inconsistent with expectations, re-call

snapshot

and re-locate elements based on visible text semantics.

Step 3: Add Bot Capabilities and Publish

Click Add Application Capabilities in Application Capabilities, find Bot and add it
Toggle the switch button on the right of Bot Configuration to on
Fill in Bot Name, Bot Introduction and Bot Description
Upload Bot Icon (user-defined or default image):
- Click the image below the bot icon
- Default image link:
```
https://img.alicdn.com/imgextra/i4/O1CN01M0iyHF1FVNzM9qjC0_!!6000000000492-2-tps-254-254.png
```
- If it is a link, download to local first then upload
- If prompted with non-compliant image, pause and ask user to manually upload a compliant image before continuing
Upload Bot Message Preview Image (user-defined or default image):
- Click the image below the bot message preview image
- Default image link:
```
https://img.alicdn.com/imgextra/i4/O1CN01M0iyHF1FVNzM9qjC0_!!6000000000492-2-tps-254-254.png
```
- If it is a link, download to local first then upload
- If prompted with non-compliant image, pause and ask user to manually upload a compliant image before continuing
Confirm that the message receiving mode is set to
```
Stream mode
```
Select Publish, a further confirmation page will pop up, select Publish. Note: Be sure to publish the bot before proceeding to the next step

Step 4: Create and Publish Version

Open

Application Release -> Version Management and Release

Create a new version (must be created after each configuration change)
Fill in the version description, select all employees for application visibility scope
Complete the release as prompted by the page, a new pop-up will appear, select Confirm Publish
Only proceed to subsequent steps/give the user the "effective" conclusion after seeing the release success status

Step 5: Obtain Credentials

Open

Basic Information -> Credentials and Basic Information

Inform the user that
```
Client ID
```
(AppKey) and
```
Client Secret
```
(AppSecret) are on this page. Do not modify them actively, guide the user to bind them on their own

CoPaw Binding Methods

After obtaining the credentials, guide the user to choose one of the following methods:

Console front-end configuration:
- Enter
```
Control -> Channels -> DingTalk
```
  in CoPaw console
- Fill in
```
Client ID
```
  and
```
Client Secret
```
Configuration file method:

json

"dingtalk": {
  "enabled": true,
  "bot_prefix": "[BOT]",
  "client_id": "Your Client ID",
  "client_secret": "Your Client Secret"
}

Path:

~/.copaw/config.json

, under

channels.dingtalk

Credential Delivery Requirements (Mandatory)

The agent is only responsible for guiding the user to the credential page, obtaining and displaying
```
Client ID
```
and the real
```
Client Secret
```
.
The agent shall not modify the
```
console
```
configuration or
```
~/.copaw/config.json
```
actively.
Must prompt the user to fill in manually in one of the following two ways:
- Console front-end:
```
Control -> Channels -> DingTalk
```
- Configuration file: Edit the
```
channels.dingtalk
```
  field in
```
~/.copaw/config.json
```

Browser Tool Calling Mode

Execute in the following order by default:

```
start
```
with
```
headed: true
```
```
open
```
```
snapshot
```
```
click
```
/
```
type
```
/
```
select_option
```
/
```
press_key
```
as needed
frequent
```
snapshot
```
after page transitions
```
stop
```
when done

Stability and Recovery Strategy

Prioritize using the
```
ref
```
from the latest
```
snapshot
```
; use
```
selector
```
only when necessary.
After each critical click or jump, use a short wait (
```
wait_for
```
) and immediately re-call
```
snapshot
```
.
If the session expires or re-login is required midway, must pause again, and resume from the current step after the user logs in.
If automation is blocked due to tenant permissions, administrator approval, etc., clearly explain the bottleneck, and ask the user to complete the step manually before resuming.

dingtalk_channel_connect

NPX Install

Tags

SKILL.md Content (Chinese)

DingTalk Channel Auto Connection (Visual Browser)

Mandatory Rules

Pre-execution Confirmation (Mandatory)

Image Upload Strategy (Both link/path Supported)

Practical Experience with Upload Actions

Automation Workflow

Step 1: Open DingTalk Developer Backend

Step 2: Create Internal Enterprise Application

Step 3: Add Bot Capabilities and Publish

Step 4: Create and Publish Version

Step 5: Obtain Credentials

CoPaw Binding Methods

Credential Delivery Requirements (Mandatory)

Browser Tool Calling Mode

Stability and Recovery Strategy