openclaw-threema 0.6.1 → 0.6.3
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/CHANGELOG.md +84 -0
- package/dist/index.js +2003 -0
- package/index.ts +148 -32
- package/openclaw.plugin.json +87 -1
- package/package.json +18 -5
package/CHANGELOG.md
ADDED
|
@@ -0,0 +1,84 @@
|
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
3
|
+
## 0.6.3 (2026-05-04)
|
|
4
|
+
|
|
5
|
+
### Fixed
|
|
6
|
+
- **File messages now route through the Channel Inbound Pipeline** like text
|
|
7
|
+
messages, so they appear as part of the same Threema DM conversation
|
|
8
|
+
the agent is already in. Previously file inbounds were dispatched via
|
|
9
|
+
legacy `enqueueSystemEvent` against `agent:main:main`, which left them
|
|
10
|
+
invisible to the running DM session: the agent only learned about the
|
|
11
|
+
file by chance (e.g. by greping the inbound media folder later).
|
|
12
|
+
Symptom hit on 2026-05-04 when the user shipped the OpenClaw
|
|
13
|
+
2026.5.3 update protocol as a `.txt` file and the agent did not see it
|
|
14
|
+
for ~20 minutes.
|
|
15
|
+
|
|
16
|
+
### Added
|
|
17
|
+
- File inbounds now expose `MediaPath` / `MediaType` / `MediaUrl` to the
|
|
18
|
+
agent context (matching the convention used by the Matrix channel
|
|
19
|
+
plugin). The agent can read the saved file directly with its normal
|
|
20
|
+
tools (read / pdf / image) and reply in the same DM thread.
|
|
21
|
+
- The memory briefing block is now also injected into file inbounds, so
|
|
22
|
+
the agent's acute-state context applies regardless of whether the
|
|
23
|
+
user sent text or a file.
|
|
24
|
+
- Voice notes (audio file messages) get the same treatment: the
|
|
25
|
+
Whisper transcription is included in the body, the audio path in
|
|
26
|
+
`MediaPath`.
|
|
27
|
+
|
|
28
|
+
### Compatibility
|
|
29
|
+
- Falls back to the legacy `enqueueSystemEvent` path on older OpenClaw
|
|
30
|
+
runtimes that don't expose `channelRuntime.reply.finalizeInboundContext`,
|
|
31
|
+
or whenever the new pipeline path throws.
|
|
32
|
+
|
|
33
|
+
## 0.6.2 (2026-05-04)
|
|
34
|
+
|
|
35
|
+
### Fixed
|
|
36
|
+
- **Compiled runtime output** for the OpenClaw 2026.5.x npm-first plugin loader.
|
|
37
|
+
The package now ships `dist/index.js` and points `main`/`exports`/
|
|
38
|
+
`openclaw.extensions` at the compiled output. Previous releases shipped
|
|
39
|
+
the raw `index.ts` only, which OpenClaw 2026.5.0+ rejects with:
|
|
40
|
+
*"installed plugin package requires compiled runtime output for
|
|
41
|
+
TypeScript entry index.ts"*.
|
|
42
|
+
- Added `tsconfig.json`, a `build`/`prepublishOnly` script, and `.npmignore`
|
|
43
|
+
so future releases always include `dist/` and exclude `node_modules`.
|
|
44
|
+
- Cleaned a couple of strict-mode TypeScript signal-noise issues so the
|
|
45
|
+
package builds cleanly with `@types/node@22` on Node 22.
|
|
46
|
+
|
|
47
|
+
### Added
|
|
48
|
+
- **`channelConfigs.threema` metadata** in `openclaw.plugin.json`. The
|
|
49
|
+
2026.5.x setup surfaces and config schema engine read this; without it,
|
|
50
|
+
doctor logs:
|
|
51
|
+
*"channel plugin manifest declares threema without channelConfigs
|
|
52
|
+
metadata"*. The previous flat `configSchema` is preserved for older
|
|
53
|
+
OpenClaw versions.
|
|
54
|
+
- `build.openclawVersion` bumped to `2026.5.3`.
|
|
55
|
+
|
|
56
|
+
## 0.6.1 (2026-05-04)
|
|
57
|
+
|
|
58
|
+
### Added
|
|
59
|
+
- **Memory briefing hook** for inbound text messages. The plugin now appends an
|
|
60
|
+
untrusted "memory_briefing" block to `BodyForAgent` on every inbound Threema
|
|
61
|
+
text message. The block is composed at inbound time from two workspace files:
|
|
62
|
+
- `MEMORY.md` -> the leading `## 📌 Current State` section
|
|
63
|
+
- `memory/pending-actions.md` -> the leading `## 🔥 Akut` section
|
|
64
|
+
Both reads are bounded (≤ 8 KB per file) and cached for 60 s.
|
|
65
|
+
|
|
66
|
+
This makes long-running sessions resilient to staleness: even after weeks of
|
|
67
|
+
conversation, the agent sees the user's current acute state on every reply
|
|
68
|
+
without depending on memory recall heuristics. `RawBody`/`CommandBody` are
|
|
69
|
+
unchanged, so slash-command routing is unaffected.
|
|
70
|
+
|
|
71
|
+
Set the workspace via `agents.<id>.workspace` in the OpenClaw config; the
|
|
72
|
+
plugin falls back to `~/.openclaw/workspace` when no agent declares one.
|
|
73
|
+
|
|
74
|
+
### Notes
|
|
75
|
+
- Backwards compatible: when neither file exists or both sections are missing,
|
|
76
|
+
no briefing block is appended and `BodyForAgent` matches the original text.
|
|
77
|
+
- The briefing block uses the same untrusted-context conventions as other
|
|
78
|
+
OpenClaw inbound metadata - it is informational, not instructions.
|
|
79
|
+
|
|
80
|
+
## 0.6.0
|
|
81
|
+
|
|
82
|
+
- Channel Inbound Pipeline integration.
|
|
83
|
+
- Slash command parsing.
|
|
84
|
+
- Long message chunking.
|