style: 修改一些变量名称

- 统一 trpc_claw 名称
- 同步修改一些文档
- 同步一些bug修复

Author: raylchen

README.md

@@ -165,8 +165,8 @@ For full configuration and advanced features, see: [openclaw.md](./docs/mkdocs/e
 **1. Generate config**
 
 ```bash
-mkdir -p ~/.trpc_agent_claw
-trpc_agent_cmd openclaw conf_temp --full > ~/.trpc_agent_claw/config.yaml
+mkdir -p ~/.trpc_claw
+trpc_agent_cmd openclaw conf_temp > ~/.trpc_claw/config.yaml
 ```
 
 **2. Set environment variables**
@@ -181,10 +181,10 @@ export TRPC_AGENT_MODEL_NAME=your_model
 
 ```bash
 # Force local CLI mode
-trpc_agent_cmd openclaw chat -c ~/.trpc_agent_claw/config.yaml
+trpc_agent_cmd openclaw chat -c ~/.trpc_claw/config.yaml
 
 # Local UI
-trpc_agent_cmd openclaw ui -c ~/.trpc_agent_claw/config.yaml
+trpc_agent_cmd openclaw ui -c ~/.trpc_claw/config.yaml
 ```
 
 **4. Connect WeCom / Telegram**
@@ -204,7 +204,7 @@ channels:
 ```
 
 ```bash
-trpc_agent_cmd openclaw run -c ~/.trpc_agent_claw/config.yaml
+trpc_agent_cmd openclaw run -c ~/.trpc_claw/config.yaml
 ```
 
 If no channel is available, `run` automatically falls back to local CLI for easy debugging.

README.zh_CN.md

@@ -166,8 +166,8 @@ tRPC-Agent 基于 [nanobot](https://github.com/HKUDS/nanobot) 提供了 trpc-cla
 **1. 生成配置文件**
 
 ```bash
-mkdir -p ~/.trpc_agent_claw
-trpc_agent_cmd openclaw conf_temp --full > ~/.trpc_agent_claw/config.yaml
+mkdir -p ~/.trpc_claw
+trpc_agent_cmd openclaw conf_temp > ~/.trpc_claw/config.yaml
 ```
 
 **2. 配置环境变量**
@@ -182,10 +182,10 @@ export TRPC_AGENT_MODEL_NAME=your_model
 
 ```bash
 # 强制本地 CLI
-trpc_agent_cmd openclaw chat -c ~/.trpc_agent_claw/config.yaml
+trpc_agent_cmd openclaw chat -c ~/.trpc_claw/config.yaml
 
 # 本地 UI
-trpc_agent_cmd openclaw ui -c ~/.trpc_agent_claw/config.yaml
+trpc_agent_cmd openclaw ui -c ~/.trpc_claw/config.yaml
 ```
 
 **4. 接入企业微信 / Telegram**
@@ -205,7 +205,7 @@ channels:
 ```
 
 ```bash
-trpc_agent_cmd openclaw run -c ~/.trpc_agent_claw/config.yaml
+trpc_agent_cmd openclaw run -c ~/.trpc_claw/config.yaml
 ```
 
 `run` 模式下若无可用通道会自动回退到本地 CLI，方便调试。

docs/mkdocs/en/multi_agents.md

@@ -440,7 +440,9 @@ Content Processing Assistant (Main Agent)
 
 ### TransferAgent (Transfer Proxy)
 
-TransferAgent is a transfer proxy Agent designed to enable custom Agents without transfer capability (such as KnotAgent, RemoteAgent, etc.) to gain transfer capability, thereby integrating them into the tRPC-Agent framework's multi-Agent system.
+TransferAgent is a transfer proxy Agent designed to enable custom Agents without transfer capability (such as `TrpcRemoteA2aAgent`) to gain transfer capability, thereby integrating them into the tRPC-Agent framework's multi-Agent system.
+
+`TrpcRemoteA2aAgent` can be used to simulate a remote Agent scenario (first start an A2A Agent service with `examples/a2a/run_server.py` to mimic a remote Agent).
 
 Through TransferAgent, custom Agents can:
 - **Act as sub_agent**: The parent Agent can transfer control to this Agent, and this Agent can transfer control to parent/sibling Agents
@@ -452,23 +454,24 @@ No need to provide `sub_agents` or `transfer_instruction` — TransferAgent dire
 
 ```python
 from trpc_agent_sdk.agents import TransferAgent, LlmAgent
-from trpc_agent_sdk.server.knot_agent import KnotAgent
-
-# Create a custom Agent (without transfer capability); KnotAgent is a specific Agent supporting an internal platform
-knot_agent = KnotAgent(
-    name="knot-assistant",
-    knot_api_url="...",
-    knot_api_key="...",
-    knot_model="...",
+from trpc_agent_sdk.server.a2a import TrpcRemoteA2aAgent
+
+# Create a custom Agent (without transfer capability); use TrpcRemoteA2aAgent to simulate a remote Agent
+remote_agent = TrpcRemoteA2aAgent(
+    name="remote-weather-assistant",
+    description="A remote weather agent served over A2A",
+    agent_base_url="http://127.0.0.1:18081",  # Remote A2A service URL
 )
+# Note: TrpcRemoteA2aAgent should be initialized during application startup
+# await remote_agent.initialize()
 
-# Enable transfer capability for knot_agent via TransferAgent
+# Enable transfer capability for remote_agent via TransferAgent
 transfer_agent = TransferAgent(
-    knot_agent,
+    remote_agent,
     model=model,
 )
 
-# Now knot_agent (via transfer_agent) can be invoked as a sub_agent
+# Now remote_agent (via transfer_agent) can be invoked as a sub_agent
 coordinator = LlmAgent(
     name="coordinator",
     model=model,
@@ -482,15 +485,16 @@ After providing `sub_agents`, TransferAgent analyzes the target Agent's returned
 
 ```python
 from trpc_agent_sdk.agents import TransferAgent, LlmAgent
-from trpc_agent_sdk.server.knot_agent import KnotAgent
-
-# Create a custom Agent (without transfer capability); KnotAgent is a specific Agent supporting an internal platform
-knot_agent = KnotAgent(
-    name="knot-assistant",
-    knot_api_url="...",
-    knot_api_key="...",
-    knot_model="...",
+from trpc_agent_sdk.server.a2a import TrpcRemoteA2aAgent
+
+# Create a custom Agent (without transfer capability); use TrpcRemoteA2aAgent
+remote_agent = TrpcRemoteA2aAgent(
+    name="remote-weather-assistant",
+    description="A remote weather agent served over A2A",
+    agent_base_url="http://127.0.0.1:18081",
 )
+# Note: TrpcRemoteA2aAgent should be initialized during application startup
+# await remote_agent.initialize()
 
 # Create child Agents
 data_analyst = LlmAgent(
@@ -502,19 +506,19 @@ data_analyst = LlmAgent(
 
 # Method 1: Provide custom transfer rules
 transfer_agent = TransferAgent(
-    knot_agent,
+    remote_agent,
     model=model,
     sub_agents=[data_analyst],
     transfer_instruction=(
-        "After knot-assistant returns results, analyze the response:\n"
+        "After remote-weather-assistant returns results, analyze the response:\n"
         "1. If the result contains data or statistics, transfer to data_analyst.\n"
         "2. Otherwise, return directly to the user."
     ),
 )
 
 # Method 2: Use default transfer rules (do not provide transfer_instruction)
 transfer_agent = TransferAgent(
-    knot_agent,
+    remote_agent,
     model=model,
     sub_agents=[data_analyst],
 )
@@ -551,7 +555,7 @@ The default rules automatically analyze the target Agent's results:
 #### Agent Naming
 
 TransferAgent's name is automatically generated in the format `transfer_{target_agent_name}`. For example:
-- If the target Agent's name is `knot-assistant`, the TransferAgent's name will be `transfer_knot-assistant`
+- If the target Agent's name is `remote-weather-assistant`, the TransferAgent's name will be `transfer_remote-weather-assistant`
 - If the target Agent's name is `custom-agent`, the TransferAgent's name will be `transfer_custom-agent`
 
 #### Notes

docs/mkdocs/en/openclaw.md

@@ -1,14 +1,14 @@
-# OpenClaw (trpc-claw)
+# OpenClaw (trpc_claw)
 
-`openclaw` is an agent runtime built on top of `trpc_agent_sdk` and `nanobot`, supporting:
+`openclaw` (also called `trpc_claw`) is an agent runtime built on top of `trpc_agent_sdk` and `nanobot`, supporting:
 
 - Third-party channel integrations (for example: Telegram / WeCom and other channels supported by nanobot). OpenClaw supports all of these channels. See [nanobot/channels](https://github.com/HKUDS/nanobot/tree/main/nanobot/channels).
 - Local CLI fallback mode
 - Tool invocation (file, shell, web, messaging, scheduled tasks, MCP, skills)
 - Session/memory management and summarization
 - Heartbeat/Cron scheduled execution
 
-Default workspace: `~/.trpc_agent_claw/workspace`
+Default workspace: `~/.trpc_claw/workspace`
 
 ## Core Capabilities
 
@@ -61,31 +61,29 @@ Current recommended command entry point (aligned with the repository state):
 trpc_agent_cmd openclaw --help
 ```
 
-> Note: older docs may mention `trpc-claw-py`; use `trpc_agent_cmd openclaw` as the authoritative command.
-
 ### 3) Generate Config Templates
 
 ```bash
-mkdir -p ~/.trpc_agent_claw
+mkdir -p ~/.trpc_claw
 
 # Minimal template
-trpc_agent_cmd openclaw conf_temp > ~/.trpc_agent_claw/config.yaml
+trpc_agent_cmd openclaw conf_temp > ~/.trpc_claw/config.yaml
 
 # Full template (recommended)
-trpc_agent_cmd openclaw conf_temp --full > ~/.trpc_agent_claw/config_full.yaml
+trpc_agent_cmd openclaw conf_temp --full > ~/.trpc_claw/config_full.yaml
 ```
 
 ### 4) Startup Modes
 
 ```bash
 # Auto mode: use gateway if channels are available; otherwise fall back to CLI
-trpc_agent_cmd openclaw run -c ~/.trpc_agent_claw/config_full.yaml
+trpc_agent_cmd openclaw run -c ~/.trpc_claw/config_full.yaml
 
 # Force local CLI interaction
-trpc_agent_cmd openclaw chat -c ~/.trpc_agent_claw/config_full.yaml
+trpc_agent_cmd openclaw chat -c ~/.trpc_claw/config_full.yaml
 
 # Start UI
-trpc_agent_cmd openclaw ui -c ~/.trpc_agent_claw/config_full.yaml
+trpc_agent_cmd openclaw ui -c ~/.trpc_claw/config_full.yaml
 ```
 
 ## Command Reference
@@ -106,23 +104,23 @@ trpc_agent_cmd openclaw ui -c ~/.trpc_agent_claw/config_full.yaml
 ```bash
 # Inspect by profile (recommended)
 trpc_agent_cmd openclaw deps \
-  -c ~/.trpc_agent_claw/config_full.yaml \
+  -c ~/.trpc_claw/config_full.yaml \
   --profile common-file-tools
 
 # Inspect by skill
 trpc_agent_cmd openclaw deps \
-  -c ~/.trpc_agent_claw/config_full.yaml \
-  --skills knot-skill-finder
+  -c ~/.trpc_claw/config_full.yaml \
+  --skills {skill-finder} # Placeholder skill name for downloading skills; replace with your real skill name
 
 # Output JSON
 trpc_agent_cmd openclaw deps \
-  -c ~/.trpc_agent_claw/config_full.yaml \
+  -c ~/.trpc_claw/config_full.yaml \
   --profile common-file-tools \
   --json
 
 # Execute the installation plan directly
 trpc_agent_cmd openclaw deps \
-  -c ~/.trpc_agent_claw/config_full.yaml \
+  -c ~/.trpc_claw/config_full.yaml \
   --profile common-file-tools \
   --apply
 ```
@@ -141,17 +139,17 @@ Common options:
 
 Configuration supports `YAML/JSON`, default lookup path:
 
-- `~/.trpc_agent_claw/config.json`
+- `~/.trpc_claw/config.json`
 
 You can override via:
 
 - CLI argument: `-c/--config`
-- Environment variable: `TRPC_AGENT_CLAW_CONFIG`
+- Environment variable: `TRPC_CLAW_CONFIG`
 
 Example:
 
 ```bash
-export TRPC_AGENT_CLAW_CONFIG=/path/to/config.yaml
+export TRPC_CLAW_CONFIG=/path/to/config.yaml
 trpc_agent_cmd openclaw chat
 ```
 
@@ -203,19 +201,21 @@ skills:
   skill_roots: []
   builtin_skill_roots: []
   config_keys:
-    - knot.enabled
-    - knot
+    - skillhub.enabled
+    - skillhub
   allow_bundled:
-    - knot.skill.finder
-    - knot-skill-finder
+    - skillhub.skill.finder
+    - skillhub-finder
   skill_configs:
-    knot-skill-finder:
+    skillhub-skill-finder:
       enabled: true
       env:
-        KNOT_USERNAME: ${KNOT_USERNAME}
-        KNOT_API_TOKEN: ${KNOT_API_TOKEN}
+        SKILLHUB_USERNAME: ${SKILLHUB_USERNAME}
+        SKILLHUB_TOKEN: ${SKILLHUB_TOKEN}
 ```
 
+Note: `skillhub-skill-finder` is only an example. Replace it with your actual skill name in real usage.
+
 ### tools
 
 - `restrict_to_workspace`: restrict tools to operate inside workspace only
@@ -241,8 +241,8 @@ skills:
 
 ## Default Directories
 
-- Config directory: `~/.trpc_agent_claw/`
-- Workspace: `~/.trpc_agent_claw/workspace`
+- Config directory: `~/.trpc_claw/`
+- Workspace: `~/.trpc_claw/workspace`
 
 ## Integrate with ClawBot
 
@@ -268,7 +268,7 @@ export TRPC_AGENT_BASE_URL=xxx
 export TRPC_AGENT_MODEL_NAME=xxx
 export WECOM_BOT_ID=xxx
 export WECOM_BOT_SECRET=xxx
-trpc_agent_cmd openclaw run -c ~/.trpc_agent_claw/config_full.yaml
+trpc_agent_cmd openclaw run -c ~/.trpc_claw/config_full.yaml
 ```
 
 ![wecom](./image/wecom.png)
@@ -288,7 +288,7 @@ Start:
 
 ```bash
 export TELEGRAM_BOT_TOKEN=xxx
-trpc_agent_cmd openclaw run -c ~/.trpc_agent_claw/config_full.yaml
+trpc_agent_cmd openclaw run -c ~/.trpc_claw/config_full.yaml
 ```
 
 ![telegram](./image/telegram.png)
@@ -378,7 +378,7 @@ tools:
 
 ```yaml
 logger:
-  name: trpc-claw
+  name: trpc_claw
   log_file: trpc_claw.log
   log_level: INFO
   log_format: "[%(asctime)s][%(levelname)s][%(name)s][%(pathname)s:%(lineno)d][%(process)d] %(message)s"