@lansenger-pm/openclaw-lansenger-channel 2.0.3 → 2.0.4
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.
package/package.json
CHANGED
|
@@ -138,13 +138,15 @@ Parameters:
|
|
|
138
138
|
```
|
|
139
139
|
|
|
140
140
|
Example flow:
|
|
141
|
-
1. `write` tool → creates
|
|
141
|
+
1. `write` tool → creates file in workspace (e.g. `~/.openclaw/workspace/report.md`)
|
|
142
142
|
2. `sendAttachment` action → sends the file to the user on Lansenger
|
|
143
143
|
|
|
144
144
|
**Rules:**
|
|
145
145
|
- Always use absolute paths for `filePath`
|
|
146
|
+
- Files MUST be in the workspace directory (`~/.openclaw/workspace/`) — if the source file is elsewhere (e.g. `~/Documents/`), copy it to workspace first using the `bash` tool, then `sendAttachment` the workspace copy
|
|
146
147
|
- `caption` is plain text only (Markdown will NOT render in attachment messages)
|
|
147
148
|
- If you need both formatted explanation AND a file attachment, send the formatted text first (Markdown works), then `sendAttachment` separately for the file
|
|
149
|
+
- `MEDIA:` tags in reply text also work for workspace files, but `sendAttachment` is more reliable for explicit file delivery
|
|
148
150
|
- Supported file types: images (.jpg/.png/.gif/.webp), videos (.mp4/.mov), documents (.pdf/.md/.txt/.zip), etc.
|
|
149
151
|
|
|
150
152
|
## Critical Pitfalls
|