| name | pawai-cli |
| description | PawAI CLI / Jetson / Go2 team-development operations. Use when the user asks about pawai doctor, pawai status, pawai jetson deploy, pawai demo start/stop, pawai logs, deploying to Jetson, starting/stopping demo, Tailscale sharing, Jetson IP/network changes, Go2 192.168.123.161 reachability, lock collisions, branch/deploy mismatch, or five-person shared Jetson workflows.
|
pawai-cli
Use this skill for the team-facing PawAI CLI workflow. The goal is to help an AI
agent operate the repo without relying on remembered SSH/tmux/ROS2 commands.
Source Of Truth
Before giving exact command flags, inspect the current CLI:
pawai --help
pawai doctor --help
pawai jetson deploy --help
pawai demo start --help
pawai demo stop --help
Then use the human docs as the canonical explanation:
docs/pawai_cli/usage-guide.md — daily-use walkthrough (start here for "how do I X with the CLI"). Has decision trees for the three high-frequency commands and an error-message lookup table.docs/pawai_cli/README.md — full command reference, flag tables, env vars.docs/pawai_cli/troubleshooting.md — red-light triage A–J.docs/pawai_cli/modules.md — module ↔ package/test/log map.docs/pawai_cli/team-onboarding.md — first-time install only.
If this skill mentions a planned flag that does not exist yet, do not invent it.
Report that the CLI has not implemented it and fall back to the nearest current
command.
Default Flow
For "how do I get started / why can't I connect":
- Run or ask for
pawai doctor.
- If Jetson is unreachable, read
references/network-diagnosis.md.
- If Go2 is unreachable, check Jetson -> Go2 from the doctor output first.
- If demo/deploy is blocked by another user, read
references/lock-semantics.md.
For "deploy my module":
- Identify the module:
face, speech, gesture, pose, object, nav, brain, or studio.
- Run
pawai dev info <module> to confirm packages, docs, tests, and logs.
- Run
pawai jetson deploy --module <module>.
- Run
pawai status --short and inspect last deploy / branch warnings.
For "demo start/stop":
- Run
pawai status --short.
- Respect any active demo/lock warning.
-y means skip ordinary prompts; only
--force may take over another user's lock.
- Phase 1 behaviour to remember:
- Own existing lock +
demo start → CLI auto-cleans your old lane and
restarts. No flag needed. Message: Existing lock is yours (...). Restarting demo.
- Own stale lock +
demo stop → CLI uses release_if_owned(), no --force
needed. Message: Reclaiming your own stale ... lock.
- Other user's lock +
demo stop → requires --force; coach the user to
coordinate first, do not auto-force.
- Start with
pawai demo start; stop with pawai demo stop.
- Use
pawai logs <module> --lines 200 for the failing module.
For "platform error / exit 10":
- The CLI rejects Windows native, WSL1, and repos under
/mnt/c/... with exit 10.
- This is non-negotiable; do not suggest workarounds. Direct the user to WSL2
Ubuntu and a Linux-side repo path.
For "what does this CLI error mean":
- The error-message lookup table is in
docs/pawai_cli/usage-guide.md §7.
- Cover: platform exit 10, Tailscale offline, missing JETSON_TAILSCALE_IP,
lock owned by other user,
-y cannot override, failed acquire lock 3 retries,
module required, Jetson unreachable. Each row has the exact next command.
For "pawai health brain" (Phase 1 new command):
- Wraps
.claude/skills/brain-studio-lane/scripts/healthcheck.sh with $JETSON_HOST
and $JETSON_TAILSCALE_IP injected from the CLI's resolved env.
- Run after
pawai demo start once the stack is ~30s up.
- Output is 8 numbered checks; treat any ❌ as actionable.
References
- Daily-use walkthrough + decision trees + error table:
docs/pawai_cli/usage-guide.md
- Command syntax and examples:
references/command-reference.md
- Lock ownership,
-y vs --force, branch mismatch: references/lock-semantics.md
- Tailscale, Jetson network moves, Go2 Ethernet:
references/network-diagnosis.md
Helper Script
For a quick non-destructive snapshot:
bash .claude/skills/pawai-cli/scripts/quick-check.sh
The script only runs read-only CLI/status commands.
