# Clawpilot Config

> Use when the user needs help locating, validating, or minimally fixing ClawPilot host configuration required for pairing, auth, or host-side operations for OpenClaw, Hermes, or cc-connect Coding Agent hosts. Explain exactly what is missing and the most direct fix.

- Skill: `rethinking-studio/clawpilot-config` (Agent Skill)
- Install (CLI): `npx skillmds@latest add rethinking-studio/clawpilot-config`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rethinking-studio/clawpilot-config/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: rethinking-studio (https://skillmd.com/u/rethinking-studio)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/rethinking-studio/clawpilot-config

---


# ClawPilot Config

Use this skill for ClawPilot host configuration inspection and minimal correction.
Support:

- OpenClaw host config
- Hermes local API config
- cc-connect runtime config

## When To Use

Use this skill when the user needs to:

- Find the relevant OpenClaw config file
- Validate gateway token or password settings
- Validate referenced environment variables
- Understand why pairing or host-side operations cannot authenticate
- Validate Hermes API server settings in `~/.hermes/.env`
- Check `API_SERVER_ENABLED` / `API_SERVER_KEY`
- Validate cc-connect runtime settings in `~/.clawai/runtimes/ccconnect.json`
- Validate the cc-connect app config in `~/.cc-connect/config.toml`
- Check whether `cc-connect` is installed and runnable
- Validate cc-connect daemon readiness when pairing or host-side ccconnect operations depend on it

Do not use this skill for file delivery or general diagnostics when configuration is not the actual issue.

## Workflow

1. Identify the runtime in question: `openclaw`, `hermes`, or `ccconnect`.
2. Locate the relevant config file.
3. Inspect only the fields relevant to the failure.
4. If auth is provided via environment variable references, verify the referenced variables exist.
5. Explain exactly what is missing or misconfigured.
6. If the fix is obvious and low-risk, propose the minimal change.

Runtime-specific scope:

For `openclaw`:
- OpenClaw config path
- gateway token/password
- referenced env vars

For `hermes`:
- `~/.hermes/.env`
- `API_SERVER_ENABLED`
- `API_SERVER_KEY`
- local API base URL assumptions

For `ccconnect`:
- `~/.cc-connect/config.toml`
  - at least one `[[projects]]` entry
  - correct `[projects.agent]` type and `work_dir`
  - `[projects.agent.options] work_dir` must exist and be writable
  - do not leave `work_dir = "/"`; prefer the user's selected workspace, `$HOME/Desktop`, or another writable user directory
  - `[management] enabled = true`, port/token
  - `[bridge] enabled = true`, port/token
- `~/.clawai/runtimes/ccconnect.json`
- `ccconnectManagementUrl`
- `ccconnectManagementToken`
- `ccconnectBridgeUrl`
- `ccconnectBridgeToken`
- `cc-connect` command availability
- selected coding agent command availability, such as `claude`, `codex`, or `gemini`
- cc-connect daemon status when pairing or PocketClaw access depends on ccconnect staying alive

Important cc-connect notes:
- The official cc-connect AI install guide configures cc-connect but does not install the cc-connect daemon automatically.
- For PocketClaw ccconnect pairing, prefer the official cc-connect daemon so the process survives the shell session. Avoid recommending `cc-connect &`, shell background jobs, or terminal background execution.
- Prefer `clawpilot prepare-ccconnect` to create `~/.cc-connect/config.toml` with the PocketClaw placeholder channel, Management API, and Bridge settings before installing the daemon.
- Do not replace the placeholder channel with a dummy platform or ask the user to choose Feishu, Telegram, Discord, WeCom, or Weixin for PocketClaw pairing.
- ClawPilot must not start cc-connect itself; cc-connect should already be reachable through its daemon before `clawpilot pair --runtime ccconnect`.
- After installing/upgrading cc-connect or changing `~/.cc-connect/config.toml`, reinstall the daemon with the explicit config path:

```bash
cc-connect daemon stop || true
cc-connect daemon uninstall || true
cc-connect daemon install --config ~/.cc-connect/config.toml
cc-connect daemon restart
cc-connect daemon status
```

- If cc-connect is crashing, use daemon logs to find the real cause:

```bash
cc-connect daemon logs -f
```

- If `~/.cc-connect/config.toml` exists but Management API or Bridge settings are missing, identify those exact missing sections instead of replacing the user's project/platform config.

## Output Rules

- Name the exact missing field, file, or environment variable.
- Prefer the shortest direct fix.
- If multiple fixes are possible, recommend one and explain why.

## Do Not

- Do not rewrite unrelated config sections.
- Do not say "config is wrong" without naming the specific field or variable.
- Do not proceed as if auth is valid when it is only referenced but not actually present in the environment.