wenlan-recall

/wenlan-recall

Search Wenlan's memory by natural-language query. Returns matching memories ranked by hybrid vector + FTS search, then re-ordered by the agent if it helps.

Resolve the active space

The /wenlan-recall skill accepts one optional inline token of the form space:<name> anywhere in the argument string. The bundled resolver strips it and returns the rest as the query. It prints the resolved Space line itself:

raw_args="<the full argument string passed to /wenlan-recall>"
resolved="$("{{WENLAN_SKILLS_DIR}}/wenlan/scripts/resolve-space.sh" --cwd "$PWD" --args "$raw_args")"
space="$(printf '%s\n' "$resolved" | cut -f1)"
source_layer="$(printf '%s\n' "$resolved" | cut -f2)"
query="$(printf '%s\n' "$resolved" | cut -f3-)"

If query is empty, ask the user what they want to search for. Pass space="$space" to the recall MCP tool only when space is non-empty; otherwise omit the space filter.

Two phases

When a local model or API key is configured, the daemon can rerank and expand server-side. In local memory mode it cannot. The skill always does agent-side expansion and rerank itself — cheap, makes results good in both modes.

Phase 1 — expand the query (agent-side)

Before calling recall, rewrite the user's query into a more search-friendly form:

• Replace pronouns with the referent ("it" → the actual thing).
• Expand abbreviations the embedder is unlikely to know.
• Add the obvious synonym when the original term is too narrow (e.g. "auth" → "auth OR authentication").

Don't over-expand. If the query is already specific, leave it alone. One recall call per /wenlan-recall invocation — duplicate calls double embedding load and the merge step is rarely worth it. The daemon's own search_memory_expanded exists for the multi-query case; if it matters, use that endpoint instead of issuing parallel calls here.

Phase 2 — call the MCP tool

recall(query="<expanded query>", space=<resolved if non-empty>, memory_type=<inferred>)