chatccc 0.2.299 → 0.2.301

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (54) hide show
  1. package/.agents/skills/create-chatccc-feishu-app/SKILL.md +85 -85
  2. package/.claude/skills/create-chatccc-feishu-app/SKILL.md +85 -85
  3. package/.cursor/skills/create-chatccc-feishu-app/SKILL.md +85 -85
  4. package/README.md +6 -2
  5. package/agent-prompts/claude_specific.md +45 -45
  6. package/agent-prompts/codex_specific.md +2 -2
  7. package/agent-prompts/cursor_specific.md +13 -13
  8. package/bin/cccagent.mjs +26 -26
  9. package/bin/chatccc.mjs +15 -15
  10. package/config.sample.json +7 -6
  11. package/deepccc-agent/README.md +21 -4
  12. package/deepccc-agent/os-prompts/darwin.md +8 -8
  13. package/deepccc-agent/os-prompts/linux.md +8 -8
  14. package/deepccc-agent/os-prompts/win32.md +11 -11
  15. package/deepccc-agent/package.json +68 -68
  16. package/dist/deepccc-agent/src/attachments.js +7 -5
  17. package/dist/deepccc-agent/src/cli.js +52 -7
  18. package/dist/deepccc-agent/src/completion-session.js +100 -0
  19. package/dist/deepccc-agent/src/config.js +4 -0
  20. package/dist/deepccc-agent/src/context.js +4 -1
  21. package/dist/deepccc-agent/src/decision-session.js +314 -0
  22. package/dist/deepccc-agent/src/file-tools.js +5 -0
  23. package/dist/deepccc-agent/src/index.js +41 -4
  24. package/dist/deepccc-agent/src/json-mode-fetch.js +12 -0
  25. package/dist/deepccc-agent/src/json-response.js +33 -0
  26. package/dist/deepccc-agent/src/multimodal.js +291 -0
  27. package/dist/deepccc-agent/src/progress/reducer.js +2 -0
  28. package/dist/deepccc-agent/src/web-page.js +411 -411
  29. package/dist/deepccc-agent/src/web-runtime.js +3 -0
  30. package/dist/deepccc-agent/src/web-server.js +2 -0
  31. package/dist/src/adapters/ccc-adapter.js +4 -0
  32. package/dist/src/agent-team/web/agent-team-page.js +250 -250
  33. package/dist/src/config.js +2 -0
  34. package/dist/src/engines/engine-specs.js +71 -71
  35. package/dist/src/feishu-api.js +14 -12
  36. package/dist/src/litellm-proxy.js +15 -15
  37. package/dist/src/progress/reducer.js +2 -0
  38. package/dist/src/session.js +1 -0
  39. package/dist/src/web-ui.js +80 -66
  40. package/im-skills/feishu-skill/receive-send-file.md +65 -65
  41. package/im-skills/feishu-skill/receive-send-image.md +26 -26
  42. package/im-skills/feishu-skill/send-file.mjs +6 -6
  43. package/im-skills/feishu-skill/send-image.mjs +6 -6
  44. package/im-skills/feishu-skill/skill.md +28 -28
  45. package/im-skills/wechat-file-skill/receive-send-file.md +38 -38
  46. package/im-skills/wechat-file-skill/send-file.mjs +83 -83
  47. package/im-skills/wechat-file-skill/skill.md +10 -10
  48. package/im-skills/wechat-image-skill/skill.md +10 -10
  49. package/im-skills/wechat-video-skill/receive-send-video.md +38 -38
  50. package/im-skills/wechat-video-skill/send-video.mjs +79 -79
  51. package/im-skills/wechat-video-skill/skill.md +10 -10
  52. package/package.json +77 -77
  53. package/scripts/postinstall-sharp-check.mjs +58 -58
  54. package/scripts/self-update-helper.mjs +301 -301
@@ -1,85 +1,85 @@
1
- ---
2
- name: create-chatccc-feishu-app
3
- description: Create, clone, or configure a Feishu enterprise self-built bot application for ChatCCC. Use when asked to create a ChatCCC Feishu app, imitate an existing lowercase `chatccc` app, prepare a bot for another computer, or configure its bot capability, `im:`/`cardkit:` permissions, events, credentials, version, and internal release from this repository's README.
4
- ---
5
-
6
- # Create a ChatCCC Feishu App
7
-
8
- Use the logged-in Feishu developer console to create and completely configure a ChatCCC bot app. Treat this repository's README as the authoritative source for permissions and required capabilities. When imitation is requested, use the existing app named exactly lowercase `chatccc` only as a template for presentation, subscriptions, and release settings.
9
-
10
- ## 1. Establish the target and authorization
11
-
12
- - Read the `README.md` section `#### 飞书(推荐)` before changing the console.
13
- - Determine the requested app name, target computer, description, icon, availability, and whether the user wants configuration only or a real release. Derive a concise description when one is not supplied; for example, `用飞书聊天控制<目标电脑>上的 Claude Code / Cursor / Codex。`.
14
- - Use the browser surface the user requested. If the user specifies Chrome DevTools/CDP, connect directly to `chromeDevtools.port` or the README default `15166`; do not substitute extension-based Chrome control.
15
- - Obtain action-time confirmation before creating the app, granting permissions, saving event/callback subscriptions, or publishing. One explicit instruction such as `完整配置并真正发布` may authorize the listed actions as a batch.
16
-
17
- ## 2. Inventory the lowercase template
18
-
19
- 1. Open `https://open.feishu.cn/app?from=devbotmenu` in the authenticated browser.
20
- 2. Open the app named exactly lowercase `chatccc` in a separate tab.
21
- 3. Record its non-secret configuration:
22
- - app description and icon;
23
- - application capabilities, especially `机器人`;
24
- - event and callback subscription modes;
25
- - every event and callback identifier;
26
- - version availability, external sharing choices, and release state.
27
- 4. Never reveal, log, export to chat, or persist the template App Secret.
28
-
29
- Do not use the template's permission set or permission counts as the source of truth. Permissions must always follow the current README rule below. Prefer current console data over a stale hard-coded list for the remaining template settings.
30
-
31
- ## 3. Create the target app
32
-
33
- 1. Choose `创建企业自建应用` and fill the requested name and description.
34
- 2. Reuse the lowercase `chatccc` icon only when imitation was requested, and verify its crop preview.
35
- 3. Click the final `创建` action only after confirmation.
36
- 4. Click once and wait for SPA navigation. Verify the exact app name, App ID, URL, and status before retrying; the console can temporarily show stale text after a successful mutation.
37
-
38
- ## 4. Configure the complete README-defined ChatCCC setup
39
-
40
- Perform the configuration in this order:
41
-
42
- 1. Add the `机器人` application capability and verify that the page offers `删除能力`, which means the capability is enabled.
43
- 2. Configure permissions from the README, not from the lowercase template:
44
- - under `权限管理`, search for the `im:` prefix and enable every permission whose name starts with `im:`;
45
- - search for the `cardkit:` prefix and enable every permission whose name starts with `cardkit:`;
46
- - separately search for the exact scope `im:message.p2p_msg:readonly` and verify that it is enabled. This private-message read permission is easy to miss and must not be inferred from other message permissions;
47
- - confirm all permission changes and complete any required administrator approval;
48
- - do not use template permission export/import as an authoritative shortcut, because the template may be incomplete or stale.
49
- 3. Under `事件与回调` > `事件配置`, set the subscription mode to `使用长连接接收事件`, then add every event present in the template. The verified baseline is:
50
- - `im.chat.disbanded_v1`
51
- - `im.chat.member.bot.added_v1`
52
- - `im.chat.member.bot.deleted_v1`
53
- - `im.chat.member.user.added_v1`
54
- - `im.chat.member.user.deleted_v1`
55
- - `im.chat.member.user.withdrawn_v1`
56
- - `im.message.bot_muted_v1`
57
- - `im.message.message_read_v1`
58
- - `im.message.reaction.created_v1`
59
- - `im.message.reaction.deleted_v1`
60
- - `im.message.recalled_v1`
61
- - `im.message.receive_v1`
62
- 4. Under `回调配置`, independently set `使用长连接接收回调` and add `card.action.trigger`. Configuring the event mode does not configure the callback mode.
63
- 5. Verify that every listed event shows a sufficient permission as `已开通`.
64
-
65
- The README requires the bot capability, every permission whose name starts with `im:` or `cardkit:`, explicit verification of `im:message.p2p_msg:readonly`, `im.message.receive_v1`, and `card.action.trigger`. A clone request may copy the current template's presentation, subscriptions, availability, and release settings, but it must not weaken the README permission rule.
66
-
67
- ## 5. Create and publish a version
68
-
69
- 1. Open `版本管理与发布` and create a version such as `1.0.0`.
70
- 2. Keep mobile and desktop default abilities set to `机器人` and write a meaningful update note.
71
- 3. Match the requested or template availability. For a personal computer, default to the owner-only internal range and leave external group/private-chat sharing disabled unless explicitly requested.
72
- 4. Save the version, then complete the separate `确认发布` action. A successful version creation alone is not a release.
73
- 5. Refresh the version list and require all of the following evidence before reporting success:
74
- - application status `已启用`;
75
- - banner `当前修改均已发布`;
76
- - version status `已发布` with a publication time.
77
- 6. If administrator review is required, submit everything authorized and report the exact remaining approval state.
78
-
79
- ## 6. Verify and hand off safely
80
-
81
- - Re-open the bot, permission, event/callback, and version pages after publication. Verify the bot is enabled, all current `im:` and `cardkit:` permissions are enabled, `im:message.p2p_msg:readonly` is explicitly present, both subscription modes are long connection, event/callback identifiers match, and the version is published.
82
- - Treat network responses and a refreshed page as stronger evidence than an immediately stale SPA view. Never repeat a create, add, or publish action only because the first page read is stale.
83
- - Report the app name, App ID, capability, whether the README permission checks passed, event/callback counts, version, release state, and any remaining action.
84
- - Never print the App Secret. If the user explicitly asks to configure ChatCCC, transfer the App ID and App Secret directly into the local private configuration without echoing the secret in commands, logs, screenshots, files tracked by Git, or chat.
85
- - Do not modify local ChatCCC configuration or transmit credentials elsewhere unless explicitly authorized.
1
+ ---
2
+ name: create-chatccc-feishu-app
3
+ description: Create, clone, or configure a Feishu enterprise self-built bot application for ChatCCC. Use when asked to create a ChatCCC Feishu app, imitate an existing lowercase `chatccc` app, prepare a bot for another computer, or configure its bot capability, `im:`/`cardkit:` permissions, events, credentials, version, and internal release from this repository's README.
4
+ ---
5
+
6
+ # Create a ChatCCC Feishu App
7
+
8
+ Use the logged-in Feishu developer console to create and completely configure a ChatCCC bot app. Treat this repository's README as the authoritative source for permissions and required capabilities. When imitation is requested, use the existing app named exactly lowercase `chatccc` only as a template for presentation, subscriptions, and release settings.
9
+
10
+ ## 1. Establish the target and authorization
11
+
12
+ - Read the `README.md` section `#### 飞书(推荐)` before changing the console.
13
+ - Determine the requested app name, target computer, description, icon, availability, and whether the user wants configuration only or a real release. Derive a concise description when one is not supplied; for example, `用飞书聊天控制<目标电脑>上的 Claude Code / Cursor / Codex。`.
14
+ - Use the browser surface the user requested. If the user specifies Chrome DevTools/CDP, connect directly to `chromeDevtools.port` or the README default `15166`; do not substitute extension-based Chrome control.
15
+ - Obtain action-time confirmation before creating the app, granting permissions, saving event/callback subscriptions, or publishing. One explicit instruction such as `完整配置并真正发布` may authorize the listed actions as a batch.
16
+
17
+ ## 2. Inventory the lowercase template
18
+
19
+ 1. Open `https://open.feishu.cn/app?from=devbotmenu` in the authenticated browser.
20
+ 2. Open the app named exactly lowercase `chatccc` in a separate tab.
21
+ 3. Record its non-secret configuration:
22
+ - app description and icon;
23
+ - application capabilities, especially `机器人`;
24
+ - event and callback subscription modes;
25
+ - every event and callback identifier;
26
+ - version availability, external sharing choices, and release state.
27
+ 4. Never reveal, log, export to chat, or persist the template App Secret.
28
+
29
+ Do not use the template's permission set or permission counts as the source of truth. Permissions must always follow the current README rule below. Prefer current console data over a stale hard-coded list for the remaining template settings.
30
+
31
+ ## 3. Create the target app
32
+
33
+ 1. Choose `创建企业自建应用` and fill the requested name and description.
34
+ 2. Reuse the lowercase `chatccc` icon only when imitation was requested, and verify its crop preview.
35
+ 3. Click the final `创建` action only after confirmation.
36
+ 4. Click once and wait for SPA navigation. Verify the exact app name, App ID, URL, and status before retrying; the console can temporarily show stale text after a successful mutation.
37
+
38
+ ## 4. Configure the complete README-defined ChatCCC setup
39
+
40
+ Perform the configuration in this order:
41
+
42
+ 1. Add the `机器人` application capability and verify that the page offers `删除能力`, which means the capability is enabled.
43
+ 2. Configure permissions from the README, not from the lowercase template:
44
+ - under `权限管理`, search for the `im:` prefix and enable every permission whose name starts with `im:`;
45
+ - search for the `cardkit:` prefix and enable every permission whose name starts with `cardkit:`;
46
+ - separately search for the exact scope `im:message.p2p_msg:readonly` and verify that it is enabled. This private-message read permission is easy to miss and must not be inferred from other message permissions;
47
+ - confirm all permission changes and complete any required administrator approval;
48
+ - do not use template permission export/import as an authoritative shortcut, because the template may be incomplete or stale.
49
+ 3. Under `事件与回调` > `事件配置`, set the subscription mode to `使用长连接接收事件`, then add every event present in the template. The verified baseline is:
50
+ - `im.chat.disbanded_v1`
51
+ - `im.chat.member.bot.added_v1`
52
+ - `im.chat.member.bot.deleted_v1`
53
+ - `im.chat.member.user.added_v1`
54
+ - `im.chat.member.user.deleted_v1`
55
+ - `im.chat.member.user.withdrawn_v1`
56
+ - `im.message.bot_muted_v1`
57
+ - `im.message.message_read_v1`
58
+ - `im.message.reaction.created_v1`
59
+ - `im.message.reaction.deleted_v1`
60
+ - `im.message.recalled_v1`
61
+ - `im.message.receive_v1`
62
+ 4. Under `回调配置`, independently set `使用长连接接收回调` and add `card.action.trigger`. Configuring the event mode does not configure the callback mode.
63
+ 5. Verify that every listed event shows a sufficient permission as `已开通`.
64
+
65
+ The README requires the bot capability, every permission whose name starts with `im:` or `cardkit:`, explicit verification of `im:message.p2p_msg:readonly`, `im.message.receive_v1`, and `card.action.trigger`. A clone request may copy the current template's presentation, subscriptions, availability, and release settings, but it must not weaken the README permission rule.
66
+
67
+ ## 5. Create and publish a version
68
+
69
+ 1. Open `版本管理与发布` and create a version such as `1.0.0`.
70
+ 2. Keep mobile and desktop default abilities set to `机器人` and write a meaningful update note.
71
+ 3. Match the requested or template availability. For a personal computer, default to the owner-only internal range and leave external group/private-chat sharing disabled unless explicitly requested.
72
+ 4. Save the version, then complete the separate `确认发布` action. A successful version creation alone is not a release.
73
+ 5. Refresh the version list and require all of the following evidence before reporting success:
74
+ - application status `已启用`;
75
+ - banner `当前修改均已发布`;
76
+ - version status `已发布` with a publication time.
77
+ 6. If administrator review is required, submit everything authorized and report the exact remaining approval state.
78
+
79
+ ## 6. Verify and hand off safely
80
+
81
+ - Re-open the bot, permission, event/callback, and version pages after publication. Verify the bot is enabled, all current `im:` and `cardkit:` permissions are enabled, `im:message.p2p_msg:readonly` is explicitly present, both subscription modes are long connection, event/callback identifiers match, and the version is published.
82
+ - Treat network responses and a refreshed page as stronger evidence than an immediately stale SPA view. Never repeat a create, add, or publish action only because the first page read is stale.
83
+ - Report the app name, App ID, capability, whether the README permission checks passed, event/callback counts, version, release state, and any remaining action.
84
+ - Never print the App Secret. If the user explicitly asks to configure ChatCCC, transfer the App ID and App Secret directly into the local private configuration without echoing the secret in commands, logs, screenshots, files tracked by Git, or chat.
85
+ - Do not modify local ChatCCC configuration or transmit credentials elsewhere unless explicitly authorized.
@@ -1,85 +1,85 @@
1
- ---
2
- name: create-chatccc-feishu-app
3
- description: Create, clone, or configure a Feishu enterprise self-built bot application for ChatCCC. Use when asked to create a ChatCCC Feishu app, imitate an existing lowercase `chatccc` app, prepare a bot for another computer, or configure its bot capability, `im:`/`cardkit:` permissions, events, credentials, version, and internal release from this repository's README.
4
- ---
5
-
6
- # Create a ChatCCC Feishu App
7
-
8
- Use the logged-in Feishu developer console to create and completely configure a ChatCCC bot app. Treat this repository's README as the authoritative source for permissions and required capabilities. When imitation is requested, use the existing app named exactly lowercase `chatccc` only as a template for presentation, subscriptions, and release settings.
9
-
10
- ## 1. Establish the target and authorization
11
-
12
- - Read the `README.md` section `#### 飞书(推荐)` before changing the console.
13
- - Determine the requested app name, target computer, description, icon, availability, and whether the user wants configuration only or a real release. Derive a concise description when one is not supplied; for example, `用飞书聊天控制<目标电脑>上的 Claude Code / Cursor / Codex。`.
14
- - Use the browser surface the user requested. If the user specifies Chrome DevTools/CDP, connect directly to `chromeDevtools.port` or the README default `15166`; do not substitute extension-based Chrome control.
15
- - Obtain action-time confirmation before creating the app, granting permissions, saving event/callback subscriptions, or publishing. One explicit instruction such as `完整配置并真正发布` may authorize the listed actions as a batch.
16
-
17
- ## 2. Inventory the lowercase template
18
-
19
- 1. Open `https://open.feishu.cn/app?from=devbotmenu` in the authenticated browser.
20
- 2. Open the app named exactly lowercase `chatccc` in a separate tab.
21
- 3. Record its non-secret configuration:
22
- - app description and icon;
23
- - application capabilities, especially `机器人`;
24
- - event and callback subscription modes;
25
- - every event and callback identifier;
26
- - version availability, external sharing choices, and release state.
27
- 4. Never reveal, log, export to chat, or persist the template App Secret.
28
-
29
- Do not use the template's permission set or permission counts as the source of truth. Permissions must always follow the current README rule below. Prefer current console data over a stale hard-coded list for the remaining template settings.
30
-
31
- ## 3. Create the target app
32
-
33
- 1. Choose `创建企业自建应用` and fill the requested name and description.
34
- 2. Reuse the lowercase `chatccc` icon only when imitation was requested, and verify its crop preview.
35
- 3. Click the final `创建` action only after confirmation.
36
- 4. Click once and wait for SPA navigation. Verify the exact app name, App ID, URL, and status before retrying; the console can temporarily show stale text after a successful mutation.
37
-
38
- ## 4. Configure the complete README-defined ChatCCC setup
39
-
40
- Perform the configuration in this order:
41
-
42
- 1. Add the `机器人` application capability and verify that the page offers `删除能力`, which means the capability is enabled.
43
- 2. Configure permissions from the README, not from the lowercase template:
44
- - under `权限管理`, search for the `im:` prefix and enable every permission whose name starts with `im:`;
45
- - search for the `cardkit:` prefix and enable every permission whose name starts with `cardkit:`;
46
- - separately search for the exact scope `im:message.p2p_msg:readonly` and verify that it is enabled. This private-message read permission is easy to miss and must not be inferred from other message permissions;
47
- - confirm all permission changes and complete any required administrator approval;
48
- - do not use template permission export/import as an authoritative shortcut, because the template may be incomplete or stale.
49
- 3. Under `事件与回调` > `事件配置`, set the subscription mode to `使用长连接接收事件`, then add every event present in the template. The verified baseline is:
50
- - `im.chat.disbanded_v1`
51
- - `im.chat.member.bot.added_v1`
52
- - `im.chat.member.bot.deleted_v1`
53
- - `im.chat.member.user.added_v1`
54
- - `im.chat.member.user.deleted_v1`
55
- - `im.chat.member.user.withdrawn_v1`
56
- - `im.message.bot_muted_v1`
57
- - `im.message.message_read_v1`
58
- - `im.message.reaction.created_v1`
59
- - `im.message.reaction.deleted_v1`
60
- - `im.message.recalled_v1`
61
- - `im.message.receive_v1`
62
- 4. Under `回调配置`, independently set `使用长连接接收回调` and add `card.action.trigger`. Configuring the event mode does not configure the callback mode.
63
- 5. Verify that every listed event shows a sufficient permission as `已开通`.
64
-
65
- The README requires the bot capability, every permission whose name starts with `im:` or `cardkit:`, explicit verification of `im:message.p2p_msg:readonly`, `im.message.receive_v1`, and `card.action.trigger`. A clone request may copy the current template's presentation, subscriptions, availability, and release settings, but it must not weaken the README permission rule.
66
-
67
- ## 5. Create and publish a version
68
-
69
- 1. Open `版本管理与发布` and create a version such as `1.0.0`.
70
- 2. Keep mobile and desktop default abilities set to `机器人` and write a meaningful update note.
71
- 3. Match the requested or template availability. For a personal computer, default to the owner-only internal range and leave external group/private-chat sharing disabled unless explicitly requested.
72
- 4. Save the version, then complete the separate `确认发布` action. A successful version creation alone is not a release.
73
- 5. Refresh the version list and require all of the following evidence before reporting success:
74
- - application status `已启用`;
75
- - banner `当前修改均已发布`;
76
- - version status `已发布` with a publication time.
77
- 6. If administrator review is required, submit everything authorized and report the exact remaining approval state.
78
-
79
- ## 6. Verify and hand off safely
80
-
81
- - Re-open the bot, permission, event/callback, and version pages after publication. Verify the bot is enabled, all current `im:` and `cardkit:` permissions are enabled, `im:message.p2p_msg:readonly` is explicitly present, both subscription modes are long connection, event/callback identifiers match, and the version is published.
82
- - Treat network responses and a refreshed page as stronger evidence than an immediately stale SPA view. Never repeat a create, add, or publish action only because the first page read is stale.
83
- - Report the app name, App ID, capability, whether the README permission checks passed, event/callback counts, version, release state, and any remaining action.
84
- - Never print the App Secret. If the user explicitly asks to configure ChatCCC, transfer the App ID and App Secret directly into the local private configuration without echoing the secret in commands, logs, screenshots, files tracked by Git, or chat.
85
- - Do not modify local ChatCCC configuration or transmit credentials elsewhere unless explicitly authorized.
1
+ ---
2
+ name: create-chatccc-feishu-app
3
+ description: Create, clone, or configure a Feishu enterprise self-built bot application for ChatCCC. Use when asked to create a ChatCCC Feishu app, imitate an existing lowercase `chatccc` app, prepare a bot for another computer, or configure its bot capability, `im:`/`cardkit:` permissions, events, credentials, version, and internal release from this repository's README.
4
+ ---
5
+
6
+ # Create a ChatCCC Feishu App
7
+
8
+ Use the logged-in Feishu developer console to create and completely configure a ChatCCC bot app. Treat this repository's README as the authoritative source for permissions and required capabilities. When imitation is requested, use the existing app named exactly lowercase `chatccc` only as a template for presentation, subscriptions, and release settings.
9
+
10
+ ## 1. Establish the target and authorization
11
+
12
+ - Read the `README.md` section `#### 飞书(推荐)` before changing the console.
13
+ - Determine the requested app name, target computer, description, icon, availability, and whether the user wants configuration only or a real release. Derive a concise description when one is not supplied; for example, `用飞书聊天控制<目标电脑>上的 Claude Code / Cursor / Codex。`.
14
+ - Use the browser surface the user requested. If the user specifies Chrome DevTools/CDP, connect directly to `chromeDevtools.port` or the README default `15166`; do not substitute extension-based Chrome control.
15
+ - Obtain action-time confirmation before creating the app, granting permissions, saving event/callback subscriptions, or publishing. One explicit instruction such as `完整配置并真正发布` may authorize the listed actions as a batch.
16
+
17
+ ## 2. Inventory the lowercase template
18
+
19
+ 1. Open `https://open.feishu.cn/app?from=devbotmenu` in the authenticated browser.
20
+ 2. Open the app named exactly lowercase `chatccc` in a separate tab.
21
+ 3. Record its non-secret configuration:
22
+ - app description and icon;
23
+ - application capabilities, especially `机器人`;
24
+ - event and callback subscription modes;
25
+ - every event and callback identifier;
26
+ - version availability, external sharing choices, and release state.
27
+ 4. Never reveal, log, export to chat, or persist the template App Secret.
28
+
29
+ Do not use the template's permission set or permission counts as the source of truth. Permissions must always follow the current README rule below. Prefer current console data over a stale hard-coded list for the remaining template settings.
30
+
31
+ ## 3. Create the target app
32
+
33
+ 1. Choose `创建企业自建应用` and fill the requested name and description.
34
+ 2. Reuse the lowercase `chatccc` icon only when imitation was requested, and verify its crop preview.
35
+ 3. Click the final `创建` action only after confirmation.
36
+ 4. Click once and wait for SPA navigation. Verify the exact app name, App ID, URL, and status before retrying; the console can temporarily show stale text after a successful mutation.
37
+
38
+ ## 4. Configure the complete README-defined ChatCCC setup
39
+
40
+ Perform the configuration in this order:
41
+
42
+ 1. Add the `机器人` application capability and verify that the page offers `删除能力`, which means the capability is enabled.
43
+ 2. Configure permissions from the README, not from the lowercase template:
44
+ - under `权限管理`, search for the `im:` prefix and enable every permission whose name starts with `im:`;
45
+ - search for the `cardkit:` prefix and enable every permission whose name starts with `cardkit:`;
46
+ - separately search for the exact scope `im:message.p2p_msg:readonly` and verify that it is enabled. This private-message read permission is easy to miss and must not be inferred from other message permissions;
47
+ - confirm all permission changes and complete any required administrator approval;
48
+ - do not use template permission export/import as an authoritative shortcut, because the template may be incomplete or stale.
49
+ 3. Under `事件与回调` > `事件配置`, set the subscription mode to `使用长连接接收事件`, then add every event present in the template. The verified baseline is:
50
+ - `im.chat.disbanded_v1`
51
+ - `im.chat.member.bot.added_v1`
52
+ - `im.chat.member.bot.deleted_v1`
53
+ - `im.chat.member.user.added_v1`
54
+ - `im.chat.member.user.deleted_v1`
55
+ - `im.chat.member.user.withdrawn_v1`
56
+ - `im.message.bot_muted_v1`
57
+ - `im.message.message_read_v1`
58
+ - `im.message.reaction.created_v1`
59
+ - `im.message.reaction.deleted_v1`
60
+ - `im.message.recalled_v1`
61
+ - `im.message.receive_v1`
62
+ 4. Under `回调配置`, independently set `使用长连接接收回调` and add `card.action.trigger`. Configuring the event mode does not configure the callback mode.
63
+ 5. Verify that every listed event shows a sufficient permission as `已开通`.
64
+
65
+ The README requires the bot capability, every permission whose name starts with `im:` or `cardkit:`, explicit verification of `im:message.p2p_msg:readonly`, `im.message.receive_v1`, and `card.action.trigger`. A clone request may copy the current template's presentation, subscriptions, availability, and release settings, but it must not weaken the README permission rule.
66
+
67
+ ## 5. Create and publish a version
68
+
69
+ 1. Open `版本管理与发布` and create a version such as `1.0.0`.
70
+ 2. Keep mobile and desktop default abilities set to `机器人` and write a meaningful update note.
71
+ 3. Match the requested or template availability. For a personal computer, default to the owner-only internal range and leave external group/private-chat sharing disabled unless explicitly requested.
72
+ 4. Save the version, then complete the separate `确认发布` action. A successful version creation alone is not a release.
73
+ 5. Refresh the version list and require all of the following evidence before reporting success:
74
+ - application status `已启用`;
75
+ - banner `当前修改均已发布`;
76
+ - version status `已发布` with a publication time.
77
+ 6. If administrator review is required, submit everything authorized and report the exact remaining approval state.
78
+
79
+ ## 6. Verify and hand off safely
80
+
81
+ - Re-open the bot, permission, event/callback, and version pages after publication. Verify the bot is enabled, all current `im:` and `cardkit:` permissions are enabled, `im:message.p2p_msg:readonly` is explicitly present, both subscription modes are long connection, event/callback identifiers match, and the version is published.
82
+ - Treat network responses and a refreshed page as stronger evidence than an immediately stale SPA view. Never repeat a create, add, or publish action only because the first page read is stale.
83
+ - Report the app name, App ID, capability, whether the README permission checks passed, event/callback counts, version, release state, and any remaining action.
84
+ - Never print the App Secret. If the user explicitly asks to configure ChatCCC, transfer the App ID and App Secret directly into the local private configuration without echoing the secret in commands, logs, screenshots, files tracked by Git, or chat.
85
+ - Do not modify local ChatCCC configuration or transmit credentials elsewhere unless explicitly authorized.
@@ -1,85 +1,85 @@
1
- ---
2
- name: create-chatccc-feishu-app
3
- description: Create, clone, or configure a Feishu enterprise self-built bot application for ChatCCC. Use when asked to create a ChatCCC Feishu app, imitate an existing lowercase `chatccc` app, prepare a bot for another computer, or configure its bot capability, `im:`/`cardkit:` permissions, events, credentials, version, and internal release from this repository's README.
4
- ---
5
-
6
- # Create a ChatCCC Feishu App
7
-
8
- Use the logged-in Feishu developer console to create and completely configure a ChatCCC bot app. Treat this repository's README as the authoritative source for permissions and required capabilities. When imitation is requested, use the existing app named exactly lowercase `chatccc` only as a template for presentation, subscriptions, and release settings.
9
-
10
- ## 1. Establish the target and authorization
11
-
12
- - Read the `README.md` section `#### 飞书(推荐)` before changing the console.
13
- - Determine the requested app name, target computer, description, icon, availability, and whether the user wants configuration only or a real release. Derive a concise description when one is not supplied; for example, `用飞书聊天控制<目标电脑>上的 Claude Code / Cursor / Codex。`.
14
- - Use the browser surface the user requested. If the user specifies Chrome DevTools/CDP, connect directly to `chromeDevtools.port` or the README default `15166`; do not substitute extension-based Chrome control.
15
- - Obtain action-time confirmation before creating the app, granting permissions, saving event/callback subscriptions, or publishing. One explicit instruction such as `完整配置并真正发布` may authorize the listed actions as a batch.
16
-
17
- ## 2. Inventory the lowercase template
18
-
19
- 1. Open `https://open.feishu.cn/app?from=devbotmenu` in the authenticated browser.
20
- 2. Open the app named exactly lowercase `chatccc` in a separate tab.
21
- 3. Record its non-secret configuration:
22
- - app description and icon;
23
- - application capabilities, especially `机器人`;
24
- - event and callback subscription modes;
25
- - every event and callback identifier;
26
- - version availability, external sharing choices, and release state.
27
- 4. Never reveal, log, export to chat, or persist the template App Secret.
28
-
29
- Do not use the template's permission set or permission counts as the source of truth. Permissions must always follow the current README rule below. Prefer current console data over a stale hard-coded list for the remaining template settings.
30
-
31
- ## 3. Create the target app
32
-
33
- 1. Choose `创建企业自建应用` and fill the requested name and description.
34
- 2. Reuse the lowercase `chatccc` icon only when imitation was requested, and verify its crop preview.
35
- 3. Click the final `创建` action only after confirmation.
36
- 4. Click once and wait for SPA navigation. Verify the exact app name, App ID, URL, and status before retrying; the console can temporarily show stale text after a successful mutation.
37
-
38
- ## 4. Configure the complete README-defined ChatCCC setup
39
-
40
- Perform the configuration in this order:
41
-
42
- 1. Add the `机器人` application capability and verify that the page offers `删除能力`, which means the capability is enabled.
43
- 2. Configure permissions from the README, not from the lowercase template:
44
- - under `权限管理`, search for the `im:` prefix and enable every permission whose name starts with `im:`;
45
- - search for the `cardkit:` prefix and enable every permission whose name starts with `cardkit:`;
46
- - separately search for the exact scope `im:message.p2p_msg:readonly` and verify that it is enabled. This private-message read permission is easy to miss and must not be inferred from other message permissions;
47
- - confirm all permission changes and complete any required administrator approval;
48
- - do not use template permission export/import as an authoritative shortcut, because the template may be incomplete or stale.
49
- 3. Under `事件与回调` > `事件配置`, set the subscription mode to `使用长连接接收事件`, then add every event present in the template. The verified baseline is:
50
- - `im.chat.disbanded_v1`
51
- - `im.chat.member.bot.added_v1`
52
- - `im.chat.member.bot.deleted_v1`
53
- - `im.chat.member.user.added_v1`
54
- - `im.chat.member.user.deleted_v1`
55
- - `im.chat.member.user.withdrawn_v1`
56
- - `im.message.bot_muted_v1`
57
- - `im.message.message_read_v1`
58
- - `im.message.reaction.created_v1`
59
- - `im.message.reaction.deleted_v1`
60
- - `im.message.recalled_v1`
61
- - `im.message.receive_v1`
62
- 4. Under `回调配置`, independently set `使用长连接接收回调` and add `card.action.trigger`. Configuring the event mode does not configure the callback mode.
63
- 5. Verify that every listed event shows a sufficient permission as `已开通`.
64
-
65
- The README requires the bot capability, every permission whose name starts with `im:` or `cardkit:`, explicit verification of `im:message.p2p_msg:readonly`, `im.message.receive_v1`, and `card.action.trigger`. A clone request may copy the current template's presentation, subscriptions, availability, and release settings, but it must not weaken the README permission rule.
66
-
67
- ## 5. Create and publish a version
68
-
69
- 1. Open `版本管理与发布` and create a version such as `1.0.0`.
70
- 2. Keep mobile and desktop default abilities set to `机器人` and write a meaningful update note.
71
- 3. Match the requested or template availability. For a personal computer, default to the owner-only internal range and leave external group/private-chat sharing disabled unless explicitly requested.
72
- 4. Save the version, then complete the separate `确认发布` action. A successful version creation alone is not a release.
73
- 5. Refresh the version list and require all of the following evidence before reporting success:
74
- - application status `已启用`;
75
- - banner `当前修改均已发布`;
76
- - version status `已发布` with a publication time.
77
- 6. If administrator review is required, submit everything authorized and report the exact remaining approval state.
78
-
79
- ## 6. Verify and hand off safely
80
-
81
- - Re-open the bot, permission, event/callback, and version pages after publication. Verify the bot is enabled, all current `im:` and `cardkit:` permissions are enabled, `im:message.p2p_msg:readonly` is explicitly present, both subscription modes are long connection, event/callback identifiers match, and the version is published.
82
- - Treat network responses and a refreshed page as stronger evidence than an immediately stale SPA view. Never repeat a create, add, or publish action only because the first page read is stale.
83
- - Report the app name, App ID, capability, whether the README permission checks passed, event/callback counts, version, release state, and any remaining action.
84
- - Never print the App Secret. If the user explicitly asks to configure ChatCCC, transfer the App ID and App Secret directly into the local private configuration without echoing the secret in commands, logs, screenshots, files tracked by Git, or chat.
85
- - Do not modify local ChatCCC configuration or transmit credentials elsewhere unless explicitly authorized.
1
+ ---
2
+ name: create-chatccc-feishu-app
3
+ description: Create, clone, or configure a Feishu enterprise self-built bot application for ChatCCC. Use when asked to create a ChatCCC Feishu app, imitate an existing lowercase `chatccc` app, prepare a bot for another computer, or configure its bot capability, `im:`/`cardkit:` permissions, events, credentials, version, and internal release from this repository's README.
4
+ ---
5
+
6
+ # Create a ChatCCC Feishu App
7
+
8
+ Use the logged-in Feishu developer console to create and completely configure a ChatCCC bot app. Treat this repository's README as the authoritative source for permissions and required capabilities. When imitation is requested, use the existing app named exactly lowercase `chatccc` only as a template for presentation, subscriptions, and release settings.
9
+
10
+ ## 1. Establish the target and authorization
11
+
12
+ - Read the `README.md` section `#### 飞书(推荐)` before changing the console.
13
+ - Determine the requested app name, target computer, description, icon, availability, and whether the user wants configuration only or a real release. Derive a concise description when one is not supplied; for example, `用飞书聊天控制<目标电脑>上的 Claude Code / Cursor / Codex。`.
14
+ - Use the browser surface the user requested. If the user specifies Chrome DevTools/CDP, connect directly to `chromeDevtools.port` or the README default `15166`; do not substitute extension-based Chrome control.
15
+ - Obtain action-time confirmation before creating the app, granting permissions, saving event/callback subscriptions, or publishing. One explicit instruction such as `完整配置并真正发布` may authorize the listed actions as a batch.
16
+
17
+ ## 2. Inventory the lowercase template
18
+
19
+ 1. Open `https://open.feishu.cn/app?from=devbotmenu` in the authenticated browser.
20
+ 2. Open the app named exactly lowercase `chatccc` in a separate tab.
21
+ 3. Record its non-secret configuration:
22
+ - app description and icon;
23
+ - application capabilities, especially `机器人`;
24
+ - event and callback subscription modes;
25
+ - every event and callback identifier;
26
+ - version availability, external sharing choices, and release state.
27
+ 4. Never reveal, log, export to chat, or persist the template App Secret.
28
+
29
+ Do not use the template's permission set or permission counts as the source of truth. Permissions must always follow the current README rule below. Prefer current console data over a stale hard-coded list for the remaining template settings.
30
+
31
+ ## 3. Create the target app
32
+
33
+ 1. Choose `创建企业自建应用` and fill the requested name and description.
34
+ 2. Reuse the lowercase `chatccc` icon only when imitation was requested, and verify its crop preview.
35
+ 3. Click the final `创建` action only after confirmation.
36
+ 4. Click once and wait for SPA navigation. Verify the exact app name, App ID, URL, and status before retrying; the console can temporarily show stale text after a successful mutation.
37
+
38
+ ## 4. Configure the complete README-defined ChatCCC setup
39
+
40
+ Perform the configuration in this order:
41
+
42
+ 1. Add the `机器人` application capability and verify that the page offers `删除能力`, which means the capability is enabled.
43
+ 2. Configure permissions from the README, not from the lowercase template:
44
+ - under `权限管理`, search for the `im:` prefix and enable every permission whose name starts with `im:`;
45
+ - search for the `cardkit:` prefix and enable every permission whose name starts with `cardkit:`;
46
+ - separately search for the exact scope `im:message.p2p_msg:readonly` and verify that it is enabled. This private-message read permission is easy to miss and must not be inferred from other message permissions;
47
+ - confirm all permission changes and complete any required administrator approval;
48
+ - do not use template permission export/import as an authoritative shortcut, because the template may be incomplete or stale.
49
+ 3. Under `事件与回调` > `事件配置`, set the subscription mode to `使用长连接接收事件`, then add every event present in the template. The verified baseline is:
50
+ - `im.chat.disbanded_v1`
51
+ - `im.chat.member.bot.added_v1`
52
+ - `im.chat.member.bot.deleted_v1`
53
+ - `im.chat.member.user.added_v1`
54
+ - `im.chat.member.user.deleted_v1`
55
+ - `im.chat.member.user.withdrawn_v1`
56
+ - `im.message.bot_muted_v1`
57
+ - `im.message.message_read_v1`
58
+ - `im.message.reaction.created_v1`
59
+ - `im.message.reaction.deleted_v1`
60
+ - `im.message.recalled_v1`
61
+ - `im.message.receive_v1`
62
+ 4. Under `回调配置`, independently set `使用长连接接收回调` and add `card.action.trigger`. Configuring the event mode does not configure the callback mode.
63
+ 5. Verify that every listed event shows a sufficient permission as `已开通`.
64
+
65
+ The README requires the bot capability, every permission whose name starts with `im:` or `cardkit:`, explicit verification of `im:message.p2p_msg:readonly`, `im.message.receive_v1`, and `card.action.trigger`. A clone request may copy the current template's presentation, subscriptions, availability, and release settings, but it must not weaken the README permission rule.
66
+
67
+ ## 5. Create and publish a version
68
+
69
+ 1. Open `版本管理与发布` and create a version such as `1.0.0`.
70
+ 2. Keep mobile and desktop default abilities set to `机器人` and write a meaningful update note.
71
+ 3. Match the requested or template availability. For a personal computer, default to the owner-only internal range and leave external group/private-chat sharing disabled unless explicitly requested.
72
+ 4. Save the version, then complete the separate `确认发布` action. A successful version creation alone is not a release.
73
+ 5. Refresh the version list and require all of the following evidence before reporting success:
74
+ - application status `已启用`;
75
+ - banner `当前修改均已发布`;
76
+ - version status `已发布` with a publication time.
77
+ 6. If administrator review is required, submit everything authorized and report the exact remaining approval state.
78
+
79
+ ## 6. Verify and hand off safely
80
+
81
+ - Re-open the bot, permission, event/callback, and version pages after publication. Verify the bot is enabled, all current `im:` and `cardkit:` permissions are enabled, `im:message.p2p_msg:readonly` is explicitly present, both subscription modes are long connection, event/callback identifiers match, and the version is published.
82
+ - Treat network responses and a refreshed page as stronger evidence than an immediately stale SPA view. Never repeat a create, add, or publish action only because the first page read is stale.
83
+ - Report the app name, App ID, capability, whether the README permission checks passed, event/callback counts, version, release state, and any remaining action.
84
+ - Never print the App Secret. If the user explicitly asks to configure ChatCCC, transfer the App ID and App Secret directly into the local private configuration without echoing the secret in commands, logs, screenshots, files tracked by Git, or chat.
85
+ - Do not modify local ChatCCC configuration or transmit credentials elsewhere unless explicitly authorized.
package/README.md CHANGED
@@ -227,7 +227,11 @@ Claude Code、Cursor 和 Codex 需要对应的本地工具;CCC Agent 内置于
227
227
 
228
228
  #### CCC Agent
229
229
 
230
- CCC Agent 是 ChatCCC 内置的编程 Agent,不需要额外安装 CLI,开箱即用。在首次配置向导或 Web 管理页中启用后,填写 API Key、Base URL 和模型即可使用;它可以设为 `/new` 的默认 Agent,也可以通过 `/new ccc` 显式创建会话。
230
+ CCC Agent 是 ChatCCC 内置的编程 Agent,不需要额外安装 CLI,开箱即用。在首次配置向导或 Web 管理页中启用后,填写 API Key、Base URL 和模型即可使用;它可以设为 `/new` 的默认 Agent,也可以通过 `/new ccc` 显式创建会话。
231
+
232
+ CCC Agent 支持图片理解:飞书/微信发送的图片与独立 DeepCCC 的 Web/CLI 附件共用内核,可看多张截图、图表及本地 `read_image` 工具产物。支持 PNG/JPEG/WebP/GIF,每条最多 10 张、单图 20 MiB、图片合计 24 MiB。主模型支持视觉时直接传图;主模型不支持时,可在设置页填写“图片模型”(`ccc.visionModel`,如 `deepseek-flash`),先由它观察图片,再由主模型继续任务。留空跟随独立 DeepCCC 的 `visionModel`;两边都未配置则使用主模型原生视觉。图片模型复用当前 API Key/Base URL/协议,界面显示实际使用的模型;错误不会静默降级。历史保存附件引用,日志过滤图片编码。详见 [DeepCCC 图片与 CLI 用法](deepccc-agent/README.md)。
233
+
234
+ 纯 CLI 用户可以运行 `cccagent --image "C:\截图\报错.png"` 后输入问题,或在运行中的交互终端等待回复结束后输入 `/image "图片路径"`,再发下一条问题。多图重复添加;一次性运行可用 `cccagent --stream-json --prompt "解释截图" --image "图片路径"`。`cccagent` 读取 `~/.deepccc/config.json` 或 `DEEPCCC_*` 环境变量。
231
235
 
232
236
  CCC Agent 支持**协作式让位**:任务运行期间你可以继续在群里发消息,ChatCCC 会在 Agent 的每个模型步骤边界把新消息注入当前任务,不打断正在执行的工具步骤、不新开一轮对话。已完成的中间工作会保留,Agent 收到插话后会调整后续方向。运行中的消息进入独立的注入队列(深度 50),与整轮排队(深度 1)分离。飞书中每条消息实际注入后,机器人会发送一条最多 200 字的回执,冻结注入前的过程卡片,并用新的“生成中”卡片展示后续过程。
233
237
 
@@ -438,7 +442,7 @@ ChatCCC 通过 Codex 的 **app-server 模式**(一个常驻进程 + WebSocket
438
442
  | `/cd` | 查看或设置后续新建会话的默认工作目录,不改变当前会话;飞书私聊自身始终使用系统用户目录 |
439
443
  | `/sessions` | 查看所有会话状态 |
440
444
  | `/session <数字>` | 将当前群聊切换到 `/sessions` 列表中的指定会话;飞书私聊不支持切换 |
441
- | `/usage` | 查看当前会话对应 Agent 的用量;Codex 显示 5h/7天窗口,主动重置次数查询失败时会明确展示上次成功快照及其查询时间(缓存结果不提供重置按钮);Cursor 显示当前周期用量,CCC Agent 和 DSH 仅在官方 DeepSeek 端点时显示账户余额(其他兼容端点自动跳过) |
445
+ | `/usage` | 查看当前会话对应 Agent 的用量;Codex 使用本机 Codex 登录凭据中的账户 ID 查询额度,只显示接口实际返回的 5h/7天窗口,主动重置次数查询失败时会明确展示上次成功快照及其查询时间(缓存结果不提供重置按钮);Cursor 显示当前周期用量,CCC Agent 和 DSH 仅在官方 DeepSeek 端点时显示账户余额(其他兼容端点自动跳过) |
442
446
  | `/git <子命令>` | 在当前会话工作目录执行 `git ...` 并回传输出 |
443
447
  | `/abd<内容>` | 去掉 `/abd` 前缀后把内容发给 Agent,并在消息末尾追加第一性原理需求澄清提示 |
444
448
  | `/plan <内容>` | 只读计划模式:仅允许读文件和 stop-stuck-loop 请求,不执行任何写操作 |