codex-to-im 1.0.11 → 1.0.12

package/README.md

@@ -10,6 +10,8 @@ The product is no longer centered around a Codex skill. The main path is:
 4. Start the bridge in the background
 5. Bind real desktop Codex threads to Feishu or Weixin chats
 
+Optional: if you want Codex to know it can send local files or images back to IM without relying on bridge-injected prompt text, install the bundled `codex-to-im` skill from the workbench.
+
 ## Project Origin
 
 The current codebase is a consolidated continuation of two earlier repositories:

package/README_CN.md

@@ -10,6 +10,8 @@
 4. 在后台启动 bridge
 5. 把真实的桌面 Codex thread 绑定到飞书或微信聊天
 
+可选：如果你希望 Codex 在不依赖 bridge 注入提示词的前提下，知道“可以把本地图片/文件回发到 IM”，可以在工作台里安装附带的 `codex-to-im` skill。
+
 ## 项目来源
 
 当前这套代码是在两个早期仓库的基础上整理和改造出来的：

package/SKILL.md

@@ -0,0 +1,67 @@
+---
+name: codex-to-im
+description: Use this skill when working through Codex-to-IM and you need Codex to send a local image or file back to the current IM chat. It teaches the attachment-send protocol and when to use it.
+---
+
+# Codex-to-IM attachment sending
+
+Use this skill only when the user is chatting through Codex-to-IM and wants you to send a generated or existing local artifact back to the IM chat.
+
+## What this skill does
+
+Codex-to-IM can send local files back to the chat after your reply. You trigger that by including one or more `<cti-send>...</cti-send>` blocks in your final answer.
+
+Supported artifact kinds:
+
+- `image`
+- `file`
+
+## Required format
+
+Output valid JSON inside the block, with no markdown fence.
+
+Single artifact:
+
+```text
+<cti-send>
+{"type":"image","path":"D:\\path\\to\\result.png","caption":"optional caption"}
+</cti-send>
+```
+
+or
+
+```text
+<cti-send>
+{"type":"file","path":"D:\\path\\to\\report.pdf","caption":"optional caption"}
+</cti-send>
+```
+
+Multiple artifacts:
+
+```text
+<cti-send>
+{"items":[
+  {"type":"image","path":"D:\\path\\to\\result.png"},
+  {"type":"file","path":"D:\\path\\to\\report.pdf"}
+]}
+</cti-send>
+```
+
+## Rules
+
+- The `path` must be an absolute local path.
+- The file must already exist before you emit the block.
+- Keep normal user-facing explanation outside the `<cti-send>` block.
+- Do not invent artifacts that were not actually created or found.
+- If you are unsure whether the file exists, verify first.
+- If the channel probably does not support the artifact well, explain that plainly instead of inventing a successful send.
+
+## When to use
+
+Use this protocol when the user asks you to:
+
+- send a generated chart, diagram, screenshot, or edited image
+- send a report, archive, patch, PDF, spreadsheet, or other output file
+- send the final result as an attachment instead of only pasting text
+
+Do not use it for ordinary text replies.

package/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Codex to IM"
+  short_description: "Help Codex send local files back to IM chats"
+  default_prompt: "Use $codex-to-im when you need to send a generated image or file back to the current Codex-to-IM chat."

package/dist/cli.mjs

@@ -3,6 +3,7 @@ import { createRequire } from 'module'; const require = createRequire(import.met
 
 // src/service-manager.ts
 import fs2 from "node:fs";
+import os2 from "node:os";
 import path2 from "node:path";
 import { spawn } from "node:child_process";
 import { fileURLToPath } from "node:url";