@houndmcp/hound-mcp-pi 10.3.0 → 10.4.0

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.
Files changed (3) hide show
  1. package/README.md +19 -1
  2. package/extensions/hound.ts +722 -569
  3. package/package.json +2 -1
package/README.md CHANGED
@@ -15,12 +15,30 @@ Hound web research for the Pi agent. Six native tools, all routed through a sing
15
15
  # 1. Install Hound (the MCP server / engine)
16
16
  pip install hound-mcp[all]
17
17
 
18
- # 2. Install this Pi extension
18
+ # 2. Install this Pi extension (npm, auto-updates)
19
+ pi install npm:@houndmcp/hound-mcp-pi
20
+ ```
21
+
22
+ Alternatively, install from git (pins to a specific tag):
23
+
24
+ ```bash
19
25
  pi install git:github.com/dondai1234/master-fetch@v10.3.0
20
26
  ```
21
27
 
22
28
  That's it. The extension auto-discovers `hound` on your PATH, spawns it as a singleton subprocess, and prewarms it at session start. No API key, no account, no config file.
23
29
 
30
+ ## Updating
31
+
32
+ ```bash
33
+ # Update Hound (the MCP server)
34
+ hound -u
35
+
36
+ # Update the Pi extension (if installed via npm, unpinned)
37
+ pi update npm:@houndmcp/hound-mcp-pi
38
+ ```
39
+
40
+ The extension checks at session start whether the installed Hound version matches the extension version. If they diverge by a major version, it warns you to update both.
41
+
24
42
  ## How it works
25
43
 
26
44
  The extension spawns `hound` (the MCP server) as a stdio subprocess and speaks MCP JSON-RPC to it. The subprocess is a singleton — it stays alive for the whole Pi session, so Hound's startup prewarm (stealthy browser, search engines, neural reranker) runs once and persists. Zero re-launch cost per call.