QwenPaw Installation and Configuration Q&A Guide

Use this skill when the user asks about QwenPaw installation, initialization, environment configuration, dependency requirements, or common configuration options.

Core principles:

• Check local documentation first, then answer
• Base answers on what has actually been read, do not speculate
• Answer in the same language the user used to ask

Standard Flow

Step 1: Locate the Documentation Directory

Use built-in path resolution (works for all install methods)

DOCS_DIR=$(python3 -c "from qwenpaw.constant import DOCS_DIR; print(DOCS_DIR or '')" 2>/dev/null)

If the above returns a non-empty path and the directory exists, use it directly and skip to Step 2.

If it fails (e.g., older version without DOCS_DIR), fall back in the following order:

Check for documentation directory in memory

First, check whether there is a documentation directory in memory. If found, use it directly; otherwise, proceed to the next step.

# Get the documentation directory from memory
DOCS_DIR=$(find ~/.qwenpaw/memory/ -type d -name "docs")

If there is no documentation directory in memory, continue with the following logic.

Check the documentation directory in the project source code

Run the following script logic to obtain the variable $QWENPAW_ROOT:

# Get the absolute path of the binary
QWENPAW_PATH=$(which qwenpaw 2>/dev/null || whereis qwenpaw | awk '{print $2}')

# Logical deduction: if the path contains .qwenpaw/bin/qwenpaw, the root is three levels up
# Example: /path/to/QwenPaw/.qwenpaw/bin/qwenpaw -> /path/to/QwenPaw
if [[ "$QWENPAW_PATH" == *".qwenpaw/bin/qwenpaw" ]]; then
    QWENPAW_ROOT=$(echo "$QWENPAW_PATH" | sed 's/\/\.qwenpaw\/bin\/qwenpaw//')
else
    # Fallback: try to get the parent of the parent directory
    QWENPAW_ROOT=$(dirname $(dirname "$QWENPAW_PATH") 2>/dev/null || echo ".")
fi

echo "Detected QwenPaw Root: $QWENPAW_ROOT"