@karmaniverous/jeeves-watcher-openclaw 0.3.8 → 0.3.9
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.
|
@@ -84,6 +84,52 @@ You don't need to know the rules in advance. The config is introspectable at run
|
|
|
84
84
|
2. **Search** — use `watcher_search` with a natural language query and optional metadata filters
|
|
85
85
|
3. **Read source** — use `read` (standard file read) with `file_path` from search results for full document content
|
|
86
86
|
|
|
87
|
+
## Bootstrap (First Session)
|
|
88
|
+
|
|
89
|
+
The first time the watcher plugin loads in a new deployment, orient yourself proactively. Don't wait for the user to ask a question — understand what you have access to.
|
|
90
|
+
|
|
91
|
+
**Automatic bootstrap sequence:**
|
|
92
|
+
|
|
93
|
+
1. **Health check** — call `watcher_status`. Confirm the service is running, note point count and collection dimensions.
|
|
94
|
+
2. **Discover the deployment** — run the Orientation Pattern (see below): query `$.['description','search']` for organizational strategy and score thresholds, then `$.inferenceRules[*].['name','description']` for available record types.
|
|
95
|
+
3. **Cache context** — store the orientation results mentally for the session. You now know what domains exist, what record types are searchable, and how to interpret scores.
|
|
96
|
+
4. **Report readiness** — briefly tell the user what you found: how many points, which domains, any issues. One or two sentences, not a wall of text.
|
|
97
|
+
|
|
98
|
+
**On subsequent sessions:** Repeat steps 1-3 silently. Only report if something changed (service down, point count dropped significantly, new domains appeared).
|
|
99
|
+
|
|
100
|
+
**Key principle:** The agent drives discovery. The user shouldn't have to explain their archive to you — the archive explains itself through its config.
|
|
101
|
+
|
|
102
|
+
## Install Modes
|
|
103
|
+
|
|
104
|
+
The plugin supports two install modes, controlled by the `--memory` flag during installation:
|
|
105
|
+
|
|
106
|
+
**Standard mode** (`npx @karmaniverous/jeeves-watcher-openclaw install`):
|
|
107
|
+
- Registers `watcher_*` tools only (search, enrich, status, query, validate, config_apply, reindex, issues)
|
|
108
|
+
- OpenClaw's built-in `memory-core` remains the memory provider
|
|
109
|
+
- Use when the watcher is a supplementary search tool alongside native memory
|
|
110
|
+
|
|
111
|
+
**Memory mode** (`npx @karmaniverous/jeeves-watcher-openclaw install --memory`):
|
|
112
|
+
- Registers all tools: `watcher_*` plus `memory_search` and `memory_get`
|
|
113
|
+
- Claims the OpenClaw memory slot — the watcher becomes the memory provider
|
|
114
|
+
- MEMORY.md and memory/*.md files are indexed and searched via the watcher's vector store
|
|
115
|
+
- Use when the watcher should be the single source of truth for both archive search and agent memory
|
|
116
|
+
|
|
117
|
+
**How to tell which mode you're in:** If `memory_search` and `memory_get` are in your available tools, you're in memory mode. If you only see `watcher_*` tools, you're in standard mode.
|
|
118
|
+
|
|
119
|
+
## Proactive Posture
|
|
120
|
+
|
|
121
|
+
**If you're in standard mode and the deployment would benefit from memory mode, say so.** The watcher's vector store with 3072-dimension Gemini embeddings provides significantly better semantic memory than flat file search. If you notice:
|
|
122
|
+
|
|
123
|
+
- The user has a substantial archive (>10K points)
|
|
124
|
+
- Memory searches are returning poor results via native memory
|
|
125
|
+
- The user is asking questions that span multiple memory files
|
|
126
|
+
|
|
127
|
+
...then suggest the upgrade:
|
|
128
|
+
|
|
129
|
+
> "The watcher is running with a large archive but I'm using basic file memory. Upgrading to memory mode would give semantic search over your memory files too. To upgrade: `npx @karmaniverous/jeeves-watcher-openclaw install --memory` and restart the gateway."
|
|
130
|
+
|
|
131
|
+
**Don't nag.** Suggest once per session at most, and only when there's a concrete benefit. If the user declines or doesn't respond, drop it.
|
|
132
|
+
|
|
87
133
|
## Tools
|
|
88
134
|
|
|
89
135
|
### `memory_search`
|
package/openclaw.plugin.json
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
"id": "jeeves-watcher-openclaw",
|
|
3
3
|
"name": "Jeeves Watcher",
|
|
4
4
|
"description": "Semantic search, metadata enrichment, and instance administration for a jeeves-watcher deployment.",
|
|
5
|
-
"version": "0.3.
|
|
5
|
+
"version": "0.3.9",
|
|
6
6
|
"skills": [
|
|
7
7
|
"dist/skills/jeeves-watcher"
|
|
8
8
|
],
|
package/package.json
CHANGED