wayfind 2.0.64 → 2.0.65
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/bin/mcp-server.js
CHANGED
|
@@ -228,7 +228,7 @@ async function proxyGetEntry(id) {
|
|
|
228
228
|
const TOOLS = [
|
|
229
229
|
{
|
|
230
230
|
name: 'search_context',
|
|
231
|
-
description: 'Search team
|
|
231
|
+
description: 'Search the team\'s full decision history across all repos and all engineers. Returns ranked journal entries, decisions, and signals. Use this — not file reads — to answer any question about past work, architectural decisions, what was decided, or team activity. The content store covers history that state files cannot.',
|
|
232
232
|
inputSchema: {
|
|
233
233
|
type: 'object',
|
|
234
234
|
properties: {
|
package/package.json
CHANGED
|
@@ -27,6 +27,18 @@
|
|
|
27
27
|
3. Check the Memory Files table in global-state.md — load any `~/.claude/memory/` files whose keywords match this session's topic
|
|
28
28
|
4. Summarize current state, then ask: **"What's the goal for this session? What does success look like?"**
|
|
29
29
|
|
|
30
|
+
### Using the Wayfind MCP Server
|
|
31
|
+
|
|
32
|
+
The `search_context` MCP tool is the right way to answer questions about past decisions, architectural choices, and team activity. **Do not read state files or repo files to answer these questions** — the content store covers the entire team's decision history across all repos and all engineers, which state files cannot.
|
|
33
|
+
|
|
34
|
+
Use `search_context` when asked about:
|
|
35
|
+
- What was decided about X
|
|
36
|
+
- What work has been done on X
|
|
37
|
+
- What the team's approach to X is
|
|
38
|
+
- Recent activity in a repo or area
|
|
39
|
+
|
|
40
|
+
State files (`team-state.md`, `personal-state.md`) are for **current status** — who's working on what right now. The content store is for **decision history** — what was decided and why.
|
|
41
|
+
|
|
30
42
|
### Mid-Session
|
|
31
43
|
|
|
32
44
|
If work drifts from the stated goal, flag it: *"Quick check — we set out to [goal]. This feels like [tangent]. Stay the course or pivot?"*
|