Repair
Troubleshooting
Fix the common setup issues: daemon not running, MCP not connected, missing Claude commands, stale context, and support escalation.
At a glance
01
Start with /wenlan in Claude Code or wenlan doctor in a terminal.
02
Most issues are one of three things: daemon not reachable, MCP server not configured, or the client needs a restart.
01
Claude Code commands are missing
If /brief, /capture, or /handoff are missing, check that the Wenlan plugin is installed and restart Claude Code. Run /wenlan to check the connection. If it cannot connect, follow its setup prompts; a connected status means Claude Code reached Wenlan.
/wenlan02
Daemon is not reachable
Run wenlan status and wenlan doctor to check the local daemon. If setup is incomplete, follow the setup guidance in the output; if port 7878 is occupied, identify the process before stopping anything. Run the checks again after the fix.
~/.wenlan/bin/wenlan status
~/.wenlan/bin/wenlan doctor03
MCP client is not connected
If the daemon is healthy but the client has no Wenlan tools, inspect the client configuration with wenlan connect <client> --dry-run. Configure the intended client and restart it if required. A successful check is a small capture and recall in a new session.
04
Recall returns weak context
Try a specific query with a project, decision, person, or exact phrase, and check the active Space. Compare the result with the source you expected. If the stored material is stale or duplicated, review and correct it.
05
When to open an issue
If the checks do not resolve the issue, collect a reproducible report and redact private data before sharing it.
Next
Diagnostics and Issue Reports
Run the right checks before asking for help, separate daemon problems from client problems, and share only redacted output.
Read next