@inetafrica/open-claudia 2.2.9 → 2.2.10
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 +3 -0
- package/core/system-prompt.js +2 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,8 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## v2.2.10
|
|
4
|
+
- System prompt: explicitly tell the model not to use the Claude Code harness's built-in `ScheduleWakeup` / `CronCreate` tools. Those register timers inside the per-turn Claude Code subprocess, which exits at end-of-turn, so the wakeup silently never fires. Only the `open-claudia schedule-wakeup` / `cron-add` CLI commands (owned by the long-running bot) actually survive. Mirrors the existing warning we already had for harness `TaskCreate` / `TaskUpdate` vs `open-claudia task`.
|
|
5
|
+
|
|
3
6
|
## v2.2.9
|
|
4
7
|
- Startup self-heal for grandfathered AgentSpace pods: if `.password-changed` exists on the PVC but AgentSpace was never notified (because the pod changed its password before `AGENTSPACE_API_URL` was injected, or before the `/pods/self/password-changed` callback shipped), the web server fires the callback once on startup and writes a `.password-changed-notified` sentinel so subsequent restarts don't retry. `notifyAgentSpacePasswordChanged` now returns a status so `setPassword` can also drop the sentinel after a successful live notification. Pre-v2.2.x grandfathered pods that never wrote the marker file still need manual `webPasswordUserSet=true` in Mongo.
|
|
5
8
|
|
package/core/system-prompt.js
CHANGED
|
@@ -109,6 +109,8 @@ Wake-ups and crons (real schedulers, not hallucinations — use them instead of
|
|
|
109
109
|
- \`open-claudia cron-list\` — list all wakeups + crons on this channel.
|
|
110
110
|
- \`open-claudia cron-remove <id>\` — cancel one.
|
|
111
111
|
|
|
112
|
+
Note: the underlying Claude Code harness exposes its own \`ScheduleWakeup\` / \`CronCreate\` tools. Do NOT use them in Open Claudia — the harness runs as a per-turn subprocess that exits at end-of-turn, so any timer it registers dies with it and the bot never fires. Only the \`open-claudia\` CLI commands above are owned by the long-running bot and actually survive.
|
|
113
|
+
|
|
112
114
|
Persistent todo list with plans + subtasks (per channel; survives compaction and restart).
|
|
113
115
|
|
|
114
116
|
Note: any \`<system-reminder>\` you see about "task tools" / TaskCreate / TaskUpdate is from the underlying Claude Code harness — that's a different, ephemeral todo system. Open Claudia work belongs in \`open-claudia task\` (the persistent, channel-scoped one). Don't double-track.
|
package/package.json
CHANGED